I had to reduce the amount of work because we change the protein and I was expecting some nasty problems. I didn't want to distribute many of those. Now it seems to be stable and we are going back to our usual generation of work.
I had to reduce the amount of work because we change the protein and I was expecting some nasty problems. I didn't want to distribute many of those. Now it seems to be stable and we are going back to our usual generation of work.
Opposite problem! One of my machines has suddenly been flooded with wu's, (flooded in relative terms, a lot more then usual shall we say - couple of pages), all claiming to have a run time of 00:03:08.
The one running at the moment has been running 00:03:00 and is showing 3.356% complete and the time to completion is going up at the same rate as the CPU time.
Errrr....
*** EDIT ***
They do seem to be finishing very quickly. The percentage completion wanders up to 2-3% then jumps to 100%. The time to completion is nonsense.
Weird things are occurring. Looks to be happening to many though.
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
I've also had some tasks run for less than 2 min's, is there a problem
with these tasks. I haven't seen any error messages.
pete.
G'Day Pete,
Doesn't appear to be a problem, just different WU type from previous (new 1c1r, old 1t7k which took over 2 hours for me).
Mine run from 100 odd seconds to over 6,000 seconds, for the same WU type.
This happens on both Windows and Linux.
The amount of credit awarded for the new work is still the same as before (quite low), so this has not been adjusted like indicated by Michela, still waiting for that change.
____________
There is no error with those workunit finishing too quickly, at least not from you. It is because the new protein tends to have more energy violations than the previous one and many conformations fall into this energy violation and return too quickly. we change the tolerance to try more times before to return this energy violation, and also we increased the threshold of the energy before to be considered a violation from 1200 to 5000, but I'm not sure it is taking effect.
Well the message is: there is no error from the BOINC clients, is the specific protein-ligand the problem, we are trying to find how to be more tolerant to those energy violations, but is gonna take some time.
I seem to be getting a lot of these again, most finish quickly between
1 min & 20 min showing the same in my messages. On both rigs.
Calling BOINC init.
Starting charmm run (initial or from checkpoint)...
WARNING - Total energy change exceeded . Code101.
Resolving file charmm.out...
Calling BOINC finish.
pete.
____________
ID:
4662 | Rating: 0
| rate:
/
Test
Joined: Aug 5 08
Posts: 4
ID: 392
Credit: 0
RAC: 0
Yes, I know =( they will continue probably. It is because of the structure of the ligands. I hope the next round will be better. Once we finish the trypsin we will use a different protein and model and hopefully the workunits will be longer
Its is gonna be a low production in the following two days because we changed the model and we want to be sure everything is working as supposed to be. We don't want to discover that there is an error and that a massive amount of work ahs to be restarted. So far everything looks fine, and we will increase the work produced slowly.
Sorry for the inconvenience, but thank you for your patience =)