Skip to content

Create SP-corrected maps before GLOWS L3e available #60

@jtniehof

Description

@jtniehof

Summary

Dave has given direction that we proceed with the survival-corrected maps in cases where the GLOWS L3e are not yet available, in accordance with the general IMAP mission principle that we not hold up products we can produce just to wait for "better" inputs. Conceptually he described this as setting up the L3 SP maps to take a "nominal" survival probability input that is just SP as a function of energy, and eventually supersede that with the real L3e inputs.

This needs further definition before it can be estimated, see below. @jtniehof will work with GLOWS team and IMWG to define.

Requirements

The goals of this feature are:

  • Providing SP-corrected maps that are "better than nothing" for science analysis.
  • Ensuring constant testing of the production pipeline such that when real L3e do show up, we can feel confident the (updated) SP-corrected maps will be properly produced.

Implementation will include:

  • An ancillary file with "nominal" values, dependency TBD (potentially energy and latitude)
  • Updating L3 SP map code to use the nominal values for pointing sets which do not have a corresponding L3e file. TBR -- if there are only one or two PSETS missing, we may want to just skip them instead
  • Flagging pixels which include any nominal values, even if averaged with "real" ones (think about the polar pixels).
  • Update the daily L3 SP initalizer code to trigger if L2 maps are available and the L2 map is new or there are new GLOWS L3e...no longer require GLOWS L3e. Because L3e are made in batches, this will not thrash.

Related tickets

This interacts with the rolling map production (IMAP-Science-Operations-Center/imap_processing#2849), as we are no longer assuming maps are triggered manually.

Metadata

Metadata

Assignees

Labels

Ins: GLOWSRelated to the GLOWS instrumentIns: HiRelated to the IMAP-Hi instrumentIns: LoRelated to the IMAP-Lo instrumentIns: UltraRelated to the IMAP-Ultra instrumentPhase E: Parent IssuePhase E major task indicatorenhancementNew feature or request

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions