Changes between Version 34 and Version 35 of Doc/CheckDebug


Ignore:
Timestamp:
05/18/17 16:03:47 (3 years ago)
Author:
pinsard
Comment:

typo

Legend:

Unmodified
Added
Removed
Modified
  • Doc/CheckDebug

    v34 v35  
    236236## Where does the problem come from ? ## 
    237237 
    238 Your problem could come from a programing error. To find it you can use the text output of the model components located in the Debug subdirectories. Your problem could be caused by the computing environment. This problem is not always easy to identify. It is therefore important to perform benchmark simulations to learn about the usual behavior of a successfully completed simulation. 
     238Your problem could come from a programming error. To find it you can use the text output of the model components located in the Debug subdirectories. Your problem could be caused by the computing environment. This problem is not always easy to identify. It is therefore important to perform benchmark simulations to learn about the usual behavior of a successfully completed simulation. 
    239239 
    240240### The Debug directory ### 
     
    258258In this case, it's possible to relaunch the main job to run again the last period. 
    259259 
    260 If the simulation stopped before coming to the end due to an error, it it possible to relaunch the latest period after eventual modifications. The simulation will then read run.card to know where to start and the simulation will continue until the end (if the problem was solved). 
     260If the simulation stopped before coming to the end due to an error, it is possible to relaunch the latest period after eventual modifications. The simulation will then read run.card to know where to start and the simulation will continue until the end (if the problem was solved). 
    261261 
    262262To relaunch manually you first need to be sure that no files have been stored for the same period. In libIGCM there are 2 scripts that help you do this cleaning up :