Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Initial Version and Version 1 of Ticket #12473


Ignore:
Timestamp:
07/17/14 12:28:24 (10 years ago)
Author:
rleigh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12473 – Description

    initial v1  
    11Most users and indeed file formats aren't separating the conjugated probes into separate metadata elements, so for most cases the existing channel name is sufficient for these needs.  However, newer formats like CZI do allow separation of the conjugated fluorophore and the probe. 
    22 
    3 With the current model, the channel name might be CK18-AF594 where in CZI you can 
    4 separate the probe (anti-cytokeratin-18) from its flurophore (Alexa 
     3With the current model, the channel name might be a physical hardware parameter (channel ID or filter name) or a general name e.g. CK18-AF594 where with CZI we have a name plus a description.  You could separate the probe (anti-cytokeratin-18) from its flurophore (Alexa 
    54Fluor 594).  However, CZI's use of channel and name for modelling this isn't particularly self-describing.  We might want to retain the generic channel name and provide additional attributes for the probe and the reporter (which isn't necessarily fluorescent), and possibly also have another generic "description" attribute for detailed description. 
    65 
    76Also note that there isn't necessarily a 1:1 correspondence between channel and probe/fluor.  Examples include hyperspectral imaging and normal imaging which requires correction for "bleedthrough" between channels.  In these cases, the physical channels used for acquisition require transformation to a set of logical channels which will be equal to or less than the acquisition channel count in number.  We might want to consider modelling this as part of the rendering settings work, or possibly split it out as a separate unit of work. 
     7 
     8Modelling suggestions: 
     9- physical channel ID (hardware channel ID/name) 
     10- logical channel ID (post-correction/unmixing) 
     11- reporter (attach to logical channel if used, otherwise physical channel) 
     12- probe (attach to logical channel if used, otherwise physical channel) 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.15233 sec.)

We're Hiring!