Migration to the new standard environment: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "= How can I change which version of <code>StdEnv</code> is my default? = Our clusters use different versions of <code>StdEnv</code> as their default version. As of August 2020...")
 
No edit summary
Line 5: Line 5:
= Do I need to reinstall/recompile my code if the <code>StdEnv</code> version changes? =
= Do I need to reinstall/recompile my code if the <code>StdEnv</code> version changes? =
Yes. If you compile your own code, or install R or Python packages, you should recompile or reinstall the packages you need using the newest version of the standard environment.
Yes. If you compile your own code, or install R or Python packages, you should recompile or reinstall the packages you need using the newest version of the standard environment.
= How can I use the old environments ? =
If you have an existing workflow and want to continue to use the same software versions you are using now, simply add <code>module load StdEnv/2018.3</code> or <code>module load StdEnv/2016.4</code> to your jobscript before loading any other modules. 
= Will old environments go away ? =
No, they ''will not go away''.  They and all the software dependent on them will remain available!  However, Compute Canada staff will no longer install anything into the old environemnts.
= Which environment should I use ? =
If you are starting a new project, or if you want to use a newer version of some software, you should use <tt>StdEnv/2020</tt>. Today you can do this by adding <code>module load StdEnv/2020</code> to your job script. As of April 1, it will be the default and the line will be unnecessary (though not a problem).
Bureaucrats, cc_docs_admin, cc_staff, rsnt_translations
2,837

edits

Navigation menu