-
Notifications
You must be signed in to change notification settings - Fork 14
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
Initial version of a BBP oriented FAQ #458
Conversation
This is the start of a FAQ to cover some of the idiosyncrasies I have run into with spack. Please add anything else you have run across. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed some details.
@mgeplf can't add you to approve my changes. Thoughts?
They're mostly line-breaks, right? I did a single line per sentence on purpose to make the diffs easier to read: so that a reflow of text doesn't force someone to eye-diff each word. |
@mgeplf, some habitual formatting. I actually prefer sentence fragments (everything separated by a comma, for example) on single lines when editing LaTeX, but here I'd actually be for enforcing stricter formatting, since the plain text should be easy to read. I sprinkled in some wisdom about |
spack module tcl find --full-path ed | ||
``` | ||
|
||
At which point, you should be able to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to get my modules accessible, I needed to:
MODULEPATH=/gpfs/bbp.cscs.ch/home/bcoste/software/modules/tcl/linux-rhel7-x86_64:${MODULEPATH}
otherwise I would get something like:
ModuleCmd_Load.c(213):ERROR:105: Unable to locate a modulefile for 'psp-validation/my-custom-version/python3/serial'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessarily :)
I ended up removing my ~/.spack/modules.yaml(created from the README instructions), only then I saw the module and managed to load it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, @wizmer are modules inaccessible even when sourcing the Spack env?
the module system. | ||
To find the module that was built, issue: | ||
``` | ||
spack module tcl find --full-path ed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this equivalent to
spack module tcl refresh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I understand, no. This will have a side effect of rebuilding your modules.
Well, let me know what you chose. Github handles line wrapping fine, imo, but line breaks pretty much mean that I can't tell what you added/changed.
Ok, good to know. |
I tend to just read the source, where overly long line mess with me. The rest of our documentation is also nicely wrapped. |
No description provided.