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
When I'm importing a Harmony dataset with the modified bioformats libarary which fully supports the Harmony datasets now, the plate acquisition node in the Omero.Web client does not get the acquisition date and time which is available in the metadata of the plate acquisition. I remember seeing that it was correctly set when using the Insight.Importer, but when I use the bin/omero import command line tool, the acquisition is called Run 1, Run 101, or something similar.
The text was updated successfully, but these errors were encountered:
I can confirm this behavior. The start time for the plate acquisition is set in the database, but OMERO.web requires that both the start and end time be set in order for the plate acquisition labels in the browsing tree to include the start time. A proposed fix for OMERO.web is forthcoming.
This adds an extra case to the logic for setting the plate acquisition
name in the tree in the left-hand panel. If a start time (but not an
end time) was set, then the name will be the start time instead of "Run $id".
See glencoesoftware#3
When I'm importing a Harmony dataset with the modified bioformats libarary which fully supports the Harmony datasets now, the plate acquisition node in the Omero.Web client does not get the acquisition date and time which is available in the metadata of the plate acquisition. I remember seeing that it was correctly set when using the Insight.Importer, but when I use the bin/omero import command line tool, the acquisition is called Run 1, Run 101, or something similar.
The text was updated successfully, but these errors were encountered: