See the follow thread in the News area...

I guess it was too much to hope for a response in an on-topic thread... :D (Please excuse the snark...I'm not like that in real life.)

BTW.

It's O.K. to use further the opt. CPU app from available 'here'?

In app_info.xml named as V0.21 ?

Like this:

<app_name>milkyway</app_name>
<version_num>21</version_num>

The new stock/orig. MW@h CPU app have 0.04 ..?



From where we could DL the other new N-body CPU app?
And how this app should be named in the app_info.xml file?



I understood it correct, that MW@h have currently 2 CPU apps?

Hi Travis (or anybody who knows),

after the fix was announced I downloaded a few new WUs and got to work. The first
de_14-2s_5_126674_1287400167_0 ran for 21+ hours and showed 16 still to go so I aborted it as it looked like a bad one the next de_14_2s_5_126673_1287400167_0 has been running for 17 hours and shows 27 hours to go.

Are these new WUs or still some from the bad batch. If they are the bad ones then no problem I will abort and download new ones. If they are not then I have a different problem and I don't know what to do with it. Both of these WUs showed a "to completion time" of about 18 hours so running for about c44 hours is way beyond what was expected. The Application running for both WUs is MW&H 0.04.

I am afraid that I am stumped HELP!!

Once the new validator gets up and going validation will work as follows:

Any result that could potentially improve one of our searches will be validated (with a quorum of 2 or 3).

Previously, any result that wouldn't improve our searches we ignored. I'll be validating 50 - 100% of these for the next couple weeks so everyones error rate gets update correctly.

After everyone's error rate has leveled out, I'll drop the validation done on these workunits to whatever % the error rate of host returning the result is (minimum 10%).

So we'll still be validating every potentially good result, but we'll be using BOINC's adaptive validation for everything else.

How is that suppose to work in regard to this -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1640 ???

Besides that, what's the problem with those results ?
When will it be fixed ?

By the way, does this fix the progress bar issues for particularly large WUs as well? IIRC Cluster Physik said it was just a case of switching from a 32-bit to a 64-bit variable. Presumably all apps need the fix (though a large part of the userbase will already be using one of the fixed optimized applications).

Confirmed Travis - I just used up my last MW wu and even though the server board shows all green and wu available - I can't get any.

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

Yes, that seems to be the case and i think that it is due to the scheduler version used.

if you take a look at the sched_reply*.xml in you boinc directory you'll see that MW uses <scheduler_version>610</scheduler_version>

Up to date projects like AQUA or Collatz use <scheduler_version>611</scheduler_version>

May be OT - I just noticed a couple of WUs with computation errors. Tried a manual update to clear the air.
'Message from server: Server error: recompile needed'.

May be OT - I just noticed a couple of WUs with computation errors. Tried a manual update to clear the air.
'Message from server: Server error: recompile needed'.

I think the project scheduler thinks the ATI app for NVIDIA. Explains why I can get work (I have a gtx) and others can't. It is also corroborated by the fact that boinc requires an NVIDIA card to do the crunching (on the ATI app).

Yes, that seems to be the case and i think that it is due to the scheduler version used.

if you take a look at the sched_reply*.xml in you boinc directory you'll see that MW uses <scheduler_version>610</scheduler_version>

Up to date projects like AQUA or Collatz use <scheduler_version>611</scheduler_version>

Hi Trav, no I've been running MW with ATI 4870's in this box but I have another that runs GPUGrid with nvidia 9800gt's, The Cuda app wasn't available at the time I started running MW and I got a really great deal on these ATI's I have now.

Also, please keep in mind folks, it's not the project I have a problem with, it's the way in which the Boinc manager handles the MW WU's while trying to run any other project. I still have MW set to run WU"s anytime it'll go fetch the work. The Boinc manager just won't go get the work if there's any other project running and that includes CPU only WU's from other projects.

I will try the latest release of the ATI apps to see if that helps.

Yo-

I state that I have problems updating your profile, but I must make a note on the home page of the site with regard to the news, it is true that we are only a few days in the new year, but we are in 2010 and 2009. :-)

I have had no work for about 1 day now!