New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
user/flavoni/libIGCM_v3.6/list_of_possible_errors (diff) – NEMO

Changes between Version 4 and Version 5 of user/flavoni/libIGCM_v3.6/list_of_possible_errors


Ignore:
Timestamp:
2015-11-02T12:39:53+01:00 (9 years ago)
Author:
flavoni
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • user/flavoni/libIGCM_v3.6/list_of_possible_errors

    v4 v5  
    33 
    44=== '''How to perform a second simulation after a run with !PeriodState=Fatal''' === 
    5   rm Job_name/run.card;  rm Script_Output* rm everything created during the simulation in IGCM_OUT 
     5  rm Job_name/run.card;  
     6  rm Script_Output*  
     7  rm everything created during the simulation in IGCM_OUT 
    68 
    7   but do not cancel run.card.'''      init'''       file, if not run.card file is not re-created. 
     9  but do not cancel run.card.'''       init'''        file, if not run.card file is not re-created. 
    810 
    9   ( File run.card.init is created with ins_job script )[[BR]]     [[BR]]     Submit the main job --- OR: cd EXPERIENCE[[BR]]     ../../../libIGCM/'''     clean_month.job''' 
     11  ( File run.card.init is created with ins_job script )[[BR]]      [[BR]]      Submit the main job  
     12  --- or you can use clean_month.job script: 
     13  cd EXPERIENCE[[BR]]      ../../../lib IGCM/'''      clean_month.job''' 
    1014 
    1115=== '''How to continue a simulation ''' === 
    12   Update config.card with the new !DateEnd     . Do not change !DateBegin     .'''      '''     Change !PeriodState      in run.card to !OnQueue      (or let clean_month job do it for you)'''      '''     Submit the main job 
     16  Update config.card with the new !DateEnd      . Do not change !DateBegin      .'''       '''      Change !PeriodState       in run.card to !OnQueue       (or let clean_month job do it for you)'''       '''      Submit the main job 
    1317 
    1418=== ''' How to continue a simulation that crashed previously''' === 
     
    1620 
    1721=== '''!RebuildFromArchive=NONE''' === 
    18   In MPI it is good to use Rebuild in "archive" machine, to not ovrerload calcul machine. [[BR]]        You have to put in config.card in POST Session: 
     22  In MPI it is good to use Rebuild in "archive" machine, to not ovrerload calcul machine. [[BR]]         You have to put in config.card in POST Session: 
    1923 
    20   !RebuildFrequency        =1Y [[BR]]        !RebuildFromArchive        =true 
     24  !RebuildFrequency         =1Y [[BR]]         !RebuildFromArchive         =true 
    2125 
    22   NOTA BENE: If you put !RebuildFrequency        =1Y and you forget to set !RebuildFromArchive        =true, it is very dangerous. NEVER DO IT! 
     26  NOTA BENE: If you put !RebuildFrequency         =1Y and you forget to set !RebuildFromArchive         =true, it is very dangerous. NEVER DO IT! 
    2327 
    2428=== '''How to do a long job without exit from queue''' === 
    25   You can play with Duration Experience, PeriodLenght         and PeriodNb        , elapstim_req in this way :[[BR]]        in '''        config.card'''         Duration Experience is = !DateBegin         - !DateEnd         [[BR]]        in '''        config.card'''         !PeriodLenght         is how many time you do restart files[[BR]]        in '''        Job_Name'''         !PeriodNb         is  in '''        Job_Name'''         elapstim_req is elapsed time limit 
     29  You can play with Duration Experience, PeriodLenght          and PeriodNb         , elapstim_req in this way :[[BR]]         in '''         config.card'''          Duration Experience is = !DateBegin          - !DateEnd          [[BR]]         in '''         config.card'''          !PeriodLenght          is how many time you do restart files[[BR]]         in '''         Job_Name'''          !PeriodNb          is  in '''         Job_Name'''          elapstim_req is elapsed time limit 
    2630 
    27   Your job is out from queue every time that is finished a PeriodNb        , so you can do : 
     31  Your job is out from queue every time that is finished a PeriodNb         , so you can do : 
    2832 
    29   !PeriodNb         = ( Duration Experience ) / !PeriodLenght 
     33  !PeriodNb          = ( Duration Experience ) / !PeriodLenght 
    3034 
    3135  but be careful with elapstim_req, because this is a limit, you've to be sure that it exists a queue that can hold you.