Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #7355 (closed)

Opened 8 years ago

Closed 6 years ago

Last modified 6 years ago

Zeiss LSM: preserve wavelength range for spectral detectors

Reported by: mlinkert Owned by: ajpatterson
Priority: major Milestone: 5.0.0-beta1
Component: Bio-Formats Version: n.a.
Keywords: schema, xsd-2013-1 Cc: wmoore, ajpatterson, m.spitaler@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Channels acquired using a spectral detector ('ChS') have a range of wavelengths associated with them (see '*Wavelength Begin' and '*Wavelength End' in original metadata).

It would be nice if these values were preserved somewhere in OME-XML, though I don't know at the moment where best to put them.

Change History (10)

comment:1 Changed 7 years ago by wmoore

I think we already do this in some cases by creating a 'Filter' that represents a spectral detector.

E.g. Model: "SP Mirror 1", TransmittanceRange (CutIn & CutOut) etc. This could be improved by specifying a new FilterType? to indicate this is a tuneable filter. Since we currently only have:

omero=# select * from filtertype;
 id | permissions |     value      | external_id 
----+-------------+----------------+-------------
  1 |         -35 | LongPass       |            
  2 |         -35 | ShortPass      |            
  3 |         -35 | BandPass       |            
  4 |         -35 | MultiPass      |            
  5 |         -35 | Dichroic       |            
  6 |         -35 | NeutralDensity |            
  7 |         -35 | Other          |            
  8 |         -35 | Unknown        |            

comment:2 Changed 7 years ago by ajpatterson

  • Keywords schema added

comment:3 Changed 7 years ago by ajpatterson

  • Milestone changed from Unscheduled to OMERO-5

comment:4 Changed 6 years ago by ajpatterson

  • Keywords xsd-2013-1 added

comment:5 Changed 6 years ago by ajpatterson

I will add a new filter type "Tuneable" at the moment. Extending the detector can be looked at as part of ticket #3682 - I have added a link back to this ticket.

Last edited 6 years ago by ajpatterson (previous) (diff)

comment:6 Changed 6 years ago by ajpatterson

After consulting with Helen, the office, and google we have decided the spelling is "Tunable" (without the e from Tune).

comment:7 Changed 6 years ago by ajpatterson

Adding attribute "Tuneable" (with the e) as stop gap measure so that the spelling matches that used in Laser. Either it will remain as this spelling or we will changes the spelling for both Filter and Laser.

comment:8 Changed 6 years ago by ajpatterson

  • Owner changed from mlinkert to ajpatterson
  • Status changed from new to accepted

comment:9 Changed 6 years ago by ajpatterson

  • Resolution set to fixed
  • Status changed from accepted to closed

comment:10 Changed 6 years ago by Andrew J Patterson <workonly@…>

(In [1c1ab603dae6162a84a7814752741642da64856c/ome.git] on branch develop) Adding Tuneable (with e) Filter Type, see #7355

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

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

We're Hiring!