• Search Icon

SSEC Home Atmospheric Emitted Radiance Interferometer AERI

  • Home
  • References
  • Contact
  • Knowledge Base
  • Research Support
  • UW
  • CIMSS
  • Data Services
  • AOSS Library
  • Partners
  • Careers
  • Disclaimer
  • Staff Directory
  • For Employees

TPSS Customization Options

Overview

All TPSS user customization options are located in the directory C:\Users\AERI\docker\config

 

 

VIP file

C:\Users\AERI\docker\config\vip.txt

The vip file contains all the parameters for running the AERIoe retrieval.
Notable parameters that may be modified by the user:

  • tres:  temporal resolution in minutes.  e.g.
    • tres=0 for retrievals at native AERI temporal resolution (highest)
    • tres=10 for retrievals every 10 mins
    • tres=60 for retrievals every 60 mins
  • cbh_default_ht:  default cloud base height in km AGL when no ceilometer data is present
    • chb_default_ht=2 is the default setting
    • Can adjust for local climatology
  • output_rootname:  root name of output file
  • output_path:  path of output directory
  • retrieve_lcloud:  retrieve liquid clouds
  • retrieve_icloud:  retrieve ice clouds
  • Global attributes for the output NetCDF file.  These must start with globatt_
    • globatt_Site=SITE
    • globatt_Instrument=AERI-118
    • globatt_Dataset_contact=Dave Turner, NOAA
    • globatt_Processing_comment=Test calculations

 

 

Local climatology

C:\Users\AERI\docker\config\prior.{mm}.cdf

  • A climatology (thermodynamic profile) is necessary at the location of observation for each month of the year in order to provide a solution space for the retrieval algorithm
  • For best results use mean monthly climatologies near the given observation site
  • If monthly climatolgy is not available, season or even yearly average climatology may be adequate
  • The prior file must have the name prior.{mm}.cdf , where {mm}=01-12 for each month of the year.
  • It’s best to use symbolic links to the actual climatology files

e.g.

mklink prior.01.cdf Xa_Sa_datafile.beijing.53_levels.month_01.cdf
mklink prior.02.cdf Xa_Sa_datafile.beijing.53_levels.month_02.cdf
mklink prior.03.cdf Xa_Sa_datafile.beijing.53_levels.month_03.cdf
mklink prior.04.cdf Xa_Sa_datafile.beijing.53_levels.month_04.cdf
mklink prior.05.cdf Xa_Sa_datafile.beijing.53_levels.month_05.cdf
mklink prior.06.cdf Xa_Sa_datafile.beijing.53_levels.month_06.cdf
mklink prior.07.cdf Xa_Sa_datafile.beijing.53_levels.month_07.cdf
mklink prior.08.cdf Xa_Sa_datafile.beijing.53_levels.month_08.cdf
mklink prior.09.cdf Xa_Sa_datafile.beijing.53_levels.month_09.cdf
mklink prior.10.cdf Xa_Sa_datafile.beijing.53_levels.month_10.cdf
mklink prior.11.cdf Xa_Sa_datafile.beijing.53_levels.month_11.cdf
mklink prior.12.cdf Xa_Sa_datafile.beijing.53_levels.month_12.cdf

 

 

Data transfer using rsync

C:\Users\AERI\docker\config\rsync_update.sh

  • The rsync protocol can be used to transfer AERI data onto the TPSS computer
  • rsync can be used for real-time incremental data transfers

Set the IP address of the AERI computer in this script

AERIIP=10.0.0.1
rsync -ar $AERIIP::ftp/AE$YYMMDD /data/raw/

The script can be customized as needed for the instrument and network being used.

UW Logo
1225 W. Dayton St. · Madison, WI 53706, USA · 608-263-6750