Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A suggestion on recognizing where modules are loaded throughout the workflow #69

Open
jefreer opened this issue May 12, 2021 · 0 comments

Comments

@jefreer
Copy link

jefreer commented May 12, 2021

It might be good to note somewhere in 'general help' all the scripts where modules are loaded and so that these might need to be changed for local computer systems. The alternative is to have a general read file where you can specify each type of module load once and then all scripts can grab what they need from there. Especially when you have module loads that are very specific to certain machines - i.e. having to strip out nixpkgs/16.09 each time. So it could have the module line specific for each load and then a numeric value to say if it needs loading or not (1 = yes, 0 = no). It would be a huge help because at the moment on a different machine you have to edit every script with hard wired module loads and this could clearly be avoided down to one module load file input that specifies them for each machine for all .sh scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant