The Atmospheric Infrared Sounder (AIRS) was launched in 2002 on board the Aqua satellite. From the NASA website (http://airs.jpl.nasa.gov/):
"AIRS uses cutting-edge infrared technology to create 3-dimensional maps of air and surface temperature, water vapor, and cloud properties. With 2378 spectral channels, AIRS has a spectral resolution more than 100 times greater than previous IR sounders and provides more accurate information on the vertical profiles of atmospheric temperature and moisture. AIRS can also measure trace greenhouse gases such as ozone, carbon monoxide, and methane. AIRS and AMSU-A share the Aqua satellite with the Moderate Resolution Imaging Spectroradiometer (MODIS), Clouds and the Earth's Radiant Energy System (CERES), and the Advanced Microwave Scanning Radiometer-EOS (AMSR-E). Aqua is part of NASA's "A-train", a series of high-inclination, Sun-synchronous satellites in low Earth orbit designed to make long-term global observations of the land surface, biosphere, solid Earth, atmosphere, and oceans."
In previous posts we have described DAS setups that exclude AIRS data. That's because we selected a date (19980302) for which no such data existed.
To use AIRS data we need need to set up a simulation with a more recent date. The following settings produce a working simulation:
FVICS? /discover/nobackup/projects/gmao/share/dkokron/restarts Starting year-month-day?  20040615
All the other settings should be similar to the ones described in https://modelingguru.nasa.gov/clearspace/blogs/geos5/2008/06/04/running-a-geos5- das-merra-simulation
After we submit a DAS job as follows:
You may notice, at the beginning, that your job queue looks something like this:
711708.borgmg ccruz general g5das.2004 2831 17 68 3892mb 08:00 R 00:02 711710.borgmg ccruz datamove acq.040616 31869 1 1 3892mb 01:00 R 00:02
The job on the datamove queue is retrieving the observational data for the DAS simulation. Since these data is archived in mass storage, sometimes the job length (1hr) may not be enough to retrieve all the data before time expires. As a result the job will start with an incomplete data stream and it may (or may not fail). If that is the case then simply resubmit the g5das.j job. By the second submission most of the data will have been (hopefully!) de-migrated and the "acquire" process will be much quicker.