We have a number of users who work on multiple projects, each of which uses a different environment and in at least some cases the environments would conflict. The user(s) and we think it would be convenient to provide this by adding an option for specifying a file that would be sourced as part of
script.sh.erb. We are also looking at the simpler task of making it possible for users to specify a list of modules to be loaded prior to the main program starting. We are using Jupyter as our test case, but we think it might be worth extending it so that it could be part of other applications.
Our thoughts about error checking are that we should check first whether the file exists, and if it does not, what to do if it does not. It seems straightforward to put that test into
script.sh.erb, but I was wondering whether that test could be included somewhere that it could throw an error prior to job submission and return the user to the application form?
Any suggestions on this? Please note, we are not Ruby programmers, so please be merciful in your assumptions when answering.