Announcing the Aerospace ADL Front End

houchin · Post by **houchin** » Tue Oct 25, 2011 1:23 pm

Hi all,

Aerospace has produced a command line front end for ADL 3 (withMetadata mode) that we are now making available to the rest of the community. The front end scripts allow an analyst to easily run a specific input file through ADL, either using default LUT/PC files, or to overriding specific files (such as when experimenting with a new LUT file). The tools consist of of several scripts, a database (files and links on disk) of default input sets, and a specially configured version of ADL to control such things as log file output and custom guide lists.

For example, if I want to run a specific VIIRS RDR file through the SDR Viirs Controller up through just VIIRS calibration, the command would be:

Code: Select all

adl v/control -gl rdrtocal -od mycaloutput rdr=/rdr/RNSCA-RVIRS_npp_d20100906_t1539234_e1540488_b00009_c20110726162409419277_noaa_ops.h5

These tools should theoretically support sensors other than VIIRS, but they have been tested only on the VIIRS portions of ADL. Analysts of the other sensors will need to create your own configuration templates for those algorithms.

To get the tools, you will need to check them out of CasaNOSA subversion, through the VIIRS Early Access project
Main project trunk:
https://casanosa.noaa.gov/svn/viirs_ear ... k/aero/adl

1.0 release:
https://casanosa.noaa.gov/svn/viirs_ear ... ro/adl/1.0

Documentation for the main front end script can be found by "adl -h" or in the file scripts/README_adl.txt. It is suggested you skip down below the definition of the command line options and start reading there, then go back to read the option syntax information. Also see the two documents in the doc folder.

If you want to run on GRAVITE and want to save yourself the trouble of making your own install, you are free to point yourself at the Aerospace installation there, in /apps/user/aero/adl. If you "source /apps/user/aero/etc/cshrc" from your .cshrc file, you will get all of the required environment variables.

Note that these tools do not require you load the complete ADL environment from your shell initial setup, as having the wrong stuff in something like LD_LIBRARY_PATH for a different tool can cause other problems. Whenever needed, the tools themselves load the ADL environment before running an ADL executable.

If you have questions or get lost, feel free to contact me.