-
Notifications
You must be signed in to change notification settings - Fork 9
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
AttributeError: 'NoneType' object has no attribute 'select_atoms' #31
Comments
Hi, Unfortunately SLURM is required to run all of the production MD (even though you can avoid it for the setup, as you've found). These instructions might help set it up on your workstation - let us know if there are any issues and we can help out! The error is likely due to your MDAnalysis version being too old compared to your GROMACS version (see this issue). Could you update to the latest version of MDAnalysis and try again please? For example, MDAnalysis 2.9.0 is required if you're using GROMACS 2024.4 (see here). No need to rerun the whole thing - it might be cleanest to delete Calculation.log and Calculation.pkl, then rerun the script, and it should pick up where it left off. Please let me know if that works and I'll enforce the most recent version of MDAnalysis in the environment yaml file to stop this happening again. Thanks! |
Thank you for your support.
Here is the output:
I don't know why this is happening. |
No problem - sorry this still isn't working, and thanks for the details. I'll try and reproduce this locally with your exact script (just to be sure that the slurm=False option isn't to blame, although this seems unlikely). Could you please post the Thanks, you too! |
Ah, just realised that the incorrect number of atoms in the xtc file matches that in the provided |
I'm trying again right now, thanks! |
Hi,
I am currently testing a3fe using the example_run_dir provided. I am running the calculations on a local workstation without SLURM installed. I managed to configure this by setting slurm=False in the SystemPreparationConfig. Below is the script I used to run the calculation.
However, during the setup phase (calc.setup()), I encountered an AttributeError. The error seems related to the restraint selection step, where it tries to use u.select_atoms but fails because u is None. This seems to stem from the trajectory file not being loaded correctly.
Here is the full traceback of the error:
Any help with this would be appreciated.
Thank you for your availability,
Silvia
The text was updated successfully, but these errors were encountered: