Hello everyone,

Thanks for your continued support. We are pulling down N-Body for the time being. We appreciate your feedback and are currently working on the next release.

We plan to test some of the absurdly credited WUs as well as fix some of the bugs that have been recurrent.

Thank you for your patience,

Jake

Acknowledged...

Any idea when we will try again?

Just so we know when to start looking for the next test run. ;-)

Do you want us to kill those in progress or run them to completion. Eg. I've got a couple of 100+hr estimate WUs with only a few hrs done so I wouldn't mind aborting them, but someone with 100hrs invested in a WU would rather let theirs run such as dhrosier whom I have just replied to in another thread

We expect to try again very soon. The tests were a huge improvement on 1.02. I don't want to make any promises, but I would like to have something out in the next week.

You will be getting work units still in queue for awhile to come, but abort them if you so desire. They won't be helping us anymore.

Jake

Roger that....

Will keep my hosts on hot standby. :-)

Are you planning to run the next batch as true multi-threaded applications?

Do you want any help checking your MT <plan_class>, if so?

Did you really mean the Linux apps to run as OpenCL applications on GPUs under Linux, as shown on the Applications page?

Roger that....

Will keep my hosts on hot standby. :-)

I'm on NNT already, and I'll be ready to dismantle/rewrite my app_info when the word is posted.

Hi,

I'm totally new to BOINC and Milky Way @Home, so bear with my ignorance...

You said running N-Body tasks is now pointless, as the results won't be useful to you.

I still get N-Body tasks from you. Is there a way to avoid them until they are needed again?

For how long will they be sent, as you mention there are some still in queue?

Thanks.

I still get N-Body tasks from you. Is there a way to avoid them until they are needed again?

Disable N-Body Simulation in your MilkyWay@Home Preferences. From what I understand it would be however better for the project to accept them and abort before they start.

---

Disable N-Body Simulation in your MilkyWay@Home Preferences. From what I understand it would be however better for the project to accept them and abort before they start.

Alright. Thank you. I'll keep all applications active :)

I just aborted two with ridiculous run times but unfortunately didn't realise they were running in the first place. Will I get any credit for wasting so much CPU time ( over 300 hrs !!! )

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

also both those units are still out there wasting someone elses time. Can you not perform a server side abort ?

I just aborted two with ridiculous run times but unfortunately didn't realise they were running in the first place. Will I get any credit for wasting so much CPU time ( over 300 hrs !!! )

No, you aborted them.

Can you not perform a server side abort ?

That would be indeed very good if possible and IIRC it was done on other projects, but might be not possible here.

---

So, I take it N-Body Simulation 1.06 should be aborted. My Intel MacPro has 240:33:00 elapsed time with 549:28:00 to go running at high priority and a deadline that has past - Wed Feb 13 21:37:36 2013. Some definitive explanation should be posted on this thread, as I don't exactly know what you mean by "taken down". That could mean no new WU's are being issued, or WU's in progress should be aborted. Thanks for any help. I hate to abort with so much elapsed time, but would rather be putting my machine to better use if it's pointless to continue.
Thanks

No, as you can read above in message 56990, only 1.02 WUs should be aborted.

---

Thanks very much for your quick answer. I'll keep my processors working on it then.