step by step porting CESM2.1.3 to a new machine

[littledddna@gmail_com]

Hi, all,
is there a detailed step by step porting procedure for CESM2.1.3 that I can find online?
I have done porting CESM1.0.0 to a new platform before but now I would like to try CESM2.1.3.
However, all materials that I found are too general and it is difficult to start.

Thanks very much

 

[jedwards]

6. Porting and validating CIME on a new platform — CIME cime5.6 documentation

 

[littledddna@gmail_com]

6. Porting and validating CIME on a new platform — CIME cime5.6 documentation

Thanks very much, I finished modifying the config_machines.xml file but i have questions about these lines.
The com_path seems pointing to the executables, but where should these init_path pointing to ?

Thanks very much

Xiao







<init_path lang="perl">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/init/perl</init_path>
<init_path lang="python">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/init/env_modules_python.py</init_path>
<init_path lang="csh">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/init/csh</init_path>
<init_path lang="sh">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/init/sh</init_path>
<cmd_path lang="perl">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/libexec/lmod perl</cmd_path>
<cmd_path lang="python">/glade/u/apps/ch/opt/lmod/7.2.1/lmod/lmod/libexec/lmod python</cmd_path>
<cmd_path lang="sh">module</cmd_path>
<cmd_path lang="csh">module</cmd_path>

 

[jedwards]

The init paths point to the module initialization script for each language, usually in a path similar to the above.

 

[littledddna@gmail_com]

The init paths point to the module initialization script for each language, usually in a path similar to the above.

Thanks very much ! Seems like in the cluster I use, it is located at

/app/modules/4.1.0-gcc-4.8.5/init/

Difficult to locate. :P

 

[m_mineter@ed_ac_uk]

Thanks very much ! Seems like in the cluster I use, it is located at

/app/modules/4.1.0-gcc-4.8.5/init/

Difficult to locate. :P

I had the same puzzle and then looked inside the script /etc/profile.d/modules.sh.
So your app/modules/4.1 etc is a module file. It can only be loaded because your .bashrc has run /etc/profile.d/modules.sh
That in turn runs the scripts that you need to include in the config_machines.xml.
I followed the pattern of the installed file and ended up with:

<module_system type="module">
<init_path lang="perl">/exports/applications/apps/SL7/environment-modules-3.2.10/Modules/3.2.10/init/perl.pm</init_path>
<init_path lang="python">/exports/applications/apps/SL7/environment-modules-3.2.10/Modules/3.2.10/init/python.py</init_path>
<init_path lang="csh">/etc/profile.d/modules.sh</init_path>
<init_path lang="sh">/etc/profile.d/modules.sh</init_path>
<cmd_path lang="perl">/exports/applications/apps/SL7/environment-modules-3.2.10/Modules/3.2.10/bin/modulecmd perl</cmd_path>
<cmd_path lang="python">/exports/applications/apps/SL7/environment-modules-3.2.10/Modules/3.2.10/bin/modulecmd python</cmd_path>

Of course you would have something different to my "/exports/applications/apps/SL7/environment-modules-3.2.10/Modules/3.2.10/"