/jwst-sources

Repository to keep track of individually published JWST sources, high-z or otherwise

Primary LanguagePythonMIT LicenseMIT

jwst-sources

Repository to keep track of individually published JWST sources, high-z or otherwise

Notes

  • Add a new reference with a csv and meta file in the ./tables directory.
  • Use tables/template.meta for an example metadata file
    • meta files should have at a minimum, arxiv and author keys
    • meta files are read as YAML
    • ':' characters are special to YAML and not allowed in the parameter value strings. Change them to, e.g., commas in long paper titles.
  • csv files should have at a minimum, id, ra, dec columns, and ideally also zphot and/or zspec.
    • ra, dec are intepreted as decimal degrees and should have a minimum of 6 and 5 decimal places, respectively
    • Alternatively, rah and decd columns can be provided with coordinates in sexagesimal format (HH:MM:SS.SS, DD:MM:SS.SS)
  • grizli is a requirement, but a basic installation with pip install grizli should be enough without all of its dependencies

Test generating the master table with

$ python build.py

Adding new references

Please feel free to add new tables with meta and csv files in the tables/ directory! To add them, fork the repository and submit the updates via a Pull Request. Please verify that new tables are processed correctly with the $ python build.py ingestion script before committing updates to the full jwst-sources tables. The ingestion script will also be run automatically by the GitHub Actions CI script when a PR is processed.

If there is self-contained code used to generate a particular csv file (e.g., 2306.02468-hainline.py), please feel free to add that as well. Though note that any python scripts have to pass the verification test in the CI Action, i.e.,:

flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics --exclude "scripts* docs* dist* examples*"

App interface

The table is rendered in at https://jwst-sources.herokuapp.com/, with some tools for querying and generating the unique source identifiers. See https://jwst-sources.herokuapp.com/help.

To Do

  • Add function to query for matches in a local test table
  • add keywords to meta, like keywords: highz, quiescent
  • Add vizier tag to meta files if the full tables eventually exist
  • Build heroku app
    • Query for existing sources around a test position
    • Build a jname for a given RA/Dec
    • Display the table itself