Package Contents | ||||||
|
-h
to request help (usage description) -c
to override the default character # used to indicate comment lines in data files -o
to specify an output file (default: standard out) -v
to request more informative output messages (verbose)
char | a single character (usually a letter or digit) |
string | a string (if there are blanks, enclose the string in quotes) |
file | essentially a string specifying a valid file name |
int | an integer |
float | a real number (e.g. 3.14 or 1.23e45) |
(the "d" or "D" for the exponent of 10 is not allowed) | |
interval | two (usually real) numbers separated by comma (no blanks!) |
lbl2xs -p 1013,800,500
lbl2xs -p '1013, 800, 500'
)
-o
option is used to specify the extension of the output file(s) -o
option)
The executable scripts are in ../bin (relative to this doc directory!)
To add this directory to your search path, you have to change the shell's PATH variable, e.g.
setenv PATH ${PATH}:${py4catsHome}/bin
or
setenv PATH ${py4catsHome}/bin:${PATH}
Here ${py4catsHome} denotes the directory where you have stored the package
(something like /a/very/long/path/to/py4cats/).
(For the bash or korn shell use the equivalent export command). Ideally add this statement to your .tcshrc (or .cshrc or .bashrc) file, because otherwise you have to redo this statement whenever you start a new terminal/console.
Note that the executables in this bin directory should be symbolic links to the corresponding scripts in the src directory (with the .py extension omitted).
If these links did not survive the packing and unpacking to/from the tarball, you can restore them by, e.g.,
cd bin; ln -s ../lbl/lbl2xs.py lbl2xs
(Also see the 1.ReadMe file in the bin directory.)
(Strictly speaking the change of the search path is not required.
You can always start a script by giving the full path name, e.g.
/a/very/long/path/to/py4cats/bin/lbl2xs
or equivalently
/a/very/long/path/to/py4cats/src/lbl2xs.py,
but thats boring, not really fun, ....)
Ideally the Py4CAtS scripts should run on any computer.
Well, almost any, of course you should have Python along with numpy
(and scipy occasionally ....).
In order to save the optical depth data using netcdf format, you also need an appropriate module
such as Scientific.IO.NetCDF
(from K. Hinsen's ScientificPython;
Alternatively pynetcdf might help ....).
For plotting (e.g. atmospheric data, line data, spectra) you need matplotlib.
(Alternatively lines can be plotted with ACE/gr = xmgr
using the plot_atlas script or its aceGr_atlas function;
Both scripts have slightly different capabilities (pro's and con's), but none is perfect!)
© fgs (+49-8153-28-1234)
Fri Jan 15, 2021; 12:34