Chunk lance : Différence entre versions
m (Created page with "= Chunk_lance = Chunk_lance allows to run a sequence of monthly model jobs in one big job. A GEM/GEMCLIM/CRCM5 simulation usually consists of a sequence of month jobs. Each m...") |
m |
||
| Ligne 1: | Ligne 1: | ||
| − | = Chunk_lance = | + | = Chunk_lance = |
| − | Chunk_lance allows to run a sequence of monthly model jobs in one big job. | + | Chunk_lance allows to run a sequence of monthly model jobs in one big job. |
A GEM/GEMCLIM/CRCM5 simulation usually consists of a sequence of month jobs. | A GEM/GEMCLIM/CRCM5 simulation usually consists of a sequence of month jobs. | ||
| − | Each monthly job is made up out of 3 parts: | + | Each monthly job is made up out of 3 parts: |
| − | #auto_launch (copies restart files from previous month, prepare config files for new month) | + | #auto_launch (copies restart files from previous month, prepare config files for new month) |
| − | #entry (only in LAM mode, prepares driving data) | + | #entry (only in LAM mode, prepares driving data) |
#model (main model job) | #model (main model job) | ||
| − | Chunk_lance will run a series of these 3 jobs, checking at the end of each model job if there is still enough time to calculate another month. If yes the 3 jobs will get executed for another month, if not an new chunk_job will get submitted. | + | Chunk_lance will run a series of these 3 jobs, checking at the end of each model job if there is still enough time to calculate another month. If yes the 3 jobs will get executed for another month, if not an new chunk_job will get submitted. |
| − | In case the model job fails it will automatically get reexecuted up to 4 times. | + | In case the model job fails it will automatically get reexecuted up to 4 times. |
| + | |||
| + | Since the running job is not always called "chunk_job" one cannot see anymore from the job name how far the simulation has progressed. But one can always have a look at the listings directory and also a log file is kept in the config file directory called "chunk_job.log".<br>This file is essential for the whole chunk_job procedure. The chunk_job itself will check this file to determine which job to execute next. Therefore this log file must only be removed if one wants to restart a simulation from the beginning.<br>However, to rerun part of a simulation one can alter the log file by hand. Just make sure there is never a blank line at the end of the log file since the chunk_job only checks the very last line of the log file! | ||
Version depuis le 20 de décembre 2011 à 15:17
Chunk_lance
Chunk_lance allows to run a sequence of monthly model jobs in one big job.
A GEM/GEMCLIM/CRCM5 simulation usually consists of a sequence of month jobs.
Each monthly job is made up out of 3 parts:
- auto_launch (copies restart files from previous month, prepare config files for new month)
- entry (only in LAM mode, prepares driving data)
- model (main model job)
Chunk_lance will run a series of these 3 jobs, checking at the end of each model job if there is still enough time to calculate another month. If yes the 3 jobs will get executed for another month, if not an new chunk_job will get submitted.
In case the model job fails it will automatically get reexecuted up to 4 times.
Since the running job is not always called "chunk_job" one cannot see anymore from the job name how far the simulation has progressed. But one can always have a look at the listings directory and also a log file is kept in the config file directory called "chunk_job.log".
This file is essential for the whole chunk_job procedure. The chunk_job itself will check this file to determine which job to execute next. Therefore this log file must only be removed if one wants to restart a simulation from the beginning.
However, to rerun part of a simulation one can alter the log file by hand. Just make sure there is never a blank line at the end of the log file since the chunk_job only checks the very last line of the log file!
