Skip to content

Commit

Permalink
Notes about varset and notur modules
Browse files Browse the repository at this point in the history
  • Loading branch information
MalkinE committed May 10, 2017
1 parent 2b980fa commit eddf7b3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion news/new_sw.rst
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,6 @@ To solve this you need to remove your old collections and create them again. We

If you are already using "mod_setup.sh"
----------------------------------------
If you have already started using the new modules by loading the "notur" module and sourcing "mod_setup.sh", simply remove these two steps and continue working as normal. We kept this option working for now to reduce the number of potentially crashing jobs, but we plan to remove it in the near future, so we recommend removing those lines from any new jobs you launch.
If you have already started using the new modules by loading the "notur" module and sourcing "mod_setup.sh", simply remove these two steps and continue working as normal. We kept this option working for now to reduce the number of potentially crashing jobs, but we plan to remove it in the near future, so we recommend removing those lines from any new jobs you launch. You do not need the module "varset" any more, StdEnv has taken over its functionality. If the only reason you were using the "notur" module was to access the newer installations, you do not need it either. If you were using the "notur" module to run ADF or other software, then you still need to continue using it.

For information about how to reach the "new" packages, before we make this scheme default, see in the software section :ref:`new_scheme`.

0 comments on commit eddf7b3

Please sign in to comment.