Closed bhilbert4 closed 11 months ago
@JeffValenti I think I can put together a workaround notebook that could be used today. There are pipeline code changes that are tied to the new specwcs files, so users would have to install the pipeline from the master branch on github, and then they would need to point to the CRDS TEST server in order to see the new specwcs files. I assume the latter half of that is possible, but I'm checking with Rossy to confirm that the files on the TEST server are publicly accessible.
Adds a very basic notebook that shows the user how to run the spec2 and tso3 pipelines in order to reprocess data when new specwcs files are available.
The notebook assumes that the new reference files are in CRDS, and that they will be downloaded and used when the pipeline is called. There is no manual specification of the reference file names in the pipeline calls.
Corresponds to the single NIRCam grism time series issue on the "Known Issues with JWST Data Products" page.