Install and compile 5 to 10 year old versions of ORCHIDEE for offline use

Authors: J. Ghattas and S. Luyssaert
Last revision: 2024/06/11, J. Ghattas

Objectives

This page provides the basic steps to install and compile old versions of the ORCHIDEE model on the standard set of machine maintained by the IPSL group: irene/TGCC, jeanzay/IDRIS, obelix/LSCE and ciclad/climserv/IPSL. "Old versions" refers to versions that were developed without XIOS, an earlier XIOS, a different machine environment, etc.

Remarks

• The instructions below should not be considered a recipe'''
• The notes were taken when installing and compiling a 5 and 11 year old version of ORCHIDEE and are closer to documentation than to a how to.
• When applied to a different version, or different machine different challenges may arise.

ORCHIDEE r6863

How to install ORCHIDEE r6863 (2019) on irene in 2024?

• Change the mod.def for ORCHIDEE_trunk and put the correct revision numbers for trunk/ORCHIDEE and trunk/ORCHIDEE_OL in mod.def.
• Extract all components by using ./model ORCHIDEE_trunk
• Update the config/ORCHIDEE_OL/ARCH folder first by making use of svn
• Use the compilation script that comes with this extraction
• Done!

ORCHIDEE r1383

How to install ORCHIDEE r1383 (2013) on irene in 2024?

• Go to svn and check the date of the revision you want to install. r1383 was committed 11/07/2013
• Use this date to get the revision number of modipsl. On 03/07/2013 modipsl was at r2021. Note that XIOS entered modipsl for ORCHIDEE in r2395.
• Change the mod.def for ORCHIDEE_trunk and put the correct revision numbers for trunk/ORCHIDEE and trunk/ORCHIDEE_OL.
• Remove XIOS from mod.def. XIOS is not yet in the ORCHIDEE code. So there is nothing we can do with XIOS.
• We used the present day IOIPSL from today’s libIGCM to benefit from updates on the different servers.
• Extract all components ./model ORCHIDEE_trunk
• Copy the compilation script compile_orchidee_ol.sh from the head of the trunk ORCHIDEE_OL.
• Copy the folder ARCH from the head of the trunk ORCHIDEE_OL
• We ran into a couple of problems:
  • Unknown option -j -> removed
  • Unknown option -without_xios -> logic because there is no XIOS. Remove an exit.
  • Unknown option -arch_path. At that time there were no arch_files yet. Remove were the compilation finds the arch file. Load the arch.env in the terminal. This could be copied from config/ORCHIDEE_OL/ARCH/arch-x64_IRENE.env
  • The environment file for IRENE does not exist in that revision because IRENE did not yet exist at that time. This file needs to be created. Use a file from CURIE as a template. So both the arch.path and arch.
  • fcm files have to be adjusted.
• In the end the above error resulted in changing the line ./makeorchidee_fcm by removing -j, -$XIOS, and -arch_path $arch_path into ./makeorchidee_fcm -parallel $parallel -$optmode -arch ${fcm_arch} $full_orch -driver $otherexec
• For running, add following in config.card in section UserChoices: EnvFile=${SUBMIT_DIR}/../ARCH/arch.env
• Done!

Let’s make a job.

• Change the config.card
  • JobNumProc is no longer used by libIGCM. So remove it
  • Rebuild frequency has to be correctly set
  • The routing requires some new (actually old) settings as well. These settings can be copied from a FG_CRUJRA_HIST/COMP/sechiba.card
  • Other paths on to the orchideeshare folder may also have to be changed

The models runs but there were problems with the rebuild.

• We installed the complete IOIPSL so we could use the rebuild from IOIPSL.
• Change the path to rebuild in libIGCM_sys/libIGCM_sys_irene.ksh export PATH=${PATH}:/ccc/work/cont003/gen6328/p86ghatt/SIMULATION_ORCHIDEE/ORCr1383/modipsl/modeles/IOIPSL/build/bin
• If the problem persists, try some manual interventions:
  • Load the correct modules
  • The file name of the exe was slightly different. After changing the name the script worked. Let’s go back to libIGCM
  • As another debugging test, try the option NONE for RebuildFrequency? in config.card and launch the rebuild script as a job. In libIGCM_sys_irene.ksh there is a switch between computing and post-processing. Depending on whether the rebuilding is done as part of the job or launched as a post processing job after the actual calculations different paths seems to be used.
  • Remember to delete the rebuild folders because as a precaution this is no longer done automatically. It was possible that all files were deleted even if the rebuild was not successful. That would imply that the whole simulation had to be rerun.