-
Notifications
You must be signed in to change notification settings - Fork 7
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
Juliacall #13
Comments
Interesting, thanks. |
Got a weird undefined reference error. Maybe we should move to juliacall sooner rather than later? |
I'll open a branch and look into swapping out |
Do you want to run it by the slack ACE channel, in case anyone has a clue what it might be? It's looking more like a pure julia error than a python-julia interface error to me. |
It seems similar as to what's going on here JuliaPy/pyjulia#306? A |
@tjjarvinen, do you have any experience with |
Very little. I am not comfortable with it unfortunately. |
Thanks anyway |
Ugh
|
Previously these segfaults seemed extremely version and platform specific unfortunately. |
I wonder if we need to limp along until we can use pure python (+ C++? LAMMPS?) for evaluation, and pure julia for fitting. |
Probably.. restarting HAL every 30-40 iterations is not workable though... Error message above came from my local Mac install, maybe not that relevant actually. Can someone reading this try
EDIT: my unix cluster also crashed... argh...
Am I doing something wrong? I think it may be unhappy by ASE.jl setting up it's own Python and calling Python ASE again? This connection is very weird and likely causing all this trouble |
Trying this now, but one thing I noticed is that it's using the wrong julia project. When I do the first import it says
even though my JULIA_PROJECT is pointing to the current directory ( |
It's stubborn and likes it's own Project, mine's in
|
does not crash for me. Seems like it dislikes I guess this means we're stuck with |
Actually looking at |
From the |
Well, it overwrote my |
I restored my |
Thank you, I’m on Julia v1.7, this may be the issue. But this kind of brittleness seems familiar regarding this Python-Julia connection… |
Updating |
I think @JPDarby may have also been on Julia v1.7.x, I'll ask him when he gets back next week |
Let's leave this open but if anyone is experiencing problems, please try out |
Anyone had any luck with julia |
I would stay away from it for now. |
I should have mentioned this sooner, but you could consider replacing
pyjulia
withjuliacall
(https://cjdoris.github.io/PythonCall.jl/stable/juliacall/). I believe there is rough consensus that it is the better choice for new projects, but I don't have enough personal experience to say.I thought of it when reading though #12.
The text was updated successfully, but these errors were encountered: