Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: ip_isr
-
Labels:None
-
Team:Alert Production
Description
Think about what AssembleCcdTask should do when passed incomplete AmpInfo tables. Options are:
- Raise an exception
- Fill gaps with NaNs (which subsequently get interpolated over by IsrTask)
Considerations:
- Amps will fail
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Team | Alert Production [ 10300 ] |
Remote Link | This issue links to "Page (Confluence)" [ 21262 ] |
Remote Link | This issue links to "Page (Confluence)" [ 36914 ] |
I don't think a failed amp can reasonably be handled by an incomplete AmpInfo table. Rather the AmpInfo table needs a flag indicating that an amplifier is bad. If that flag is set then some other data in the table should be ignored. But the bounding boxes indicating raw and assembled data are still relevant. Thus I don't think it make sense to support incomplete AmpInfo tables.