-
Notifications
You must be signed in to change notification settings - Fork 7
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
Generalize to other spectral lines #1
Comments
This is potentially useful information on how to query for spectral lines in splatalogue. The python package SpectralCube already does that in this function: And in the following tutorial using ALMA they show an example on how to call it, including how to use dask to parallelise it (at the end of the page): "...We use the find_lines tool to query splatalogue with astroquery over the spectral range covered by the cube. It returns a table of matching lines. Note that some line names will be repeated because Splatalogue includes several different databases and most chemical species are present in all of these.
The tutorial covers all these steps applied to ALMA datacubes: Step 1: Download |
This paper may be relevant for this purpose Automated Spectroscopic Detection And Mapping Using ALMA The code behind the processes was originally built in a Jupyter Notebook, but has since been modified to be compatible with Google Colab so that it may be used by anyone with an internet connection and the AutoSpec.ipynb file. Google Colab includes most of the standard python libraries already built-in. For the few non-standard libraries (Astroquery, Astropy), they are automatically installed in the Google Colab environment for use with the code. In this manner, the end user needs only to upload data to Google Colab, and run every cell. The output of the program is automatic and are the most probably set-cover combinations for whatever data has been fed into the program. In this way, any celestial object with spectral data gathered in a similar format to that used in our process will have the ability to be analyzed seemlessly. |
CO immediately comes to mind, but maybe OH 1667/1665 as well.
The text was updated successfully, but these errors were encountered: