Metadata-Version: 2.4
Name: piratical
Version: 0.3.0
Summary: Plunder spectra from the JWST NIRSpec archive
Home-page: https://bagpipes.readthedocs.io
Author: Adam Carnall, Ho-Hin Leung
Author-email: adamc@roe.ac.uk
Project-URL: GitHub, https://github.com/ACCarnall/piratical_pipeline
Requires-Dist: numpy<=2.2
Requires-Dist: pandas
Requires-Dist: astropy
Requires-Dist: matplotlib>=2.2.2
Requires-Dist: scipy
Requires-Dist: mastquery
Requires-Dist: jwst<=1.20.2
Dynamic: author
Dynamic: author-email
Dynamic: description
Dynamic: home-page
Dynamic: project-url
Dynamic: requires-dist
Dynamic: summary

NIRSpec Piratical Pipeline
--------------------------

Plunder spectra from the JWST archive.


FAQ/things to note
------------------

Q: Code won't run, pipeline crashes

A: Based on our testing the most likely cause for this is incompatible/bugged versions of one or more of the STScI python packages the jwst pipeline depends on. For starters, the pipeline is currently incompatible with python 3.14, so I'd recommend using python 3.13. STScI is also in the process of releasing v2.0.0 of the JWST pipeline which will undoubtedly cause chaos. For now I've required version lesseq 1.20.2 of the JWST pipeline, which seems stable. Some more-specific cases are dealt with below.

....................

Q: I'm getting errors that say something about the CRDS server connection failing

A: To run the JWST pipeline you need to set some environment variables so the pipeline can download calibration files, details available here: `here <https://jwst-pipeline.readthedocs.io/en/latest/jwst/user_documentation/reference_files_crds.html#crds-servers>`_. Sometimes the CRDS server seems to go down and you might need to wait a few hours to be able to connect to it again.

....................

Q: A step in the pipeline is failing, potentially saying something about missing ASDF?

A: You might have a partially downloaded rate or uncal file (depending on whether you're skipping the L1 pipeline or not). Look in the uncal_files or rate_files directory for one or more files that are smaller than the others, try deleting them and running again. In the longer term we'll try to write something into the pipeline to automatically detect this.
