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

Running on HPC clusters (Torque/Slurm) #117

Open
namheegordonkim opened this issue Nov 15, 2018 · 0 comments
Open

Running on HPC clusters (Torque/Slurm) #117

namheegordonkim opened this issue Nov 15, 2018 · 0 comments

Comments

@namheegordonkim
Copy link

namheegordonkim commented Nov 15, 2018

I'm using Torque and Slurm in conjunction with Jupyter. I managed to confirm these facts:

  • When Jupyter is running on a head node (that is, not one of the HPC nodes but the login node connected to the rest of the Internet), matlab_kernel works well
  • When Jupyter is running on an HPC node via interactive session, matlab_kernel does not work. I see Assertion failed: nbytes == sizeof dummyon Torque, and the kernel never successfully connects on Slurm (i.e. Replacing stale connection while doing something as simple as disp('hello'). I also observe matlab.engine.EngineError: Transport stopped.).
  • When Jupyter is running on an HPC node via interactive session, Python and R kernels work well as intended.

I'm trying to figure out if this is an issue with a particular HPC configuration or an issue with matlab_kernel. Has anyone else experienced the same?

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

No branches or pull requests

1 participant