You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an easy way to get access to a clean representation (non-hybrid) of the ligand trajectory at lambda[0] and lambda[-1]? Maybe I'm overcomplicating the indexing procedure, but actually it seems quite tedious.
In an ideal world I would envision something like an extra flag for the reader, e.g.:
I just realized that I was indeed overcomplicating the indexing, it seems that the lambda state is stored in the bfactor field (with 0.25, 0.5, 0.75 corresponding to state A, both states, and state B respectively). So getting a clean trajectory just involves something like this:
Ah yes, thanks for raising this @tlhr - the bfactor hack is.. well kind of a hack, we probably need to find a better long term solution to this problem and/or make sure it's well documented!
Is there an easy way to get access to a clean representation (non-hybrid) of the ligand trajectory at
lambda[0]
andlambda[-1]
? Maybe I'm overcomplicating the indexing procedure, but actually it seems quite tedious.In an ideal world I would envision something like an extra flag for the reader, e.g.:
This would make subsequent analyses a lot easier!
The text was updated successfully, but these errors were encountered: