This page links to tools used for NorESM model evaluation.

The diagnostics packages are currently available on NIRD. Each package can be run/configured from the command line using the program diag_run:

-------------------------------------------------
Program:
/projects/NS2345K/noresm_diagnostics/bin/diag_run
Version: 171123
-------------------------------------------------
Short description:
diag_run is used to configure and run the NorESM diagnostic packages.
 
Basic usage:
diag_run -m [model] -c [test case name] -s [test case start yr] -e [test case end yr] # Run model-obs diagnostics
diag_run -m [model] -c [test case name] -s [test case start yr] -e [test case end yr] -c2 [cntl case name] -s2 [cntl case start yr] -e2 [cntl case end yr] # Run model1-model2 diagnostics
nohup /projects/NS2345K/noresm_diagnostics/bin/diag_run -m [model] -c [test case name] -s [test case start yr] -e [test case end yr] &> out & # Run model-obs diagnostics in the background with nohup
 
Command-line options:
-m, --model=MODEL                             Specify the diagnostics package (REQUIRED).
                                              Valid arguments:
                                                cam  : atmospheric package (AMWG)
                                                clm  : land package (LMWG)
                                                cice : sea-ice package
                                                all  : configure all available packages (currently cam, clm and cice; micom and pop are still in development).
-c, -c1, --case=CASE1, --case1=CASE1          Test case simulation (OPTIONAL).
-s, -s1, --start_yr=SYR1, --start_yr1=SYR1    Start year of test case climatology (OPTIONAL).
-e, -e1, --end_yr=EYR1, --end_yr1=EYR1        End year of test case climatology (OPTIONAL).
-c2, --case2=CASE2                            Control case simulation (OPTIONAL).
-s2, --start_yr2=SYR2                         Start year of control case climatology (OPTIONAL).
-e2, --end_yr2=EYR2                           End year of control case climatology (OPTIONAL).
-i, -i1, --input-dir=DIR, --input-dir1=DIR    Specify the directory where the test case history files are located (OPTIONAL).
                                              Default is --input-dir=/projects/NS2345K/noresm/cases
-i2, --input-dir2=DIR                         Specify the directory where the control case history files are located (OPTIONAL).
                                              Default is --input-dir=/projects/NS2345K/noresm/cases
-o, --output-dir=DIR                          Specify the directory where the package(s) should be installed (OPTIONAL).
                                              Default is --output-dir=/scratch/johiak/noresm_diagnostics
-p, --passive-mode                            Run the script in passive mode: the diagnostic script will be configured but not executed (OPTIONAL).
-t, --type=TYPE                               Specify climatology or time series diagnostics (OPTIONAL): valid options are --type=climo and --type=time_series.
                                              Default is to run both. Note that the time series are computed over the entire simulation.
-w, --web-dir=DIR                             Specify the directory where the html should be published (OPTIONAL).
                                              Default is --web-dir=/projects/NS2345K/www/noresm_diagnostics
 
Examples:
diag_run -m all -c N1850_f19_tn11_exp1 -s 21 -e 50 # model-obs diagnostics of N1850_f19_tn11_exp1 for all (available) components.
diag_run -m cam -c N1850_f19_tn11_exp1 -s 21 -e 50 -w /path/to/my/html # model-obs diagnostics for CAM, publish the html in /path/to/my/html.
diag_run -m cice -c N1850_f19_tn11_exp1 -s 21 -e 50 -p # configure (but do not run) model-obs diagnostics for CICE.
diag_run -m clm -c N1850_f19_tn11_exp1 -s 21 -e 50 -i /input/directory1 -c2 N1850_f19_tn11_exp2 -s2 21 -e2 50 -i2 /input/directory2 # model1-model2 diagnostics for CLM with user-specified history file directories
diag_run -m clm -c N1850_f19_tn11_exp1 -s 21 -e 50 -t climo # model-obs climatology diagnostics (no time series) for CLM:
diag_run -m cam -o /my/dir # install CAM diagnostics in /my/dir with minimal configuration.

Report any problems, comments or suggestions to Johan Liakka: johan.liakka@nersc.no

(NEW 2015.04.23) First version of MICOM diagnostic package is available on grunch/norstore/hexagon/vilje. Please find more details here.

(NEW 2015.04.23)

The NorESM Diagnostic Packages can be downloaded via svn using the command:

svn export svn://noresg.norstore.no/NoresmDiagnosticPackages

A web-viewer is available at https://webserver1.norstore.uio.no:8443/websvn/wsvn/NORESG-diagpacks (user: guestuser, passw: friendly).

In both the default CAM5-aerosol packages (MAM3,MAM7) and the Oslo-aerosol packages, the budget terms can be taken out using a variable in the namelist :

&phys_ctl_nl
history_aerosol = .true.
/

Two more diagnostics are useful:

• Enable estimates multiple calls to radiation which are necessary for effective radiative forcing estimates
• Enable diagnostics for AEROCOM

To enable this, take the file cam/src/physics/cam_oslo$ vim preprocessorDefinitions.h and copy it to your SourceMods/src.cam folder

Change both preprocessor definitions to true

#define AEROCOM
#define AEROFFL

The AEROCOM-token turns on diagnostics needed for AEROCOM The AEROFFL-token tells the model to do additional radiation-diagnostics for aerosol indirect effect

Running with budgets activated will produce the following terms in the monthly output files:

Note: Since 3D-emissions and and gas washout rates are included in the term GS_{Tracer} in the mozart chemistry solver, the individual terms can be found like this (example for SO2):

ncap2 -O -s GS_ONLY_SO2=GS_SO2-WD_A_SO2-SO2_CLXF infile.nc outfile.nc

More info on SO2 budgets (see /models/atm/cam/tools/diagnostics/ncl/ModIvsModII/ for scripts with info on all tracers):

GS_SO2 contains the SO2 budget terms for all that goes on in the chemistry-routine, which is
1) Gas phase chemistry, 2) Wet deposition, and 3) 3D-emissions.
Gas phase chemistry is both production from DMS (GS_DMS) and loss through OH (GL_OH)
For calculations of net loss, e.g. used to calculate SO2 life-times, we're interested in the
loss through OH from the chemistry-term (GL_OH).
GS_SO2 = GL_OH + SO2_CLXF - WD_A_SO2 - GS_DMS*64/62
or
GL_OH = GS_SO2 - SO2_CLXF + WD_A_SO2 + GS_DMS*64/62

Estimating chemical loss w.r.t. S (instead of SO2 or DMS), for comparison with CAM4-Oslo numbers:
net chemial loss gas phase = (GS_SO2/1.998 - SO2_CLXF + WD_A_SO2)/1.998 + GS_DMS/1.938
net chemical loss = net chemial loss gas phase + AQ_SO2/1.998

Finally, total net loss (used to calculate life-time = -load/(net loss), where load = cb_SO2/1.998):
net loss =
- WD_A_SO2/1.998 ;wet deposition in kg/m2/sec (positive in output file)
- DF_SO2/1.998 ;dry deposition in kg/m2/sec (positive in output file)
+ AQ_SO2/1.998 ;wet phase production of SO4 in kg/m2/ses (negative in output file)
+ (GS_SO2 - SO2_CLXF + WD_A_SO2)/1.998 + GS_DMS/1.938 ; net chemical loss gas phase

• Go to the directory models/atm/cam/tools/diagnostics/ncl/budgets
• Change the filename to use in the file budgets.ncl (“myFileName” around line 18). Should be for example yearly average of month-avg file in a run with budgets
• Run the script budgets.sh to create a pdf-file (output.pdf)

• Make a local copy (on Linux) of the directory models/atm/cam/tools/diagnostics/ncl/ModIvsModII
• Assuming that you have produced output data from 4 simulations: two different model versions, each with PD and PI emissions, and all run with #define AEROCOM & AEROFFL:
• In ModIvsModII.csh (note: read the header info):
• - edit model info for the first model (shown to the left in the plots): modelI = CAM4-Oslo or modelI = CAM5-Oslo ?
• - provide paths and partial file names of the model data (PD and PI) for Model I (CAM4-Oslo or CAM5-Oslo) and Model II (must be CAM5-Oslo)
• - choose desired plot format (plotf=ps, eps, pdf or png)
• Run the script: ./ModIvsModII.csh
• Furthermore, to display the plots in an organized form by use of a web browser (only possible if the chosen plot format is png):
• - download htm template files from ftp://ftp.met.no/projects/noresmatm/upload/NorESM2Diagnostics/ModIvsModII/htm-templates/
• - edit general model info (only) in ModIvsModII.htm, and manually cut and paste the mass budget numbers from the script output into this file
• - copy all png (plots) and htm files to the desired output (common) directory
• - open ModIvsModII.htm in your browser: hyper-links to all other htm files, including plots, are found here
• Example: ftp://ftp.met.no/projects/noresmatm/upload/NorESM2Diagnostics/ModIvsModII/revision610inclSOA-Nudged_1984-12to1985-11_vs_CAM4-Oslo/ModIvsModII.htm

To switch on extra output for cloud diagnostics (mass and number tendencies for liquid water and mass) change the following namelist variable:

&phys_ctl_nl
history_budget = .true.
/

A python script for plotting the mass and number budgets for the cloud microphysics can be found under:

models/atm/cam/tools/diagnostics/ncl/cloudBudgets

in the same branch. Copy the script to your local computer or lustre and edit the script to read the correct input file(s) (instructions inside the script). Run the script by typing:

python scriptname.py

in your terminal.

To prepare output so that it is processed automatically by the aerocom tools, use the script located at models/atm/cam/tools/aerocom/ in the svn repository. The script prepares files such that the idl aerocom tools prepare plots for the aerocom webinterface: URL link to NorESM on AeroCom webinterface

The script requires <ModelName>_<ExperimentName> and <Period> as input.

<Period>: for a climatological average and run choose 9999 , for nudged simulations choose the year of the meteorology

<ModelName>_<ExperimentName>: is the dataset identifier under which the plots appear on the AeroCom webinterface
in the required format NorESM-CAM5_svn{RevisionNumber}_YYMMDD{initials}_Freetext.

Example: “NorESM-CAM5_svn1094_151201AG_CMIP6endelig”
Initials AG: Alf Grini, AK: Alf Kirkevåg, DO: Dirk Olivie…

Where the date YYMMDD corresponds to the time when the AeroCom data preparation script has been executed.

The script creates files named like

“aerocom3_<ModelName>_<ExperimentName>_<VariableName>_<VerticalCoordinateType>_<Period>_<Frequency>.nc”

<ModelName> ⇒ eg NorESM-CAM53
<ExperimentName> ⇒ svn{RevisionNumber}_YYMMDD{initials}_Freetext
<VariableName> ⇒ aerocom variable names
<VerticalCoordinateType> ⇒ “Surface”, “Column”, “ModelLevel”, “SurfaceAtStations”, “ModelLevelAtStations” 
<Period> ⇒ eg “2008”, “2010”, “9999”
<Frequency> ⇒ “timeinvariant”,”hourly”, “daily”, “monthly”, “sat1000”, “sat1330”, “sat2200”, “sat0130”

Note that VerticalCoordinateType is dependent on the variable!! It is not a question about “vertical coordinate type used in model simulations”!

The script copies files on norstore into /projects/NS2345K/CAM-Oslo/DO_AEROCOM/<ModelName>_<ExperimentName>/renamed/

ESMVALtool http://www.geosci-model-dev-discuss.net/8/7541/2015/gmdd-8-7541-2015-discussion.html

cis tools http://www.cistools.net

JASMIN http://www.jasmin.ac.uk/services/jasmin-analysis-platform/