Exclude source-specific WFSS files from observation page #1651
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WFSS source specific files have started showing up on JWQL's observation level pages. I'm not sure how this happened. The filenames come in from the MAST query. Maybe the metadata examined by MAST has changed? This was leading to a lot of extra thumbnail placeholders being added to WFSS programs on the observation level pages. I don't think we want to keep track of these files, even though they are an output of the spec2 pipeline, and JWQL generally supports stage 2 outputs. In WFSS there is one file for each extracted source. By default the pipeline now keeps only the top 100 brightest sources per exposure. I think adding 100*n_exposures files to the page could quickly become overwhelming. Maybe if we come up with a better way to organize these, we can add them back in. They are 2D images of extracted spectra.
This is not tested yet.