Resolved. . . completed in a little over 12 hours.

Occasionally the client is being confused about the percent progress and goes wild. Some have seen 700-800-900% maybe more for HCMD2. There are presently 2 cut offs for this science:

- At 6 CPU hours there's a soft cut off if > 40% of the positions in the task have not completed and the position being computed at the 6:00 hours is finished and task closed. If the algorithm determines early in the task it wont be able to complete the first 60% [of positions], it will show as going from 0-100% properly, but if positions in a task are variable in effort, easy and hard ones, the application and/or client might get it wrong... let it run.

- At 12 CPU hours there's a hard cut off, no matter how many positions left.

Elapsed time in a client will show more, so you need to look in the task properties to see the true CPU time.

HCMD2 is not known to fail, in fact it's got an extremely low error rate and most of these come from systems that were too busy doing other things, tasks dying because of so-called loss of heartbeat (BOINC client not sensing pulse from science app).

In short, unless the CPU time has gone beyond 12 hours, just let it run, else, suspend task and ask on forum. If a system has been running for a long time [weeks], then a soft-boot [don't use the power switch] will refresh the system. It's helps at times for a task to restart from last checkpoint. If you though look in the task properties and see the ''last checkpoint'' time just being a short while ago and CPU time incrementing... just let it run.

--//--

Addendum: what can be seen in task properties of a running job:

Computer:	MyMachine
Project	
	
Name	c4cw_target04_037017397_0
	
Application	c4cw 6.40
Workunit name	c4cw_target04_037017397
State	Running
Received	04-07-2011 08:05
Report deadline	14-07-2011 08:05
Estimated app speed	1.59 GFLOPs/sec
Estimated task size	40009 GFLOPs
CPU time at last checkpoint	02:28:47
CPU time	02:30:35
Elapsed time	02:40:42
Estimated time remaining	04:44:23
Fraction done	37.953 %
Virtual memory size	83.47 MB
Working set size	73.27 MB
Directory	slots/2
Process ID	4952