Next: USE /ASTRO
Up: LINEDB Language Internal Help
Previous: Language
Contents
USE
LINEDB\USE IN|OUT|BOTH dbname1 [[dbname2] [dbname3...]] [/ASTRO]
[/OVERWRITE]
Define the atomic and molecular line database(s) used as input and/or
output.
Input databases can be either an existing filenames or a database avail-
able through internet. Recognized internet databases are
JPL the JPL molecular spectroscopy database
CDMS the Cologne Database for Molecular Spectrocopy
These names can thus not be used as database filenames.
The input file is tested to determine whether it is a valid SQLITE data-
base. If not, it is assumed to be an ASCII file following the JPL data
format, see e.g.
https://spec.jpl.nasa.gov/ftp/pub/catalog/README, and
https://spec.jpl.nasa.gov/ftp/pub/catalog/catdir.html
for reference and examples. In this case, the log10 of the partition
functions of all the referenced species must be provided in a file named
"partfunc.cat", with at least the 300K value. See ker-
nel/python/linedb/demo/demo-53001.cat and kernel/python/linedb/de-
mo/partfunc.cat in the Gildas sources for a complete example.
Multiple input databases can be used together. However, only one output
database can be defined at a given time. The OUT and BOTH keywords ap-
plies only to SQLITE databases. The /OVERWRITE option implies that the
output database is first removed. The absence of the option implies that
any subsequent call to the INSERT command will append lines to the al-
ready existing output database.
After execution of the command, the name of the input databases is saved
in the list LINEDB%DBIN. For symmetry, the name of the output database
is saved in the list LINEDB%DBOUT (with a single element in this case).
Subsections
Gildas manager
2023-06-01