Migration to the new standard environment: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
<translate> | <translate> | ||
= What are the differences between | = What are the differences between <tt>StdEnv/2020</tt> and the earlier environments? = <!--T:1--> | ||
The differences are discussed in [[Standard software environments]]. | |||
= | = Can I change my default standard environment? = <!--T:2--> | ||
Our clusters use different | Our clusters currently use different <code>StdEnv</code> versions as their default. [[Cedar]] and [[Graham]] use <code>StdEnv/2016.4</code>, while [[Béluga/en|Béluga]] uses <code>StdEnv/2018.3</code>. [[Niagara]] defaults to <code>StdEnv/2018.3</code> when you run <code>module load CCEnv StdEnv</code>. | ||
<!--T:8--> | <!--T:8--> | ||
On April | On April 1, 2021, <code>StdEnv/2020</code> will be the default environment for all clusters. However, you can specify your own default environment by running the following command (example provided for version 2016.4): | ||
{{Command|echo "module-version StdEnv/2020 default" >> $HOME/.modulerc}} | {{Command|echo "module-version StdEnv/2020 default" >> $HOME/.modulerc}} | ||
= Do I need to reinstall/recompile my code | = Do I need to reinstall/recompile my code when the <code>StdEnv</code> changes? = <!--T:3--> | ||
Yes. If you compile your own code, or | Yes. If you compile your own code, or have installed R or Python packages, you should recompile your code or reinstall the packages you need with the newest version of the standard environment. | ||
= How can I use | = How can I use an earlier environment? = <!--T:4--> | ||
If you have an existing workflow and want to continue to use the same software versions you are using now, simply add | If you have an existing workflow and want to continue to use the same software versions you are using now, simply add | ||
module load StdEnv/2018.3 | module load StdEnv/2018.3 | ||
or | or | ||
module load StdEnv/2016.4 | module load StdEnv/2016.4 | ||
to your job | to your job scripts before loading any other modules. | ||
= Will | = Will the earlier environments be removed? = <!--T:5--> | ||
The earlier environments and any software dependent on them will remain available. However, our staff will no longer install anything in the old environments. | |||
= Which environment should I use ? = <!--T:6--> | = Which environment should I use ? = <!--T:6--> | ||
If you are starting a new project, or if you want to use a newer version of | If you are starting a new project, or if you want to use a newer version of an application, you should use <tt>StdEnv/2020</tt> by adding | ||
module load StdEnv/2020 | module load StdEnv/2020 | ||
to your job | to your job scripts. This command does not need to be deleted to use <code>StdEnv</code> after April 1. | ||
= Can I keep the old environment by loading modules in my <code>.bashrc</code> ? = <!--T:7--> | = Can I keep using the old environment by loading modules in my <code>.bashrc</code>? = <!--T:7--> | ||
Loading modules in your <code>.bashrc</code> is '''not recommended'''. Instead, explicitly load modules in your job scripts. | Loading modules in your <code>.bashrc</code> is '''not recommended'''. Instead, explicitly load modules in your job scripts. | ||
</translate> | </translate> | ||
Revision as of 20:41, 23 March 2021
What are the differences between StdEnv/2020 and the earlier environments?
The differences are discussed in Standard software environments.
Can I change my default standard environment?
Our clusters currently use different StdEnv versions as their default. Cedar and Graham use StdEnv/2016.4, while Béluga uses StdEnv/2018.3. Niagara defaults to StdEnv/2018.3 when you run module load CCEnv StdEnv.
On April 1, 2021, StdEnv/2020 will be the default environment for all clusters. However, you can specify your own default environment by running the following command (example provided for version 2016.4):
[name@server ~]$ echo "module-version StdEnv/2020 default" >> $HOME/.modulerc
Do I need to reinstall/recompile my code when the StdEnv changes?
Yes. If you compile your own code, or have installed R or Python packages, you should recompile your code or reinstall the packages you need with the newest version of the standard environment.
How can I use an earlier environment?
If you have an existing workflow and want to continue to use the same software versions you are using now, simply add
module load StdEnv/2018.3
or
module load StdEnv/2016.4
to your job scripts before loading any other modules.
Will the earlier environments be removed?
The earlier environments and any software dependent on them will remain available. However, our staff will no longer install anything in the old environments.
Which environment should I use ?
If you are starting a new project, or if you want to use a newer version of an application, you should use StdEnv/2020 by adding
module load StdEnv/2020
to your job scripts. This command does not need to be deleted to use StdEnv after April 1.
Can I keep using the old environment by loading modules in my .bashrc?
Loading modules in your .bashrc is not recommended. Instead, explicitly load modules in your job scripts.