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
Exchanges are quite expensive, how would folks feel about the possibility of adding a control parameter for the number of swap attempts?
In the back of my mind I'm thinking that eventually it would be great to build some kind of adaptive approach that minimises the number of swap attempts for a target mixing ratio.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback! That could indeed be useful to have, but can you share an example where the replica exchange/swap is taking too long? Because in my experience this part is pretty fast, so I wonder if we may not be reporting the times correctly, even though I double checked some of the logs I have and they seem consistent with this idea of mixing of replicas not taking long at all.
As part of the above we've found that there seems to be no substantial difference between the numba and non-numba replica mixing loop. This might not be a problem though.
There are cases where the number of replica mixes are probably insufficient (n_windows**3 is a lot lower than what Vytas did in his own assessments for ABFEs for example).
The rationale for the number of swaps we currently do is to ensure that we swap as much as possible without it taking a significant fraction of iteration time. A better approach might be to have a setting that specifies how many seconds to spend on swapping, and then run batches of swaps and check if the timer has exceeded the allowed time.
Exchanges are quite expensive, how would folks feel about the possibility of adding a control parameter for the number of swap attempts?
In the back of my mind I'm thinking that eventually it would be great to build some kind of adaptive approach that minimises the number of swap attempts for a target mixing ratio.
The text was updated successfully, but these errors were encountered: