Skip to content

Metadata export #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
smXplorer opened this issue Apr 7, 2019 · 2 comments
Open

Metadata export #1

smXplorer opened this issue Apr 7, 2019 · 2 comments

Comments

@smXplorer
Copy link

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.

@ekatrukha
Copy link
Member

I am sorry for the late reply.

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?

@smXplorer
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants