Task #3651 (new)
Opened 13 years ago
Last modified 12 years ago
Colour metadata from PFF — at Version 1
| Reported by: | wmoore | Owned by: | wmoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-Beta4.3 |
| Component: | Import | Version: | n.a. |
| Keywords: | n.a. | Cc: | ajpatterson, cxallan, jburel, j.springfield@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by wmoore)
At least some formats store colours for channels, either user-assigned or based on acquisition.
Several users have requested that we read this data and use it to set initial rendering settings on import.
E.g. From Martin's e-mail:
One constant issue is still assignment of the colours to the channels. Using the colours assigne by the user at acquisition is NOT OPTIONAL, using the 'natural colours' creates constant problems for the following reasons:
- whenever two channels have the same detection range (with different excitation), the channels are shown with the same colour on the screen and hence indistinguishable
- whenever a detection range is in the far-red or infrared range, the channel is not shown at all (consequent, but pointless)
Waiting on reply to forum above regarding format.
I'll look at where this info is stored in lif files and other confocal formats.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
From Martin's e-mail:
One constant issue is still assignment of the colours to the channels. Using the colours assigne by the user at acquisition is NOT OPTIONAL, using the 'natural colours' creates constant problems for the following reasons: