Closed vineetbansal closed 10 months ago
Created a working python version of the hello
template - pyhello
. Simultaneously created a similar pyhello
command.
tigress/LEIFER/communalCode
directory using the tigress/LEIFER/communalCode/wbi
prefixcowsay
package inside the conda environment /anaconda3/2023.9
module by module load anaconda3/2023.9
conda activate /tigress/LEIFER/communalCode/wib
python -c "import socket; import cowsay; cowsay.cow('Hello ' + socket.gethostname());"
Great..I'd be interested to try this out if you can open a PR.
I don't think we should add a pyhello
command though, unless you meant a wbi remote pyhello
. The latter may work automatically if the template is found (I forgot how we programmed this) and we may not need to do anything.
I created both wbi remote pyhello
and wbi pyhello
. I removed the pyhello
command now and opened a Pull Request.
After modifying the hello template to only use bash and getting it to work, we then need to create a working python version of it, (say
pyhello
), but something that activates a custom environment on the cluster.For this to work, we need to make
conda activate /tigress/LEIFER/path/to/conda/env
work (i.e. some shared conda env path that has cowsay preinstalled).This will be a good issue to tackle before issue #10.
The real validation of this would be if someone other than you (who has read/execute permissions on
tigress/LEIFER/path/to/conda/env
) canpip install wbi
and runwbi remote pyhello
, and it "just works".