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

Jupyter kernel crashes when importing galsim #870

Closed
hsnee opened this issue Feb 20, 2017 · 3 comments
Closed

Jupyter kernel crashes when importing galsim #870

hsnee opened this issue Feb 20, 2017 · 3 comments
Labels
bug report Bug report build Related to compiling, building, installing
Milestone

Comments

@hsnee
Copy link

hsnee commented Feb 20, 2017

Hello, I'm a new grad student at Carnegie Mellon working with @rmandelb on testing the psf modelling errors for lsst.

I installed galsim and it's working fine but when I try to use it in a jupyter notebook, every time I import it, the kernel crashes immediately and restarts. I'm on macOS Sierra 10.12.3, using Python 2.7.9 (Apple's build).

I tried debugging it with ipdb, but it didn't provide any information at all. Any ideas what may be causing this?

@rmjarvis
Copy link
Member

rmjarvis commented Feb 20, 2017

It's hard to say without more information, but it sounds like there is some kind of mismatch in either the python kernel or the search path between Jupyter and the command line Python. I found this discussion on an Anaconda issue page that mentions some of the kinds of issues that can arise. Not sure if any of that is relevant here, but maybe reading through it will give you some things to try.

Also, maybe worth trying a different Jupyter platform. e.g. Pineapple. Not sure which Jupyter you are using, but I typically use the pip install jupyter version, which should use the same Python version as pip, which by default is your system Python. So if you did something different, maybe try the pip version to see if that works better.

@hsnee
Copy link
Author

hsnee commented Feb 26, 2017

Thanks @rmjarvis, that helped a lot -- It was indeed a mismatch problem, both the python version and path were mismatched. It's working now after pointing it to the appropriate paths. I should probably do something about having 5 coexisting python versions installed...

@hsnee hsnee closed this as completed Feb 26, 2017
@rmjarvis
Copy link
Member

Thanks for the update. Glad it's working now. I similarly have quite a few different Pythons installed on my laptop so I can test code against each of them. But it means sometimes things get completely borked and it's not always obvious how to get back to a working state...

@rmjarvis rmjarvis added this to the Will not fix milestone Mar 14, 2017
@rmjarvis rmjarvis added bug report Bug report build Related to compiling, building, installing labels Mar 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Bug report build Related to compiling, building, installing
Projects
None yet
Development

No branches or pull requests

2 participants