Jonathan --

As I am not yet that familiar with this project, this is only speculation, but as I understand it, the docking software we are running does not checkpoint as often as we were used to with the Human Proteome Folding project and, I believe that no graphics are produced before a checkpoint has been taken. It may be that when you exited and then returned, you were taken back to square one on that work unit. I do know that the World Community Grid application developers will be changing the checkpoint interval as well as reducing the memory requirements at some point in the future. Perhaps one of the Techs may be able to shed more light on this.

Best Regards,

I ran one whole unit that didn't show any docking activity at all.
The current one is more interesting, with a lot going on.

UDMonitor also shows that the checkpoints are extremely variable. I have seen saves every 4 minutes, every 7 minutes, and every 41 minutes so far...on different workunits on a fairly fast computer.

I am ignoring the first 2 speedy server-test workunits that only took 20 minutes total for each one. That is not the norm now with normal sized ones.
These AMD computers are running workunits in 3-5 hours each now.

Observation: There's a green moving line in Best Docking Energy graph "C". A checkpoint seems to be taken when it reaches the right side and starts over with another test, as there was a UDMonitor save at that point.

I did have occasion to restart the first workunit that wasn't showing any activity. I lost about 1.5% but the checkpoint was not obvious in the graph, of course.

A dotted red line shows the lowest docking energy encountered so far in the tests.

Jonathan,

This sounds like a potential problem. It is probably just a minor issue and I doubt it would affect the quality of your results. We'll be looking into it.

As for the 'green line' observation, this is correct. The C-panels X-axis represents one complete docking run.

Time for units of work as well as checkpointing interval will vary a decent amount. The docking parameters can produce quite a variance where this is concerned. It has to due with the type of ligand it is trying to dock, because the size affects the time of the search I believe.

Hmmm. That makes me wonder now. Is there a way of getting the stats for individual work units?

For example, with BOINC, you can get a list of recent WUs that shows you which ones validated successfully, which ones failed and therefore gave you 0 points, how long they took to complete, etc.

I 'spose I couldah started a new thread, but how about total graphics failure all together??? :

From the OK dialog box:

"Error switching to module graphics"
"Error Number: 364"
"MSG: Object was unloaded"

Going from the Main Window to the Application Window has no visible results. Then clicking on the Preferences button and then to Application button gets that error...