Aspen can process data provided in many formats, including AVAPS Dropsonde, NCAR EOL, HRD FRD, and WMO TEMP formats. It is able to analyze both dropsonde and upsonde soundings.
Aspen is designed to operate as automatically as possible, while allowing the user to fine tune the quality control algorithms. For instance, as soon as the user selects a sounding file for processing, the data is brought into Aspen and automatically analyzed. In most cases this first pass will be the only step required. If the processing needs to be modified, the user can change the QC parameters and reprocess the data as many times as necessary.
An extensive series of QC algorithms is applied to the data. These algorithms typically have one or two parameters that may be adjusted by the user if the default values are not suitable for a particular sounding. The user can save the modified options, so that the initial analysis of a new sounding will use the customized QC parameters.
Aspen can have a large number of input files open at the same time. This makes it convenient to compare soundings. Output results can be formatted as printed text and graphics, and saved in graphics, ASCII, CSV, and netCDF files.
The synoptic map capability is particularly useful for detecting anomalous observations during operational sounding activities. It allows a collection soundings to be compared from a geographic perspective. This can very quickly reveal discrepancies in calculated pressure heights and other sensor malfunctions.
History
Aspen is derived from the Editsonde software developed at the National Hurricance Center's Hurricane Research Division (HRD). It has progressed through four versions:
- V1 - The Fortran Editsonde package was wrapped in Visual Basic, in order to provide a graphical interface and MS Windows compatibility.
- V2 - The entire package was rewritten in C++, with graphics implemented using the Microsoft Foundation Classes.
- V3 - The graphics were ported to the Qt toolkit, in order to support Linux, OSX and MS Windows, using an identical code base.
- V4 - The package was significantly updated to work with the next generation ACS dropsonde control software.
Aspen version 4 is the current release, and is under active development. The current release series is V4.1.
Command Line Versions (Aspen-QC)
The Aspen quality control processing can also be performed by a command line program, which does not provide a graphical user interface. This program is named Aspen-QC, to signify that it only performs the quality control processing, without providing a user interface.
The output products are specified with command line switches. This can be useful for scripted processing, but as always with automated processing, care must be taken to validate the results.
The quality control parameters are specified in the aspen.xml file, which is same underlying configuration mechanism used by the graphical version of Aspen. The most convenient way to modify these parameters is to run Aspen and use its configuration editor to change parameters, and then copy that aspen.xml file to the directory containing the Aspen-QC program. The directory containing aspen.xml is shown in the status bar at the bottom of the Aspen display.
Documentation and Help
The user manual is accessible from within the Help menu when running Aspen. Its content is also hosted online:
AspenDocs documentation site
For help or questions, please contact eol-aspen[at]ucar[dot]edu.
When referencing the NCAR/EOL ASPEN software in publications or presentations, please use the citation:
Martin, C. and Suhr, I. (2026). NCAR/EOL Atmospheric Sounding Processing ENvironment (ASPEN) software version 4.0.6. https://doi.org/10.26023/3MXP-4C54, 2026.
Please update the access date and the software version you used in the citation.