Changes between Version 56 and Version 57 of Doc/FAQ


Ignore:
Timestamp:
10/10/19 12:12:05 (5 years ago)
Author:
nillod
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/FAQ

    v56 v57  
    5252 
    5353## How do I create the LMDZ histins.nc file? ## 
    54 You have several options. The easiest one is to change the output frequency of one of the existing files. For instance, you can change the output frequency of the histhf.nc file to instantaneous without changing the file name. To do so, keep HF in !WriteFrequency in config.card: 
     54You have several options to create instantaneous output file. The easiest one is to change the output frequency of one of the existing files. For instance, you can change the output frequency of the histhf.nc file to instantaneous without changing the file name. To do so, keep HF in !WriteFrequency in config.card: 
    5555{{{ 
    5656[ATM] 
    … …  
    7272'''Important''' : If your simulation stops you can look for the keyword "IGCM_debug_CallStack" in this file. This word will be preceded by a line giving more details on the problem that occurred.  
    7373 
    74 See [wiki:DocGmonitor#AnalyzingtheJoboutput:Script_Output can be found here] for more details. 
     74Click [wiki:Doc/CheckDebug#AnalyzingtheJoboutput:Script_Output here for more details]. 
    7575 
    7676## The LMDZ parallelism and the Bands files ## 
    77 See [wiki:DocImodelBlmdz#ParallelismandtheBandsfile here]. 
     77See [wiki:Doc/Models/LMDZ#ParallelismandtheBandsfile here]. 
    7878 
    7979## How do I define the number of MPI jobs and the number of OpenMP threads? ## 
    … …  
    9292}}} 
    9393 
    94 Notice that the job header differs from the one for openMP. 
     94Notice that the job header differs from the one for openMP because you fill the total of core to use. 
    9595 
    9696  
    … …  
    105105 * a post processing job encountered a problem 
    106106  * `pack_xxx` has failed and caused the simulation to abort. In this case, you must find `STOP HERE INCLUDING THE COMPUTING JOB` located in the appropriate output pack file.  
    107    * `rebuild` was not completed successfully  
    108  
    109 See the corresponding chapter about [wiki:DocGmonitor monitoring and debug] for further information. 
     107   * `rebuild` was not completed successfully (for ORCHIDEE_OL)  
     108 
     109See the corresponding chapter about [wiki:Doc/CheckDebug monitoring and debug] for further information. 
    110110 
    111111## How do I use a different version of libIGCM? ## 
    … …  
    113113libIGCM is constantly being updated. We recommend to choose the latest tag of libIGCM. Here is what to do: 
    114114 * save the old libIGCM version (just in case)  
    115  * get libIGCM 
     115 * get new libIGCM 
    116116 * reinstall the post processing jobs  
    117117 * make sure that there has been no major change in AA_job, otherwise reinstall the main job  
    118 {{{ 
     118{{{#!sh 
    119119cd modipsl 
    120120mv libIGCM libIGCM_old 
    … …  
    125125In case you need version XXX of the trunk of libIGCM, change the "svn checkout" line into: 
    126126 
    127 {{{ 
     127{{{#!sh 
    128128svn checkout -r XXX http://forge.ipsl.jussieu.fr/libigcm/svn/trunk/libIGCM libIGCM 
    129129}}} 
    … …  
    133133 * move to the experiment directory,  
    134134 * delete or move old jobs  
    135  * rerun the new jobs using `ins_job`. MYCONFIG could be IPSLCM5_v5 or ORCHIDEE_OL, for example: 
     135 * rerun the new jobs using `ins_job`. MYCONFIG could be IPSLCM6 or ORCHIDEE_OL, for example: 
    136136{{{ 
    137137cd ...../config/MYCONFIG/MYEXP 
    … …  
    140140# modifier Job_MYEXP : NbPeriod, memory,... as it was done in OLDJOB 
    141141}}} 
     142 
    142143## How do I restart a simulation to recover missing output files?  ## 
    143144 
    144 UPDATE - ON CURIE  (4/18/2016 ACo) / TO BE DONE ON ADA (idea : change $STOREDIR by ergon or ada workdir)  
     145TO BE DONE ON JEANZAY (idea : change $STOREDIR by jeanzay workdir)  
    145146 
    146147This method shows how to rerun a complete simulation period in a different directory (REDO instead of DEVT/PROD). 
    … …  
    157158}}} 
    158159 * There is nothing to do for the Bands file, it's save at previous period in PARAM directory, and the simulation know where to find it.  
    159  * If you are running a coupled model : On the scratch disk ($SCRATCHDIR/IGCM_OUT), create the mesh_mask file (TO BE CONFIRMED)  
    160 {{{ 
    161 mkdir $SCRATCHDIR/....IGCM_OUT/IPSLCM5A/REDO/historicalAnt/v3.historicalAnt1REDO 
    162 cd $SCRATCHDIR/....IGCM_OUT/IPSLCM5A/REDO/historicalAnt/v3.historicalAnt1REDO 
     160 * If you are running a coupled model : On the scratch disk ($CCCSCRATCHDIR/IGCM_OUT), create the mesh_mask file 
     161{{{ 
     162mkdir $CCCSCRATCHDIR/....IGCM_OUT/IPSLCM5A/REDO/historicalAnt/v3.historicalAnt1REDO 
     163cd $CCCSCRATCHDIR/....IGCM_OUT/IPSLCM5A/REDO/historicalAnt/v3.historicalAnt1REDO 
    163164# mesh_mask 
    164165mkdir -p OCE/Output 
    … …  
    180181PeriodState= OnQueue 
    181182}}} 
    182    * change the config.card file to one pack period (1 year), do not do any post processing, start rebuild month by month and specify !PackFrequency. 
     183   * change the config.card file to one pack period (1 year), do not do any post processing, start rebuild month by month (only for ORCHIDEE_OL) and specify !PackFrequency. 
    183184{{{ 
    184185JobName=v3.historicalAnt1 
    … …  
    188189DateEnd= 1964-12-31 
    189190... 
    190 RebuildFrequency=1M 
     191RebuildFrequency=1M # only for ORCHIDEE_OL 
    191192PackFrequency=1Y 
    192193... 
    … …  
    254255}}} 
    255256[[BR]][[BR]] 
     257'''Warning: you'll need to get parameter files and maybe some forcing ones corresponding to the resolution.''' 
     258 
    256259 
    257260# FAQ :  Special configurations #