Skip to content
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

Centrally managed neurocommands #261

Closed
marcelzwiers opened this issue Jan 29, 2024 · 3 comments
Closed

Centrally managed neurocommands #261

marcelzwiers opened this issue Jan 29, 2024 · 3 comments
Assignees

Comments

@marcelzwiers
Copy link
Contributor

Installing neurocommands on our HPC works as expected, following the instructions from the documentation. This installs modules and containers in the user directory. What I would like to do is:

  • Install it for all HPC users, e.g. in /opt/neurocommand/. Can I ask our sys admin to do just that or is there something that needs to be adapted (e.g. the build script)?
  • Install it without changing the Python base environment. I know that can be done using venv (or conda or so), but would that require users to activate that environment before running neurocommands? Or is the Python venv not needed to run neurocommands and can I simply run the build script in the venv, fetch containers, deactivate it, and then load the module and run neurocommands in the base environment?
@stebo85
Copy link
Contributor

stebo85 commented Jan 29, 2024

Dear @marcelzwiers

yes, you can install neurocommand in a global directory for all users on an HPC. /opt/ might not be the best location and I would suggest a network-mount that's available on all compute nodes.

The python environment is only needed for installing it, not for using it. So you can do exactly what you said: Install the containers in the python environment for neurocommand and then change back to the base environment for using them. The users of the HPC would only need to add the modules directory to their lmod modulepath (or run module use).

Let me know how you go with this and if the documentation needs more details on this

Thank you
Steffen

@stebo85 stebo85 self-assigned this Jan 29, 2024
@stebo85 stebo85 moved this from New to Waiting on External Input in NeuroDesk Jan 29, 2024
@marcelzwiers
Copy link
Contributor Author

marcelzwiers commented Jan 29, 2024 via email

@github-project-automation github-project-automation bot moved this from Waiting on External Input to Completed in NeuroDesk Jan 29, 2024
@stebo85
Copy link
Contributor

stebo85 commented Jan 29, 2024

Great :) I added more details to the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Completed
Development

No branches or pull requests

2 participants