Odd, that test hasn't changed in a while. That said, the error message doesn't really correspond to the current test (but shouldn't be triggered anyway). My guess would be that the Model is confused about what is going on, perhaps due to things not being reset properly after a failed evaluate (but there doesn't seem to be any prior model evaluate calls, so I'm not very sure about that guess). I'll look into it later. If it is blocking, turn off the test in Restraint.cpp:evaluate().
Â
Â
On Sun, Nov 1, 2009 at 5:11 PM, Keren Lasker <">> wrote:
hi,
I think something is wrong now with calling to restraint evaluation. After adding the restraint to the model, I am keep getting the message:
ERROR: ---------------------------------------------------------------------- Traceback (most recent call last): ÂFile "simple_test.py", line 49, in test_ev  Âprint r.evaluate(None) ÂFile "/viola1/home/kerenl/bioinformatics/projects/imp/build/lib/IMP/__init__.py", line 1193, in evaluate
 Âdef evaluate(self, *args): return _IMP.Restraint_evaluate(self, *args) ValueError: Restraint::evaluate() cannot be called during model evaluatio
I think the attached test case should work and I am not sure why it does not .....