-
Notifications
You must be signed in to change notification settings - Fork 0
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
Virtual env is probably not being activated #3
Comments
It must be that when I was testing, the environment in the login node was somehow transferred to the compute node or something. Now the same commands fail. Maybe the ex3 admins changed that behaviour. One potential way of solving this is it move the virtual environments to the @JLenssen FYI |
It turns out that this only happens for specific modules that are available in the login node but not available in the compute node. In this case, 'python-3.8.16' is the culprit. To check if a module is available in the compute module, run this: # enter the compute node in this case: armq
srun -p armq -N 1 -n 256 --pty /bin/bash # check which python modules are available. See if the module you want is in the list
module avail python |
@JLenssen could you have a look at this issue and its related pull request? |
Hi @ch-ahindura , yes I'll try to check it this week. Unfortunately, quite busy atm. |
Sure, no worries. When you have time. |
Issue
When we run the command below in ex3:
where sample.py is
It raises the error:
line 6: python: command not found
The text was updated successfully, but these errors were encountered: