| Table of Contents |
|---|
...
Evaluation
Current solution
The initial request was to enable users to set-up working environment easily providing possibility of choosing:
...
- in most cases users specify only "
module load imasenv"or "module load imasenv/<dd-ver>" - UAL is a "yet another library" that don't has to be set separately (
"ual/<al-version>"part of schema) - users usually don't take into account AL version and other libs version... and use defaults
- there is a need to couple imasenv with particular wpcdenv version:
- currently imasenv loads default wpcdenv
- all imasenv libraries can be not compatible with other wpcdenv version as being used during compilation
- loading manually wpcdenv by user and than imasenv can result in inconsistent environment
Simplification of wpcdenv/imasenv schema
Propositions to simplify mechanism for setting working environment base on initial David C. suggestions (yes, Dave, I should follow your hints):
...
| Info |
|---|
Defaults Please note that module system allows to provide defaults on every level of module structure. So, taking imasenv as an example there is :
"WPCD products" ETS workflow is the most complex product being developed by WPCD, however WPCD activity is not limited to ETS development, so this document will refer to "WPCD products" keeping in mind that in most cases it is synonym of "ERTS workflow" |
...