ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Instructions for modellers for AeroCom 2018/2019 phase III CTRL and associated experimentsComments
2
Final deadline for AeroCom experiment wiki update and fixing of this diagnostics sheet: 8.2.2019
3
Performing the AP3-CTRL is needed to participate in AeroCom 2018/2019
4
5
AP3-CTRL: nudged with fixed SST, years at least 2010 and 1850, nudged with 2010 meteo, CMIP6 2010 and 1850 emissions
6
If possible: Simulate also year 1750 for this CTRL configuration
7
8
For GCMS, ESMs, (eg those participating in AerChemMIP/CMIP6) :
9
Possibly submit more than one "CTRL" experiments with different meteo configurations in addition to AP3-CTRL
10
Additional possible Meteo configurations:
11
fSST: Simulate 5 AMIP years for 1850 and 2010 and compute monthly averages
12
CPL: Average 20 years around 1850 and 2010 in historical simulation and compute monthly averages
13
14
Year in filenames reflects year of emissions
15
Subsequent sheets specify output
16
Tier 1 refers to a variable which is obligatory in an experiment
17
If tier 1 seems "not possible" in your model, do what you can (best guess), or document reasons why not in readme file
18
If tier 1 requests daily, and thats not possible, monthly becomes tier 1
19
Tier 2 are variables for which analysis is planned, but core analysis is possible without
20
21
See further submission instructions on aerocom wiki (https://wiki.met.no/aerocom/data_submission)
22
Provide one ascii readme file per Model and MeteoConfiguration, use also global netcdf attributes for further info
23
Use file checker from MetNo to check submission before submitting files (will be ready in January2019)
24
25
ModelVersionName and Directory on AeroCom database
26
Goal: assemble CTRL and all experiments from a given model version and meteo configuration in ONE directory
27
Directory name on AeroCom database will be: <ModelName>-<MeteoConfigSpecifier>
28
29
One file per year(Period), variable, coordinatetype, frequency
30
31
File granularity and Filenames
32
Filename template with <components>:
33
aerocom3_<ModelName>-<MeteoConfigSpecifier>_<ExperimentName>-<PerturbationName>_<VariableName>_<VerticalCoordinateType>_<Period>_<Frequency>.nc
34
Filenames shall have exactly 6 underscores in name
35
36
Examples
37
aerocom3_GOCARTv7.2_AP3-CTRL_od550aer_Column_2010_monthly.nc
38
aerocom3_GISS-MATRIX-met2010_AP3-ACRI-AFRICA_od550aer_Column_2010_daily.nc
39
aerocom3_GOCARTv7.2-met2010_AP3-CTRL-od550aer_Column_1850_monthly.nc
40
aerocom3_GISS-MATRIX-fSST_AP3-CTRL-od550aer_Column_1850_monthly.nc
41
42
43
44
45
Explanations of component
46
<ModelName> Modelname shall reflect model version, but dont make ModelName too long, Modelname can contain hyphens
47
<MeteoConfigSpecifiers> => "met2010" (default, nudged to 2010 meteo) / "fSST" (fixed 2010 SST monthly fields, not nudged) / "CPL" (coupled AOGCM model, not nudged) A MeteoSpecifier has to be present
48
<ExperimentName> possible "AP3-CTRL", "HIST", "ACRI", "UTLS", "ATOM", "INSITU"
49
<PerturbationName> see experiment descriptions on aerocom wiki, if required for the experiment, use exact case sensititve name from description
50
<VariableName> see diagnostics sheets variable name column ( NOTE variable name in file name must be the same as within netcdf file)
51
<VerticalCoordinateType> ⇒ “Surface” (2D at a given level), “Column” ( 2D integrated data), “ModelLevel” (3D), “SurfaceAtStations” (means model surface level 2D @stations), “ModelLevelAtStations” (for profile storage), "AtFlightTrack" (from 3hourly output extract, see extra instructions for aircraft exps), "AtStationAltitude" (from 3hourly output, see extra instructions
52
<Period> Year is reflecting emissions !! PD becomes 2010, PI 1850 or 1750, (meteorology needs to be specified via MeteoConfiguration)
53
<Frequency> "daily", "monthly", "fixed", "3hourly"
54
55
Contributors to this Diagnostics sheet
56
Michael Schulz, Mian Chin, Gunnar Myhre, Bjørn Samset, Stefan Kinne, Kostas Tsigaridis, Betsy Andrews, Huisheng Bian, Nick Schutgens, Christina Williamson, Duncan Watson-Parris, Philip Stier, Su Wenying
57
AP3_CTRLMichael
58
ACRIMian
59
HISTGunnar
60
ATomHuisheng
61
62
63
Input requirements, more info is assembled on the aerocom wiki page as introduction to phase III experiments (Mian edits)
64
65
66
67
Instructions for requesting output for Experiment/Analysis teams
68
See if analysis really requires an extra experiment, or can be done with CTRL or HIST
69
Put in a 1 or 2 for each variable to indicate tier 1 or 2 (each additional experiment one column)
70
Tier 1 output should be obligatory for an experiment, otherwise its tier 2
71
Variables which are requested on different frequencies: if higher frequency is tier 1 then lower frequency is tier 2 (monthly can be recomputed from daily)
72
Remember that variables which are convenient to have, but can be constructed eg from other variables, higher frequency tier 1 should be tier 2
73
Eventually see long name and notes for a variable by unhiding the hidden columns B and F "unhide colums"
74
Make comments to individual variables to the right in the comment section
75
Add name to your comments (or Initials)
76
The tables are based on AerChemMIP output request. Content should not be deletd, but rather appended
77
78
79
80
81
82
83
TODO
84
Coordinate type should be added to diagnostic sheets
85
Share for view only to modeller
86
Implement file checker w list of files, send around to modellers
87
88
89
90
91
92
93
94
95
96
97
98
99
100