Thanks for the Update!
Well be standing-by.

Looks like the download issue should be resolved and I can start working on some of the other issues again.

Jake W.

Yes and No, I got one project of each but cannot get any more.
Took a long time to get new projects after your reset.
827160402 617077081 12 Sep 2014, 20:39:36 UTC 12 Sep 2014, 20:47:01 UTC Completed, validation inconclusive 400.07 52.63 pending Milkyway@Home Separation (Modified Fit) v1.32 (opencl_nvidia)

Also it shows that I have 97 In progress and I have no programs running on this computer ID: 561866.
Looking at ID: 581205 now as this is my other Rig running your projects.

It will take a while for the server to push out some more of my work units because there were so many errors. It tried to distribute them evenly among the different runs and since I had so many sent out earlier it just needs to let the others catch up. Should be back to normal running conditions soon.

Jake W

ID: 561866 is still not getting any tasks.
827160586 617077177 12 Sep 2014, 20:39:36 UTC 12 Sep 2014, 20:47:01 UTC Completed and validated 200.36 26.07 106.88 MilkyWay@Home v1.02 (opencl_nvidia)

Still shows 97 running tasks
827054583 617018049 12 Sep 2014, 16:44:48 UTC 24 Sep 2014, 16:44:48 UTC In progress --- --- --- MilkyWay@Home v1.02 (opencl_nvidia)

I have reset the project a few times now.
Thanks,
Bill

Getting error messages, checked my stats and none of them are processing. I will enclose the "error message," the next time it appears. Mike

Hi Jake,
I have been supporting MilkyWay for a long time and decided to get the T-shirt with my donation. Was disappointed that the shirt did not have a photo of our beautiful Milkyway!!

Second, I just got 750 hours to process BEFORE 23 Sept!! I am on an iMac and do not have that kind of horsepower. Is it OK to abort those that I cannot finish by the deadline?

Larr2000@Gmail.com

---

Hey Larr2000,

Which application is it that is giving you a 750 hour work unit? If it is separation you can abort it. If it is nbody it is probably just not calculating it correctly because the nbody application is notorious for giving incorrect estimated run times. Sorry the shirt didn't have a photo of the Milky Way on it. For future reference the design is posted on the fund raiser page.

Jake W.

Is it OK to abort those that I cannot finish by the deadline?

Aborted WUs simply get sent out to other crunchers sooner than if they go past deadline. If you cannot crunch them, the sooner you abort them, then the sooner they will get completed.

129 invalid, due to Workunit error, validation error etc. 23 error as well

http://milkyway.cs.rpi.edu/milkyway/results.php?userid=135022&offset=0&show_names=0&state=5&appid=

Something definitely is amiss with the new version.

Is it OK to abort those that I cannot finish by the deadline?

Aborted WUs simply get sent out to other crunchers sooner than if they go past deadline. If you cannot crunch them, the sooner you abort them, then the sooner they will get completed.

This may well be true, but each aborted work unit would appear to count as an "error" as far as validation is concerned, with the result that there can be a task that ends up as "Completed, can't validate" because of (typically) two aborts and one genuine crash. To the best of my knowledge, there's no way to stop BOINC treating user aborts the same as errors...

This is no big deal if a GPU job gets wasted, but it's very frustrating if one sees several hours-worth of cpu time black-holed because a couple of users have aborted MilkyWay jobs and someone else's [Nvidia, usually :-)] gpu job crashes.

However, it's been a fairly rare occurrence to date (for me, that is), so I'm merely pointing out a possible down side...

Is it OK to abort those that I cannot finish by the deadline?

Aborted WUs simply get sent out to other crunchers sooner than if they go past deadline. If you cannot crunch them, the sooner you abort them, then the sooner they will get completed.

This may well be true, but each aborted work unit would appear to count as an "error" as far as validation is concerned, with the result that there can be a task that ends up as "Completed, can't validate" because of (typically) two aborts and one genuine crash. To the best of my knowledge, there's no way to stop BOINC treating user aborts the same as errors...

This is no big deal if a GPU job gets wasted, but it's very frustrating if one sees several hours-worth of cpu time black-holed because a couple of users have aborted MilkyWay jobs and someone else's [Nvidia, usually :-)] gpu job crashes.

However, it's been a fairly rare occurrence to date (for me, that is), so I'm merely pointing out a possible down side...

Then there is a problem somewhere in the Server Side software, because aborting a unit is supposed to do nothing more then put it back in the cache of available workunits. Now if you abort too many workunits it CAN decrease the total number of workunits you can get in a day, but as soon as you start returning valid units again that will exponentially pop right back up to normal. The key is to abort what you have to and crunch what you can.

I talked about the aborting work unit problem about a year ago. It is a problem but I don't work on the server side of the project much so I can't personally fix it. I will ask Travis about it again since he is in charge of most server side things.

Jake W.

For info: The following (representative) jobs all errored out over the last couple of days.

ps_modfit_15_3s_130_wrap_const_1_1405680903_7765724_3
de_modfit_15_3s_132_wrap_8_1410552780_140958_1
de_modfit_15_3s_132_wrap_8_1410552780_141748_0
de_modfit_15_3s_132_wrap_8_1410552780_131333_0
de_modfit_15_3s_132_wrap_8_1410552780_133902_0
de_modfit_15_3s_132_wrap_7_1410552780_130778_1
ps_modfit_15_3s_132_wrap_3_1410552780_136533_0
de_modfit_15_3s_132_wrap_8_1410552780_131960_2

This isn't occasional;it's endemic across all modfit jobs on my Windows machine.
Machine is Win7, Nvidia GT640. Currently running MW jobs doubled up, so that may be contributing ...

On the linux box (Mint, 32-bit, Geforce GTX 660) most 1.30 modfit and some 1.32 teststars jobs are erroring out as other folk have reported.

---

SLRE,

Are you using the most recent NVidia drivers for your cards?

Jake W.

SLRE,

Are you using the most recent NVidia drivers for your cards?

Jake W.

There are hints at SETI@Home of a possible OpenCL problem with NVidia driver 340.52 - the problems observed so far relate to Compute Capability 1.x cards only, but that could be the tip of the iceberg,

NVidia have reproduced the observed problem and are investigating. https://developer.nvidia.com/nvbugs/cuda/edit/1554016 (accessible to registered developers only)

Still seeing errors and unable to validate/validate error in my jobs list.

Can someone with a clue on the new version and its coding, check up on it ?

I'm too getting lots of ps_modfit errors recently on AMD HD 7950.
I had to opt-out of the Modfit tasks.

DutchDK,

I am checking up on it. I coded all of the new changes. Doesn't seem to be any issues with the code though. Most likely it has to do with some library issues since we switched over to a new, more automated, build system.

Jake W.

FYI
All my Separation (Modified Fit...) work unites stop after 6-10 seconds with the message "Computation error." Only the 1.02 (opend_nvidia) get processed.
Mike