First pass at updating prose to match user guide#1016
First pass at updating prose to match user guide#1016ddietz89 wants to merge 4 commits intoolcf:masterfrom
Conversation
| $ module load cray−python/3.11.7 | ||
| $ python3 −m venv ve.rp | ||
| $ module load cray-python | ||
| $ python3 -m venv ve.rp |
There was a problem hiding this comment.
this explains why I ran into weird problems earlier. I kept getting errors along the lines of cannot find file /path/to/working/dir/-m
software/workflows/rp.rst
Outdated
|
|
||
| $ git clone https://github.com/henrymonge/chroma_rp.git | ||
| $ cd chroma_rp | ||
| $ ./compile_chroma/build_stack.sh |
There was a problem hiding this comment.
neat I imagine this is why I ran into errors that were hard to debug
There was a problem hiding this comment.
I think you also need to be in the compile_chroma directory. At the end of the script it looks for ../setup_tasks_example.py
There was a problem hiding this comment.
additionally, it asks to source a file. so it may be worth adding the command here: source ./env.sh
There was a problem hiding this comment.
Will add a note to edit the env.sh as there's some module loads and what not that may not work. Looks like you can set install paths and such in there too.
software/workflows/rp.rst
Outdated
|
|
||
| $ git clone https://github.com/henrymonge/chroma_rp.git | ||
| $ git clone https://github.com/olcf/workflow-examples.git | ||
| $ cd chroma_rp |
There was a problem hiding this comment.
this will either need to be cd workflow-examples/chroma_rp or
cd workflow-examples
cd chroma_rp
software/workflows/rp.rst
Outdated
| $ cd chroma_rp | ||
| $ ./compile_chroma/build_stack.sh | ||
|
|
||
| The user will be required to edit the ``setup_tasks_example.py`` and ``chroma_rp.py`` to your desired workflow |
There was a problem hiding this comment.
This instruction may need to come before the above code block because build_stack.sh seems to depend upon setup_tasks_example.py
|
OK, clarified that a bit to get the relative paths right and a note to edit the env.sh as necessary. |
2 participants
No description provided.