-
Notifications
You must be signed in to change notification settings - Fork 2
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
Change (make flexible) placement of loadR.sh in sbatch_master #10
Comments
as we discussed, I changed #!/bin/bash
. /gscratch/csde/spack/spack/share/spack/setup-env.sh
module load r-4.0.0-gcc-9.2.0-p7wezul to #!/bin/bash
. /gscratch/csde/spack/spack/share/spack/setup-env.sh
spack load [email protected] and it gives me the following error:
is there something I am doing differently than you? |
Hmm... no I think it is the same. After you run |
Can you restart your session, load spack, and then run |
|
what do you have listed here: |
I was actually looking into it:
|
ok try this: spack load [email protected], spack compiler find (this should add 9.2.0 to your .yaml), restart session, load spack, spack load [email protected] |
does not work either.
I think I need to do
to register it |
wait, did you do spack compiler find after spack load [email protected]? |
no, just |
try this sequence, as suggested above: |
my bad, I read to fast. It worked this time. |
excellent, can you add this step to any instructions on statnet/computing? |
On it, where on the repo do you want me to put that info?
|
I was thinking somewhere on this readme: https://github.com/statnet/computing/tree/master/build |
I updated the "loadR.sh" file in "build" and added an explanation on how to correct the missing compiler error. I also modified the "reproducible env" README saying that "loadR.sh" should be copied in the project's folder. I made linked to the "build" README so the user can know where to look |
cc: @AdrienLeGuillou
After that, change Hyak instructions on https://github.com/statnet/computing/tree/master/slurmLite
after that, address wiki issue here: statnet/computing#6
The text was updated successfully, but these errors were encountered: