Open GiovanniBussi opened 11 years ago
I remove this issue from milestone 2.1 as I think it is too difficult to solve it quickly
would not be enough to reset the fluctuations estimate upon exchange? I think anything else would be utterly complex for such a specific case
This was discussed in #25 and was closed adding a check that crashes the code. It would be nice to implement the possibility to do something inside plumed upon exchange (need to change the MD patch to pass this extra info).