Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add MA table reference file #461

Open
tddesjardins opened this issue Oct 4, 2024 · 1 comment
Open

Add MA table reference file #461

tddesjardins opened this issue Oct 4, 2024 · 1 comment

Comments

@tddesjardins
Copy link

To better keep in sync the versions of the multi-accumulation (MA) tables used by various simulation tools at the SOC as well as by the romancal pipeline, we request a new type of reference file to capture this information. I welcome comments on this issue for how best to format the file, but I'm going to sketch out an initial suggestion here. Note that ref_common includes ROMAN.META.INSTRUMENT.DETECTOR, but this would apply to all detectors...I guess we can just always put WFI01? We're not going to match on it, so we don't need to put a p_ keyword for this, just a placeholder.

CRDS Selectors:

  • ROMAN.META.EXPOSURE.START_TIME

Schema:

title: WFI Multi-Accumulation (MA) Tables

type: object
properties:
     meta:
          allOf:
               - $ref_common
               - type: object
                     properties:
                          type: string
                         enum: [MATAB]
     ma_table:
          title: Multi-Accumulation (MA) Table Readout Patterns
          description: Readout specifications of the multi-accumulation (MA) tables.
          type: object
          patternProperties:
               ??? - Need to put the MA table ID numbers here...can we leave this general to any integer 1 – 99?
               type: object
               properties:
                    read_pattern:
                         title: Readout Pattern
                         description: The enumeration of detector reads to resultants making up the Level 1 ramp data cube. The read pattern is nested such that each grouping of read numbers represents a resultant. For example, a readout pattern of [[1], [2, 3], [4]] consists of four reads that were downlinked as three resultants with both the first and last resultant each containing a single read.
                         type: array
                         items:
                             type: array
                             items:
                                 type: integer
     timing:
          title: Detector Readout Time (s)
         description: The readout time per observing mode in seconds of the Wide Field Instrument (WFI) detectors. This represents the time between the start and end of the readout. The difference in readout times is governed by the guide window mode in use, which is tied to the observing mode.
         patternProperties: 
                "^(WFI_IMAGE|WFI_GRISM|WFI_PRISM|WFI_WFSC)$":
                       frame_time:
                            title: Detector Readout Time (s)
                            description: The readout time in seconds of the Wide Field Instrument (WFI) detectors. This represents the time between the start and end of the readout.

Questions:

  1. What does exposure type WFI_WFSC represent? There are differences in the frame times between WFI imaging, WFI spectroscopy, large defocus, and moderate defocus modes. Expect these to change, but in last PRD this was 3.04, 4.03, 4.41, and 6.40 seconds, respectively). Does WFI_WFSC correspond to one of the defocus modes? Both? We may need to think about this...
@tddesjardins
Copy link
Author

cc from RTB @rcosenti-stsci and @wcschultz in addition to the usual RCAL folks @schlafly , @PaulHuwe , @ddavis-stsci , @nden .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant