I've started some new separation runs:

de_separation_15_sSgr_1
de_separation_16_sSgr_1
ps_separation_15_sSgr_1
ps_separation_16_sSgr_1

These should run fine, but let me know if you see anything weird. Milkyway@home is moving along nicely!

Cheers,
Matthew N

Below are details of a task that appears to be out of control. The deadline for this is 1/29/2013 so it is impossible to complete even if the time Remaining stopped increasing. I apologize for the format, I have tried everything I can think of to get the items below into columns in my Reply but I cannot.

Total
Date Time Work Done Elapsed + Remaining
1/17/2013 11:49 PM "851,392.06" 15:20 + 396.26 = 411.46
1/18/2013 1:11 PM 28:41 + 408.04 = 436.45
11:58 PM no 39:27 + 417:35 + 457.02
1/19/2013 9:48 AM changes 49:19 + 425.31 = 474.60
1/19/2013 4:38 PM """" 62:11 + 436.23 = 498.37
1/20/2013 10:34 AM """" 74:04 + 445.58 = 520.02
1/20/2013 11:37 PM """" 87:07 + 456.34 = 543.41
1/21/2013 11:32 PM """" 111:03 + 476.29 = 587.32
1/22/2013 12:18 PM """" 123:48 + 482.40 = 606.28
MilkyWay@Home N-Body Simulation 1.04
de_nbody_100K_1_1356215205_101619_1

Hi DH,
Your post would sit better in one of the N_body threads; perhaps some nice moderator could move it there for you.

In reply meanwhile:
The run time estimates here have been way out for a while. I have found that once those with an increasing estimate get to about 45% or so progress, the time remaining starts to come down again, and tends to accelerate so if it's about that Progress then you may not have as long to go as it's telling you. My longest one estimated 300+hrs at one point but finished in 112hrs. Currently I have one with 270+hrs to completion (increasing) after <1% but completed in 184Hrs for my wingman. Others have had similar and even longer.
I'm guessing it's de_nbody_100K_104_1_1356215205_101619 which has already timed-out for your wingman so maybe it is just far too big. Maybe somebody in Admin can help you further as to what to do with it. If it's still chugging along happily, it would be a shame to lose it. If you keep it going, it might be prudent to increase the space allowed for Boinc, just in case the logs get too big.
Good luck with it.

(Edited for typo and bad grammar)

Hi Ray,

Your thoughtful posts help a lot. I am a retired actuary, not stupid but need and happy to have all of the help I can get in this activity.

I am running an I7 CPU so the strange job uses only one of those, the other 7 are running merrily along. I will let the oddball roll until it either completes or the project people tell me to Abort it.

FLASH! I just checked Tasks, the current status is 152:56 + 499:44 = 652:40 and Remaining appears to continue rising.

A few months ago I had one Task which was able to run all 8 simultaneously. Perhaps that is what the author of this recent fun had in mind.

I have not been active on the threads until now, not much to say that I thought would be worth taking peoples' time.

Dreighton Rosier

Hi again Dreighton,
I think it's probably time to lay that WU to rest 8¬( Check what % progress it has but with completion time still increasing, I suspect it may never finish successfully. Some have had problems if there has been a break in the computation eg. a machine reboot, and the task hasn't properly picked up from it's last checkpoint. These 1.04 tasks have been "Beta test" units and I'm sure the guys have learned enough from them to improve the application but from Jake's post here "...abort them if you so desire. They won't be helping us anymore." I aborted 2 long ones but they had both only done a few hours. It's a shame to lose so much time but maybe better not to waste any more. That's my opinion, but I'm not on staff so you have to decide for youself.

Other tasks have been multithreaded but these ones have been single thread only, probably to simplify debugging and eliminate some reasons for errors. (They could probably be fooled into running multithread but only by those more savvy than me 8¬)