-
Notifications
You must be signed in to change notification settings - Fork 33
Map epoch and epoch_delta #1747
Copy link
Copy link
Open
Labels
Ins: HiRelated to the IMAP-Hi instrumentRelated to the IMAP-Hi instrumentIns: LoRelated to the IMAP-Lo instrumentRelated to the IMAP-Lo instrumentIns: UltraRelated to the IMAP-Ultra instrumentRelated to the IMAP-Ultra instrumentMapper ToolsWork related to common mapper toolsWork related to common mapper toolsPhase E: Parent IssuePhase E major task indicatorPhase E major task indicatorPlannedTasks originally committed for the monthTasks originally committed for the month
Milestone
Metadata
Metadata
Assignees
Labels
Ins: HiRelated to the IMAP-Hi instrumentRelated to the IMAP-Hi instrumentIns: LoRelated to the IMAP-Lo instrumentRelated to the IMAP-Lo instrumentIns: UltraRelated to the IMAP-Ultra instrumentRelated to the IMAP-Ultra instrumentMapper ToolsWork related to common mapper toolsWork related to common mapper toolsPhase E: Parent IssuePhase E major task indicatorPhase E major task indicatorPlannedTasks originally committed for the monthTasks originally committed for the month
Type
Projects
Status
Todo
Algorithm Description:
A temporary method for setting the map
epochandepoch_deltavalues has been implemented in the ena_maps.AbstractSkyMap.project_pset_values_to_map()` method. It just keeps track of the min and max epoch from psets that get projected to the map.@nkerman pointed out that the end epoch should really be the end of the final PSET that is included instead of the start which is what is in the
epochvariable. This ticket should fix that by either addingepoch_deltato all PSET products and getting the end epoch fromend_epoch = epoch + epoch_delta, or we should keep track of the min and max pointing numbers. Using those we can query for the min pointing start time and max pointing end time to set the mapepochandepoch_deltavalues.See PR discussion here:
Originally posted by @nkerman in #1743 (comment)