You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for a very useful plugin.
Unless I have overlooked it, there is currently just one way to export the metadata present in the original PTU files, which is to open up the Console window and copy/paste the relevant information in a separate file. This becomes cumbersome as soon as one imports more than one PTU file, as their metadata is appended to the console output (together with any intermediate ImageJ message, if any.
One suggestion would be to create a CSV file-ready tabulated output of the corresponding information, as done for instance by the Bio-Formats Importer plugin, which creates a separate "Original Metadata - File Name" tabulated representation of SDT file metadata (Becker & Hickl hardware equivalent of the PicoQuant PTU file format).
This makes it convenient to save that file as a CSV file right after importing a FLIM stack, saving it as a folder of image, and before importing a new one.
The text was updated successfully, but these errors were encountered:
Is it ok, if there would be an option to show a Results table after loading PTU file?
It can be saved as a tabulated CSV file in a macro to any location.
Or just dropping CSV into original file path/folder is better?
No worries.
I have in the meantime written my own ptu file import code, but either of the two options you are suggesting would probably do the job. The point is that there is a lot of critical information in this metadata without which it is hard to fully interpret the resulting data.
Thanks for a very useful plugin.
Unless I have overlooked it, there is currently just one way to export the metadata present in the original PTU files, which is to open up the Console window and copy/paste the relevant information in a separate file. This becomes cumbersome as soon as one imports more than one PTU file, as their metadata is appended to the console output (together with any intermediate ImageJ message, if any.
One suggestion would be to create a CSV file-ready tabulated output of the corresponding information, as done for instance by the Bio-Formats Importer plugin, which creates a separate "Original Metadata - File Name" tabulated representation of SDT file metadata (Becker & Hickl hardware equivalent of the PicoQuant PTU file format).
This makes it convenient to save that file as a CSV file right after importing a FLIM stack, saving it as a folder of image, and before importing a new one.
The text was updated successfully, but these errors were encountered: