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
Is your feature request related to a problem? Please describe.
The crop function in l3_to_l4.py currently assumes the input data is taken using the HLC mode, and raises an error if not.
Describe the solution you'd like
Expand the crop function to handle additional instrument modes, and adjust the default behavior of the crop function based on the mode. E.g. for the HLC mode, the crop function assumes by default that you want to crop to a region the size of the HLC dark hole, centered on the star position, so we should adjust the size of the crop region based on the dark hole size for a given mode. The header keywords for the star position would probably remain the same, but I'm not certain yet.
I think the size of the dark hole is essentially limited by the lyot stop, so we can determine what the behavior should be using the "LSAMNAME" keyword in the primary header.
Table 1 of this paper describes a bunch of possible modes and the associated Precision Alignment Mechanism (PAM) positions associated with them: https://arxiv.org/pdf/2108.05986
Is your feature request related to a problem? Please describe.
The crop function in l3_to_l4.py currently assumes the input data is taken using the HLC mode, and raises an error if not.
Describe the solution you'd like
Expand the crop function to handle additional instrument modes, and adjust the default behavior of the crop function based on the mode. E.g. for the HLC mode, the crop function assumes by default that you want to crop to a region the size of the HLC dark hole, centered on the star position, so we should adjust the size of the crop region based on the dark hole size for a given mode. The header keywords for the star position would probably remain the same, but I'm not certain yet.
I think the size of the dark hole is essentially limited by the lyot stop, so we can determine what the behavior should be using the "LSAMNAME" keyword in the primary header.
Table 1 of this paper describes a bunch of possible modes and the associated Precision Alignment Mechanism (PAM) positions associated with them: https://arxiv.org/pdf/2108.05986
And this page in the Confluence space outlines all the header keywords associated with the PAM: https://collaboration.ipac.caltech.edu/display/romancoronagraph/CFAMNAME%2C+DPAMNAME%2C+FPAMNAME%2C+FSAMNAME%2C+LSAMNAME%2C+SPAMNAME
The text was updated successfully, but these errors were encountered: