Version 6 (modified by acosce, 8 months ago) (diff) |
---|
ICOLMDZOR_v7
Table of contents
ICOLMDZOR_v7 DOESN'T EXIST ANYMORE - IT'S NOW INCLUDE IN IPSLCM7 CONFIGURATION
See IPSLCM7 documentation
1. OLD Description
ICOLMDZOR is a configuration coupling DYNAMICO, LMDZ physics and ORCHIDEE.
1.1. OLD Computing centers
ICOLMDZOR_v7_work is currently maintained at irene/TGCC and jeanzay/IDRIS.
1.2. OLD Compilation
Compilation is done using a script compilation_icolmdzor.sh available in modipsl/config/ICOLMDZOR. The script detects on which computing center the installation is done and sources modules needed for compilation. The same modules will be sourced during run time by libIGCM. The module file is set in the folder modipsl/config/ICOLMDZOR/ARCH/.
1.3. OLD Running
- The resolution is given by the parameters RESOL_NBP and RESOL_ATM_Z set in dynamico.card. Input files for resolution RESOL_NBP=40 and RESOL_NBP=160 exist on the shared repository.
- Output level and frequency for LMDZ and ORCHIDEE is set in corresponding comp.card : lmdz.card, orchidee.card and stomate.card
2. OLD Quick installation guide
# Install modipsl svn co http://forge.ipsl.jussieu.fr/igcmg/svn/modipsl/trunk modipsl cd modipsl/util # Download and compile configuration ICOLMDZOR_v7_work ./model ICOLMDZOR_v7_work cd ../config/ICOLMDZOR_v7 ./compile_icolmdzor.sh [-debug, ...] # Experiment setup cp EXPERIMENT/ICOLMDZOR/highresmip/config.card . # => modify at least JobName=MyJobname, DateBegin, DateEnd in config.card, number of cores per component ../../libIGCM/ins_job cd MyJobname # Modify default setup: # for example change atmospheric resolution nbp, output level, parameter setup or input files ccc_msub Job_MyJobname
3. OLD Trick to prepare a run directory corresponding to a predefined experiment
If you need for development purpose work directly in the run directory without lauching with libIGCM, you can prepare the run directory using following:
# Prepare the main job as above # In the main Job_MyJobname, add exit after the line echo "# DIR BEFORE RUN EXECUTION #" exit # Launch the job: ccc_msub Job_MyJobname # Find the path to the run directory grep RUN_DIR Script_Output_MyJobname.0001 # All input files and executables now exist in the RUN_DIR but you need to write the job to launch yourself