Shortly, there will be release of N-Body 1.07. Hopefully, many of the issues on the Windows clients will be resolved. I plan to upload a search with an improved likelihood calculation and a fixed simulation time. We are making a lot of progress with N-Body's development thanks to the excellent userbase. We really appreciate your feedback.

Jake

Are the linux plan class issues going to be sorted out? I have a job using 8 threads in the ati_opencl plan class that boinc thinks is only using 5% of a cpu

My first 1.06 finished last night successfully ... however I don't think the cobblestone Wh...s will be happy with the credit! (Workunit 303830201)

Wall time 379,018 sec (4d23h12m25s), CPU time: 1,315,527 sec, credit: 3,004.90 :-(

if this had been the "de_separation_15_sSgr_1" kinda' runs the credit would have been about 33,000 cobs.

Perhaps a tweak in the code is in order :-)

Ed F

Are there any other modifications on the linux side. I have a work-unit at the moment that has the remaining time increasing steadily. The completion estimates I did yesterday and today at 18:00 GMT both say that the unit will complete well after the deadline date. I suppose that my question is was there a timing issue and why were 1.06 units behaving this way? I do not like aborting a unit and for the first time actually did. The unit I have now I am going to leave running and see what happens!!!!!

James

by the way ... It sounds completely crazy BUT ...

While the WU was running my computer clock was 1 hr behind real time (switch time zones??) ... after the WU finished ... my computer time is back to normal ....


Now that is strange!!

Ed F

Shall I let it run, even after the Deadline ???
Will that help the science - to validate this WU id 291600433 ? :o)

It will take at least two times 1 milion 800 thousand seconds in total ... on my core i7 720QM 1.6 GHz !
... eventhough: I let it run alone sometimes (TurboBoosts to 2.8 GHz).

See the time it has taken for a Core i5 at 3.1 GHz here:

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=291600433

*Thanx*

---

Melwen - Child of the Fangorn Forest
Rig "BRISINGR" [ASUS G73-JH, i7 720QM 1.73, 4x2GB DDR3 1333 CL7, ATi HD5870M 1GB GDDR5],bought on 2011-02-24

Will the server accept the finished RESULT (if no computation error appears) AFTER deadline ?

Thanx :)

Will the server accept the finished RESULT (if no computation error appears) AFTER deadline ?

If you return it before the last wingman: yes.

---

I am looking into the calculation times and the long runs.

We did sweep parameter space to shake out some errors for the code side.

We will be tightening up the parameters in future runs.

As for the new version Jake is running some tests against work units to verify the math coming out.

Once I get the ok on that I will test it across the platforms. And get the new versions out.

We are shaking out the bugs that come out in the extreme ends of the data so to speak.

I am trying to get everything in place shortly to update the binaries I will put a new heading in here for that.

I will be pushing out the binaries and verifying the binaries have gone out before starting the science runs.

The last wingman ???
Is it the one computing it using NBody 1.06 NVidia-opencl ?????? I have no chance I think. :O

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=291600433

The last wingman ???
Is it the one computing it using NBody 1.06 NVidia-opencl ?????? I have no chance I think. :O

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=291600433

Well, he's managed to get quite a few valid results running non-GPU code on his GPU:

Valid MilkyWay@Home N-Body Simulation tasks for computer 496658

But I suspect your big task may be another to drop down the Too many errors (may have bug) plughole:

Task 291533448 (I'm the one with the 1.5 million seconds CPU time).

Is there going to be a 32 bit Windows or Linux GPU version of the N-Body application released?

---

Thank You!

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=291600433

Update: My extreme-unit is at 50.7 % now!, running at 2.67 GHz most of the time... as I let it alone to Turboboost CPU...

The last wingmen now is a XEON at 2.5 GHz !
// XEONs are extremely effective per clock cycle - but my core i7 is also.

Shall I let it run, even after the Deadline ???
Will that help the science - to validate this WU id 291600433 ? :o)

It will take at least two times 1 milion 800 thousand seconds in total ... on my core i7 720QM 1.6 GHz !
... even though: I let it run alone sometimes (TurboBoosts to 2.8 GHz).

Ah, so I am not alone in having a mega-second WU. I had one:

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3148&nowrap=true#57268

I seem to be getting a succession of "Completed, validation inconclusive" results.

Task 	Work unit	Computer 	Sent 	Time reported or deadline	Status 	Run time 	CPU time 	Credit 	Application
399803703 	291524669 	462901 	10 Feb 2013 | 12:36:32 UTC 	18 Feb 2013 | 3:52:29 UTC 	Completed, validation inconclusive 	659,757.00 	1,561,110.00 	pending 	MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia)

I don't know if I ever got any credits for that. :-(

I have an extremely long one as well

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=294575850

It has been running for 124 hours and is not quite 42% done. The deadline is the 23rd, which I won't make, but it has run to completion on one other system so it is possible.

---

Are long-running N-Body 1.06 worth running at all, or do they all error out?

All the ones that promised to run for 75 hours usually errored out pretty quick for me, but now I got one that's been running for 80 hours already, and estimated time has now changed to 112 hours and is still growing.

Despite the increasing estimated time, it managed to get to 33% completed so far.

With all that said, should I abort it or let it run? I'm guessing it will run for 160 more hours and it would be a shame if it just died eventually, like other 75-hour N-Body 1.06 runs.

This is the WU in question: http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=305973763

My computer is the 495319 one.

This is the WU in question: http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=305973763

My computer is the 495319 one.

All error on that WU happened with 0 run time, so you don't seem to be affected by that error. The first computer is also probably still running it, it has timed out for him already, but the last contact was the 17th, so he is probably alive.

I mean, nobody can tell you, if it will error out or not, you have to try it. If everyone aborts all WUs, that eventually might error out, how shall anyone get to know, if they really error out and why? In science also something that didn't work might be a valuable result.

---

I mean, nobody can tell you, if it will error out or not, you have to try it. If everyone aborts all WUs, that eventually might error out, how shall anyone get to know, if they really error out and why? In science also something that didn't work might be a valuable result.

Alright :) I'll keep it running :D (37.6% right now). Thanks for replying.

All error on that WU happened with 0 run time, so you don't seem to be affected by that error. The first computer is also probably still running it, it has timed out for him already, but the last contact was the 17th, so he is probably alive.

I mean, nobody can tell you, if it will error out or not, you have to try it. If everyone aborts all WUs, that eventually might error out, how shall anyone get to know, if they really error out and why? In science also something that didn't work might be a valuable result.

So now my run completed successfully, and another box tried to run it unsuccessfully. The message now reads "Too many errors (may have bug)" and "Completed, can't validate"

Will my result now be discarded, or is it somehow possible for me to validate it (or for someone with my type of box to run it... not sure why I'm the only one without errors).

Just curious.

I also have a 1.06 N-Body workunit that has run for 43.5 hours and is 37.8% complete.

Since there are 5 other failed tasks on this workunit, should I let it

run hoping to get another user to complete this workunit?

Someone mentioned that they do not need 1.06 Workunits anymore?? If so

is the proper procedure here to abort 1.06 WU in favor of 1.07?

Thanks