Changes between Version 65 and Version 66 of Doc/Running
- Timestamp:
- 10/10/19 17:16:29 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/Running
v65 v66 47 47 48 48 ### Execution directory ### 49 * At TGCC your simulation is performed in a $ SCRATCHDIR/RUN_DIR/job_number directory. You can check the status of your simulation in this directory.49 * At TGCC your simulation is performed in a $CCCSCRATCHDIR/RUN_DIR/job_number directory. You can check the status of your simulation in this directory. 50 50 * [[Span(id=run_dir_path)]]At IDRIS your simulation is performed in a temporary directory. You must first specify '''RUN_DIR_PATH=$WORKDIR''' in your production job if you want to monitor it. 51 51 … … 174 174 175 175 Prior to the packs execution, this directory structure is stored 176 * on the $ SCRATCHDIR at TGCC176 * on the $CCCSCRATCHDIR at TGCC 177 177 * on the $WORKDIR at IDRIS 178 178 … … 245 245 * IOIPSL is used as output writing library and you run in parallel mode. 246 246 * XIOS is used as output writing library, you run in parallel mode, you run in XIOS attached mode (or server mode with several servers) and you activate multiple_file XIOS mode. 247 * If needed, `rebuild` is automatically called at the !RebuildFrequency frequency and it is usually the very first step of post processing. Specifying NONE for !RebuildFrequency will start the file combining on the computing machine instead of doing it on the post processing machine. This is strongly discouraged. !RebuildFrequency=1Y indicates the frequency of running REBUILD. The files to be combined by `rebuild` are stored on a buffer space $ SCRATCHDIR/IGCM_OUT/../!JobName/REBUILD/ at TGCC and $WORK/IGCM_OUT/.../!JobName/REBUILD at IDRIS. Note: if !JobType=DEV the parameter is forced to have the !PeriodLength value.247 * If needed, `rebuild` is automatically called at the !RebuildFrequency frequency and it is usually the very first step of post processing. Specifying NONE for !RebuildFrequency will start the file combining on the computing machine instead of doing it on the post processing machine. This is strongly discouraged. !RebuildFrequency=1Y indicates the frequency of running REBUILD. The files to be combined by `rebuild` are stored on a buffer space $CCCSCRATCHDIR/IGCM_OUT/../!JobName/REBUILD/ at TGCC and $WORK/IGCM_OUT/.../!JobName/REBUILD at IDRIS. Note: if !JobType=DEV the parameter is forced to have the !PeriodLength value. 248 248 * !RebuildFromArchive=NONE is the option to be used on all machines. The REBUILD job first looks for the files to be assembled on the buffer space. Then it assembles them (''rebuild''), applies requested Patchs and stores them in the usual COMP/Output/MO or COMP/Output/DA directories for monthly or daily files of the COMP component (OCE, ICE, ATM, SRF, ...). Note: REBUILD does the ordering of other post processing jobs ran by the create_ts.job and create_se.job jobs. 249 249 … … 448 448 Besides, the post processing output log files are : 449 449 * on Ada: `$WORKDIR/IGCM_OUT/TagName/.../JobName/Out` 450 * on Curie: `$ SCRATCHDIR/IGCM_OUT/TagName/.../JobName/Out`450 * on Curie: `$CCCSCRATCHDIR/IGCM_OUT/TagName/.../JobName/Out` 451 451 452 452 In these directories, you find the job output files for following jobs: `rebuild`, `pack*`, `ts`, `se`, `atlas`, `monitoring `.
