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
Describe the issue identified (if applicable)
Time Delay Integration (TDI) is a feature of many cameras. It is currently not part of IMG. We want to rectify that by providing a TDI class to describe these cameras.
Describe the solution you'd like
New class: Time_Delay_Integration
Contains parameters describing Time_Delay_Integration, which is where the detector is shifted by rows in synchronization with the motion of the image across the detector, in order to increase integration time.
Class should be a child of both Imaging and Commanded_Parameters, with a cardinality of 0:any in both.
Class should inherit from Data_Processing
Attributes:
tdi_detector_id - string, card 0-1
Identifies the detector for which this TDI parameter set applies. Detector IDs are mission specific.
tdi_rows - int, card 0-1. This is the same as tdi_stage_count for junocam, TDI in hirise edr
Specifies the number of detector rows that are integrated together for TDI
tdi_direction - string, card 0-1
Specifies the direction of TDI integration in a mission-specific manner
tdi_line_rate - float, unit of time, card 0-1
Specifies the time interval from readout of one row to readout of the next
tdi_line_rate_code - string, card 0-1
Mission-specific identifier or commanded value for line_rate
Attribute set is designed to meet the needs of currently-known cameras (see examples below). As with everything in IMG, the attributes can and should be extended as cameras with different capabilities or metadata come along.
Describe alternatives you've considered
Currently, missions are rolling their own keywords in the MISSION LDD's, which is antithetical to good LDD design practice.
LDD Dictionary Version
Next version
PDS4 IM Version
All of the currently-built ones
Need-by Date
ASAP. We want to refit Clipper to use these but the window for that will not be open for long. Juno also uses these and is in active PDS3->4 migration now.
Additional context
Here is how this would look in various current or planned missions. Note that some of these missions are already in production. We are not suggesting that they change to use this mechanism (although we welcome it if they want). Just showing how the class definition meets the needs of existing TDI cameras.
<img:Time_Delay_Integration>
<img:active_flag>true</>
<img:tdi_rows> value of tdi_stages_count </>
</>
Clipper
<img:Time_Delay_Integration>
<img:active_flag>false</> -- I think rows=1 means false?
<img:tdi_rows>1</>
</>
ShadowCam
<img:Time_Delay_Integration>
<img:active_flag>true</>
<img:tdi_direction>A</> -- A or B for shadowcam
<img:tdi_line_rate unit="ms"> line_rate_ms value </>
<img:tdi_line_rate_code> line_rate_code value </>
</>
HiRISE EDR
<img:Time_Delay_Integration>
<img:active_flag>true</>
<img:detector_id>red5</> -- optional for EDR
<img:tdi_rows> TDI value </>
</>
Issue Type
Enhancement
Describe the issue identified (if applicable)
Time Delay Integration (TDI) is a feature of many cameras. It is currently not part of IMG. We want to rectify that by providing a TDI class to describe these cameras.
Describe the solution you'd like
Class should be a child of both Imaging and Commanded_Parameters, with a cardinality of 0:any in both.
Class should inherit from Data_Processing
Attributes:
Attribute set is designed to meet the needs of currently-known cameras (see examples below). As with everything in IMG, the attributes can and should be extended as cameras with different capabilities or metadata come along.
Describe alternatives you've considered
Currently, missions are rolling their own keywords in the MISSION LDD's, which is antithetical to good LDD design practice.
LDD Dictionary Version
Next version
PDS4 IM Version
All of the currently-built ones
Need-by Date
ASAP. We want to refit Clipper to use these but the window for that will not be open for long. Juno also uses these and is in active PDS3->4 migration now.
Additional context
Here is how this would look in various current or planned missions. Note that some of these missions are already in production. We are not suggesting that they change to use this mechanism (although we welcome it if they want). Just showing how the class definition meets the needs of existing TDI cameras.
Juno-SRU
Junocam
Clipper
ShadowCam
HiRISE EDR
HiRISE RDR
MVIC on New Horizons/Lucy
with a similar section under Commanded_Parameters, but without tdi_line_rate:
The text was updated successfully, but these errors were encountered: