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

File control for MIRI Offs #10

Closed
low-sky opened this issue Mar 14, 2023 · 1 comment
Closed

File control for MIRI Offs #10

low-sky opened this issue Mar 14, 2023 · 1 comment

Comments

@low-sky
Copy link
Contributor

low-sky commented Mar 14, 2023

Develop control method at the TOML level to control custom MIRI offs.

@thomaswilliamsastro
Copy link
Collaborator

I think this exists as of v0p7p3, you can pull in extra observations like:

[extra_obs_to_include.ic5332]
ngc7496 = [
    'jw02107041001_0?2',
]

In this case, these are the OFF observations for 7496, which we include for the IC5332 data. If you want control over how we decide whether things are OFFs or not, there's

bgr_check_type = 'parallel_off'
bgr_background_name = 'off'
bgr_observation_types = [
    'miri',
]

bgr_check_type is either 'parallel_off' (it will use parallel MIRI observations as offs, as in the PHANGS setup), or 'check_in_name', where it will look for 'bgr_background_name' to match in the target name (this is what we do for the M33 obs). The 'bgr_observation_types' are nircam/miri, so we can switch this on and off per instrument

@low-sky low-sky closed this as completed Oct 12, 2023
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

2 participants