Changes between Version 6 and Version 7 of Documentation/UserGuide/VerifyClimate

Timestamp:

2014-11-11T14:04:29+01:00 (9 years ago)

Author:

luyssaert

Comment:

--

Documentation/UserGuide/VerifyClimate

@@ -1 +1 @@
 Once you have run LMDZOR, the first question to ask yourself is: does the climate I'm getting make sense?  There does not seem to be any straightforward way to answer this question, so this page is going to give ideas on how to procede.
 
-Tip 1) Run a spinup of ORCHIDEE offline to get reasonable biomass and soil water pools, which seems to be fairly important if you are using the 11-layer hydrology.  The only way to do this that I know of is to regrid the driver files to the resolution you are interested in (such files now exist for the CRU dataset for 128x118) and use those to run offline for 50 years or so.  Then you can use the resulting restart files to start the LMDZOR calculation.  This is not a trivial step!  You also need to make sure that the land mask you are using matches what is found in LMDZOR.  The way we came up with to do this was to run a one day simulation of LMDWOR without a restart and look at the resulting history files.  There are variables inside the histday*nc files called CONTFRACOR and CONTFRACATM, which contain the fraction of each gridcell which have land.  We made sure that all these pixels had climate variables in our regridded forcing files, even if it meant copying the forcing data from nearby pixels.
+Tip 1) Run a spinup of ORCHIDEE offline to get reasonable biomass and soil water pools, which seems to be fairly important if you are using the 11-layer hydrology.  The only way to do this that I know of is to regrid the driver files to the resolution you are interested in (such files now exist for the CRU dataset for 128x118) and use those to run offline for 50 years or so.  Then you can use the resulting restart files to start the LMDZOR calculation.  This is not a trivial step!  You also need to make sure that the land mask you are using matches what is found in LMDZOR.  The way we came up with to do this, was to run a one day simulation of LMDZOR without a restart and look at the resulting history files.  There are variables inside the histday*nc files called CONTFRACOR and CONTFRACATM, which contain the fraction of each gridcell which have land.  We made sure that all these pixels had climate variables in our regridded forcing files, even if it meant copying the forcing data from nearby pixels.
 
 Tip 2) It takes at least 10 simulation years to get a good idea of the climate.  It also takes some time to equilibrate the climate after starting from a restart, so it seems that you can plan on a simulation of at least 15 years: 5 years to equilibrate, and 10 years over which to calculate the average climate.
 
-Once you have the simulation, you need to do the averaging, find data to compare to, and create graphs.  The tool ATLAS appears to do this.  I wasn't able to find much documentation on it, though.
+Once you have the simulation, you need to do the averaging, find data to compare to, and create graphs.  The tool ATLAS does exactly this.  I wasn't able to find much documentation on it, though.
 
 (in French, only a few small mentions)
@@ -22 +22 @@
 
 
-It appears that the post-treatment proceeds in two steps: step 1 is to combine the raw data into files containing all the years you want to average over (given by SeasonalFrequency in the config.card).  Step 2 is to compare these files (located in JOBNAME/ATM/Analyse/SE/ in the IGCM directory tree...what comes before this depends on what you put in the config.card and what system you are running on) to a set of reference data.  Step 2 then compares this data to the reference simulation or observations, depending on what you are trying to do.
+It appears that the post-treatment proceeds in two steps: 
+* step 1 is to combine the raw data into files containing all the years you want to average over (given by SeasonalFrequency in the config.card).  Step 2 is to compare these files (located in ./JOBNAME/ATM/Analyse/SE/ in the IGCM directory tree. What comes before JOBNAME depends on what you put in the config.card and what system you are running on) to a set of reference data.  
+* Step 2 then compares this data to the reference simulation or observations, depending on what you are trying to do.
 
 As an example, let's say I have two simulations that I want to compare.