Changes between Version 7 and Version 8 of Doc/Running


Ignore:
Timestamp:
10/23/14 17:21:52 (9 years ago)
Author:
mafoipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/Running

    v7 v8  
    3333# Status of the running simulation #  
    3434## run.card during the simulation ## 
    35 A run.card file is created as soon as your simulation starts. It contains information about your simulation, in particular the !PeriodState parameter which is:  
    36  * Start or !OnQueue   if your simulation is queued  
    37  * Running                  if your simulation is being executed  
    38  * Completed              if your simulation was successfully completed  
    39  * Fatal                       if your simulation was aborted due to a fatal error  
     35A ''run.card'' file is created as soon as your simulation starts. It contains information about your simulation, in particular the !PeriodState parameter which is:  
     36 * `Start` or `!OnQueue`   if your simulation is queued  
     37 * `Running`                  if your simulation is being executed  
     38 * `Completed`              if your simulation was successfully completed  
     39 * `Fatal`                       if your simulation was aborted due to a fatal error  
    4040 
    4141## Execution directory ## 
     
    121121 
    122122## run.card at the end of a simulation ## 
    123 At the end of your simulation, the !PeriodState parameter of the run.card files indicates if the simulation has been '''completed''' or was aborted due to a '''Fatal''' error. 
     123At the end of your simulation, the !PeriodState parameter of the ''run.card'' files indicates if the simulation has been '''completed''' or was aborted due to a '''Fatal''' error. 
    124124[[BR]]This files contains the following sections : 
    125125 * Configuration : allows you to find out how many integration steps were simulated and what would be the next integration step if the experiment would be continued.  
     
    201201 
    202202## Post processing in config.card ## 
    203 You must specify in config.card the kind and frequency of the post processing.  
     203You must specify in ''config.card'' the kind and frequency of the post processing.  
    204204{{{ 
    205205#======================================================================== 
     
    247247## Time Series ## 
    248248A Time Series is a file which contains a single variable over the whole simulation period (!ChunckJob2D = NONE) or for a shorter period for 2D (!ChunckJob2D = 100Y) or 3D (!ChunckJob3D = 50Y) variables.  
    249  * The write frequency is defined in the config.card file: !TimeSeriesFrequency=10Y indicates that the time series will be written every 10 years and for 10-year periods. 
     249 * The write frequency is defined in the ''config.card'' file: !TimeSeriesFrequency=10Y indicates that the time series will be written every 10 years and for 10-year periods. 
    250250 * The Time Series are set in the COMP/*.card files by the !TimeSeriesVars2D and !TimeSeriesVars3D options. 
    251251 
     
    286286 * dods at ada: http://dodsp.idris.fr 
    287287 
    288 The key variables plotted in the monitoring are computed using Time Series values. The monitoring is updated at the !TimeSerieFrequency set in config.card if the time series were successfully done. 
     288The key variables plotted in the monitoring are computed using Time Series values. The monitoring is updated at the !TimeSerieFrequency set in ''config.card'' if the time series were successfully done. 
    289289This allows you to monitor a simulation and to check the status during a en going simulation and afterwards. 
    290290By monitoring your simulations you can detect anomalies and evaluate the impact of changes you have made. We suggest to create a tab in your browser allowing you to frequently monitor your simulation. If a few key variables start looking suspicious you might want to stop your simulation. By doing so, you will save computing time. 
     
    293293 
    294294 
    295 Here is an example for the IPSLCM5A coupled model and a 10-year period. The first tab called '''Analysis Cards''' gives a summary of dates and execution times obtained from the config.card and run.card files. The second tab called '''Monitoring Board''' presents a monitoring table for the key variables (selecting one or more model components is optional). 
     295Here is an example for the IPSLCM5A coupled model and a 10-year period. The first tab called '''Analysis Cards''' gives a summary of dates and execution times obtained from the ''config.card'' and ''run.card'' files. The second tab called '''Monitoring Board''' presents a monitoring table for the key variables (selecting one or more model components is optional). 
    296296 
    297297[[Image(monitoring_01.jpg, 50%)]] 
     
    334334 
    335335## Seasonal means ## 
    336  * The SE (seasonal means) files contain averages for each month of the year (jan, feb,...) for a frequency defined in the config.card files 
     336 * The SE (seasonal means) files contain averages for each month of the year (jan, feb,...) for a frequency defined in the ''config.card'' files 
    337337   * !SeasonalFrequency=10Y The seasonal means will be computed every 10 years. 
    338338   * !SeasonalFrequencyOffset=0 The number of years to be skipped for calculating seasonal means.