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

Support flexibility in cookbook names #258

Open
bberkeyU opened this issue Apr 15, 2024 · 0 comments
Open

Support flexibility in cookbook names #258

bberkeyU opened this issue Apr 15, 2024 · 0 comments
Assignees
Labels
enhancement new feature
Milestone

Comments

@bberkeyU
Copy link
Contributor

We need a better way to handle cookbook names. This would allow more flexibility in cookbook names for more tailored observing programs while still allowing appropriate data to bubble through the L1/L2 pipelines and show up on the webpage.

For example, we broke the "synoptic" program during the eclipse into old and new line programs. o that we could run the old (1074,1079,789,673) lines multiple times and the new lines only once; we didn't take the new program, but if we did, all nine wavelengths should have been treated as synoptic if we took it.

One possible solution would be to call the program with the most (non-wave) files for a particular wavelength and call that synoptic. Alternatively, we could use some metric that uses the number of non-wave files and points across the emission line.

@mgalloy mgalloy self-assigned this Apr 15, 2024
@mgalloy mgalloy changed the title Support flexibility in cookbook names. Support flexibility in cookbook names Apr 15, 2024
@mgalloy mgalloy added the enhancement new feature label Apr 15, 2024
@mgalloy mgalloy added this to the 1.1 reprocessing milestone Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new feature
Projects
None yet
Development

No branches or pull requests

2 participants