kmhess / SoFiA-image-pipeline

Generate figures of spectral line sources, for publication or quick inspection, based on SoFiA-2 output catalog and fits files.
GNU General Public License v3.0
16 stars 7 forks source link

Generalize to other spectral lines #1

Open kmhess opened 2 years ago

kmhess commented 2 years ago

CO immediately comes to mind, but maybe OH 1667/1665 as well.

mctoribio commented 3 months ago

This is potentially useful information on how to query for spectral lines in splatalogue.

The python package SpectralCube already does that in this function: https://spectral-cube.readthedocs.io/en/latest/api/spectral_cube.SpectralCube.html#spectral_cube.SpectralCube.find_lines

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): https://learn.astropy.org/tutorials/SpectralCubeReprojectExample.html

"...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.

cube1.find_lines(chemical_name=' H2CS ').show_in_notebook()

The tutorial covers all these steps applied to ALMA datacubes:

Step 1: Download Step 2: Open files, collect metadata Step 3: Convert to velocity Step 4: Spectral Interpolation Step 5: Spatial Smoothing Step 6: Reprojection

mctoribio commented 3 months ago

This paper may be relevant for this purpose

Automated Spectroscopic Detection And Mapping Using ALMA and Machine LearningTechniques Cocke et al. 2020

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.