AirWare
air quality assessment & management
Reference and User Manual
     
      AirWare   On-line Reference Manual
        Release Level 6.2
        Release Date 2013 09
        Revision Level 1.0
      Last modified on:   Saturday, 7-Dec-13 21:22 CET

      Configuration of scheduled model runs

      The setup and configuration of
      1. CAMx Nowcast model scenarios (automatically uses previous results as initial conditions)
      2. CAMx Forecast model scenarios (automatically uses previous results as initial conditions)
      3. AERMOD Nowcast model scenarios
      consists basically of three steps:
      1. Generate the nowcast or forecast scenario
      2. Generate or edit the shell script in /var/www/cgi-bin/camx or /var/www/cgi-bin/aermod, resp.
      3. Make an entry into crontab

      generate a CAMx nowcast/forecast scenario

      ???

      generate an AERMOD nowcast scenario

      • generate an AERMOD NOx nowcast scenario:
        • Hourly Nowcast -> NOx (AERMOD)
        • button "new"
        • edit the name and click "save"
        • button "Domain": select a domain
      • generate an AERMOD SO2 nowcast scenario:
        • Hourly Nowcast -> SO2 (AERMOD)
        • button "new"
        • edit the name and click "save"
        • button "Domain": select a domain
        • select the substance: click on (the blue) NOx and select SO2 instead.

      crontab entries:

      /var/www/cgi-bin/aermod/run[APPLICATION]Nowcast.sh
      To add a new nowcast run, only the corresponding scenarioID needs to be added to the list of scenarioID's (line21)

      Scheduled run configuration

      The scheduled runs are configured in the following files: The file names are arbitrary, they only need to be the consistent with the filenames in the crontab.

      CAMx Nowcast:
      /var/www/cgi-bin/camx/run[APPLICATION]Nowcast.sh
      To add a new nowcast run, only the corresponding scenarioID needs to be added to the list of scenarioID's (line26)

      CAMx Forecast:
      /var/www/cgi-bin/camx/run[APPLICATION]NOxForecast.sh
      To add a new forecast run, make a copy, and substitute the scenarioID (line 4)

      In addition to the scenario ID the "run*.sh" files contain the following information (nothing needs to be changed here!):

        # database configuration file
        config="/var/www/cgi-bin/[APPLICATION]_db"

        # base directory of cgi's
        cgiDir="/var/www/cgi-bin/"

        # where to write log and error file
        errorFile="$path/camx/log/forecastNOx.error"
        logFile="$path/camx/log/forecastNOx.log"

        # base directory of output files
        outDir="$path/camx/forecast/"

        # where to find camx input files generated by mm5 (CAMx only)
        mm5Dir="/var/airdata/mm5/"

        # the simulation date (forecast only)
        tmw=`date -d tomorrow +'%Y-%m-%d'`

      Scheduling (crontab entries

      The runs are started via the following (root) crontab entries: (edit with:   crontab -e)

      #aermod
      mn * * * * /var/www/cgi-bin/aermod/run[APPLICATION]Nowcast.sh

      #camx
      mn * * * * /var/www/cgi-bin/camx/run[APPLICATION]Nowcast.sh mf hf * * * /var/www/cgi-bin/camx/run[APLICATION]NOxForecast.sh

      Any new CAMx forecast runs need to be added here.

      mn is the minute of nowcast start - depending on server time relative to location time (mn=1 or mn=31). If server time is equal to location time mn=1.

      mf is the minute, hf is the hour of forecast start, depending on the availability of MM5 results. It can be started as soon as MM5 results are available.

      Make sure that each of the Nowcast runs will be finished within an hour (for all scenarios included in the shell script). Otherwise th nowcast of the next hour will be aborted.

      Make sure that only ONE CAMx forecast is running at time. Otherwise the run which starts later will be aborted.


© Copyright 1995-2016 by:   ESS   Environmental Software and Services GmbH AUSTRIA | print page