-
Notifications
You must be signed in to change notification settings - Fork 35
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
MDAnalysis 2.0.0 issues #356
Comments
Hi and thank you for letting me know. I will look into this and get back to you as soon as possible.
M
On Sat 22. Jan 2022 at 16:07, Rowan Walker ***@***.******@***.***>> wrote:
Hi there,
I'm finding that when I upgrade my MDAnalysis package to the latest version 2.0.0 pytim stops working for me. It imports fine but pytim.ITIM hangs when called on a Universe.
Creating a conda environment with the previous MDAnalysis version 1.1.1 seemingly solves the issue: conda create -n new_env -c conda-forge mdanalysis=1.1 pytim
I would like to be able to use the latest version of MDAnalysis as Universes can now be pickled paving the way to easier parallel analyses. Do you know if this would be true of a Universe that has first been analysed with pytim.ITIM?
Cheers,
Rowan
—
Reply to this email directly, view it on GitHub<#356>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADRZD53QV5WQVFOIZY4DXTUXLB2TANCNFSM5MSCQV7Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
…------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr. Astrid Lambrecht,
Prof. Dr. Frauke Melchior
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
|
So, a quick test with MDAnalysis 2.0.0 does not show any problem for me: In [1]: import MDAnalysis as mda
...: import pytim
...: from pytim.datafiles import LJ_GRO,LJ_SHORT_XTC
...: print('mda version:',mda.__version__)
...: u = mda.Universe(LJ_GRO,LJ_SHORT_XTC)
...: inter = pytim.ITIM(u)
...: for ts in u.trajectory[:2]:
...: print(inter.layers[0,0].n_atoms)
...:
...:
mda version: 2.0.0
1227
1184 This is with the latest commit from the Could you post a minimal example that triggers the issue? Then it would be easier for me to understand what's going wrong. Let me know also which version of pytim you are using. |
In the meantime, I fixed some issues with MDA 2.0.0. They went unnoticed because Travis dropped support. Now I switched to CircleCI and automated testing should be back on track. Please check your issue also with v0.9.0 from the GitHub repo. I will soon provide packages for PyPI and Conda. |
PyPI and Anaconda packages for v0.9.0 are now available |
Thanks so much for getting back to me! The issue is resolved with the v0.9.0 PyPI package. Conda-forge channel still shows v0.8.4, will this update soon? The issue I had can be recreated with: conda create -n test -c conda-forge mdanalysis pytim=0.8.4 then if I ctrl-C out of pytim.ITIM hanging: `
|
OK, thanks for the details, that was clearly a problem with multiproc, which, apparently, was triggered only using conda. At the moment I have no idea why that happened, but I will make sure to test the conda packages in the future to avoid problems like this, thanks a lot for reporting the issue! About the package, I see v0.9.0 already available on https://anaconda.org/conda-forge/pytim
|
BTW, it would be great if you could report on any successful/unsuccessful experience with parallel analysis. |
Ok so unfortunately the multiproc issue is still occuring with the v0.9.0 package downloaded with conda If I create a conda environment and then instead install pytim v0.9.0 with the PyPI package there are no issues. Parallel analyses (such as those outlined here: https://yuxuanzhuang.github.io/UserGuide/examples/analysis/custom_parallel_analysis.html#Parallelization-in-a-split-apply-combine-fashion) on a Universe that has first been analysed with pytim.ITIM are also successful. I will play around further and get back to you. |
OK. I'd suggest first trying with multiproc disabled, e.g. inter = pytim.ITIM(u,max_layers=4, multiproc=False) to check that there are no other issues. |
Maybe related to this issue ? |
my mistake sorry, conda v0.9.0 package is working fine, my new conda environment was still using a previous PyPI 0.8.4 version thanks again, happy to close the issue, if I find anything interesting re parallel analysis I will let you know :) |
great, thanks! |
Hi there,
I'm finding that when I upgrade my MDAnalysis package to the latest version 2.0.0 pytim stops working for me. It imports fine but pytim.ITIM hangs when called on a Universe.
Creating a conda environment with the previous MDAnalysis version 1.1.1 seemingly solves the issue: conda create -n new_env -c conda-forge mdanalysis=1.1 pytim
I would like to be able to use the latest version of MDAnalysis as Universes can now be pickled paving the way to easier parallel analyses. Do you know if this would be true of a Universe that has first been analysed with pytim.ITIM?
Cheers,
Rowan
The text was updated successfully, but these errors were encountered: