-
Notifications
You must be signed in to change notification settings - Fork 11
TypeError: 'restraint' must be of type 'BioSimSpace.FreeEnergy.Restraint' for free leg of simulation. #33
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
Comments
Hi, thanks so much for your inofrmation. I guess you resubmitted the run. So what you need to do before rerunning is delete Give it a try and let me know if the progress is going well. Cheers, |
By the way, for you somd.cfg
when using PME, it's best to remove Thanks~ |
Hi, I have removed The results are here, and it seems like the restrain and vanish stages are fine, but I have problems in the discharge state; can you please check and let me know what could possibly be wrong? The files I used as input are the same as above. Here is the comparison of results for MIF from the paper and my target. |
Thank you for the information and very great that you got the results! From your discharge plot, it seems like the issue might be related to somd.pert. Do you use a specific somd.pert file for different stages? Since the discharge somd.pert file controls the electrostatic change, it could be the source of the problem. Would you mind having a quick look? Thank you! |
Thanks for the details @yasirkhanqu and thanks for looking into this @Roy-Haolin-Du. Your PMFs look reasonable to me! Are your final dGs reasonable? The reason your discharge PMFs look very different to ours for MIF is that we used reaction field electrostatics whereas you're using PME. While the PMFs look very different, the difference between the bound and free discharge dGs should be very similar with PME or RF (with a neutral ligand). Also, while it's a good idea to remove |
The problem is that my energies are positive: ###################################### Free Energies ######################################## Also, I used the same somd.pert file, as generated automatically by the workflow. I understand the higher energies for the discharge leg as the active site has a Mn2+ ion. I don't know why the overall dGs are positive. The ligand is charged with -2e, but i have neutralised the whole system. |
Ok, thanks for the details. Could you please share all inputs/ outputs to make it easier for us to debug? The easiest way to do this is likely:
We haven't run any calculations with a -2 (or +2) charge - this is a challenging case but I would hope that we could do better than > 10 kcal mol-1 estimate, especially as the variance isn't crazy. Thanks. |
Thank you so much, @fjclark; I have done as you suggested. The size of the directory is still reasonably high, and it fails to bind here, so I uploaded it to Google Drive. Here is the link: https://drive.google.com/file/d/1gC0VcwNN_rni-QFjEMrJK1pk3uAiWe_c/view?usp=drive_link Please send a request, and I will grant you permissions. Looking forward to seeing how it works out. |
Thanks @yasirkhanqu - I've asked for access. I'll take a look when I can, but I'm busy and might not get to it this week. I'm not sure if @Roy-Haolin-Du has time? Either way, we'll get to it as soon as we cann |
Thanks @yasirkhanqu I’ve also requested access and just got approved. Apologies for the late reply and I’ll review everything in the next couple of days. |
Hi @yasirkhanqu , hope you are well. For the unexpected data, I noticed that in your bound system, the calculation was simulated without using Using co-alchemical ion approach, whereas in the free system, it was used. You can see it in the leg.log file: Then I use to check your ligand charge:
So for your bound system, when you parameterised your complex system, the charged ligand lost its charge, which caused 0 charge recognized. Thanks! |
Hi, @Roy-Haolin-Du. Thank you. I'm OK, hope you are too. I have reprepared the systems. Here is how it looks right now `In [2]: system = BSS.IO.readMolecules(["bound_param.prm7", "bound_param.rst7"]) In [3]: system_lig = BSS.IO.readMolecules(["free_param.prm7", "free_param.rst7"]) I will let you know about the outcomes... btw, I am doing parameterization in LEAP. I have tried several times adding ions and solvents too (in leap), but then a3fe would not recognise the box with an error something like there is no box found or something related... I tried using biosimspace, too, but couldn't get it right. I would be glad if you would let me know. It would help me add a suitable amount of salt as well. |
Good!, looking forward your new system result. For the box issue, OpenMM (like some other engines) has additional constraints on the orientation of the lattice vectors.
If you use a3fe/biosimspace, the box should be fine and could be recognised well. There are two related issues, you can have a look to give more detailed explaination. Thanks. |
Hi,
I am working with a system with a protein, an acceptor substrate of (three) carbohydrate subunits parameterised with GLYCAM, MG2+ ion, and a donor substrate (LIG), parameterised with gaff forcefield.
Everything works fine for the bound leg until this error erupts (which is for the free leg as I can see from the error). I have attached the input files and the overall output.log file. I have also attached the restraint configuration file from bound/restraint/input/somd.cfg. Additionally, I have attached the param files and the restrain folder from bound/restrain.
Here is bound/restraint/input/somd.cfg file.
param_log_restrain.zip
The text was updated successfully, but these errors were encountered: