Welcome to MilkyWay@home

Posts by Microcruncher*

1) Message boards : Number crunching : Separation (Modified Fit) libc6 error (Message 59033)
Posted 22 Jun 2013 by Microcruncher*
Post:
Debian 7.0/7.1 (wheezy) uses the GLIBC 2.13 while the app requires version 2.14. This prevents the OpenCL app (and that from Poem@Home) from running on a Debian wheezy installation.
2) Message boards : News : testing new validator (Message 38844)
Posted 18 Apr 2010 by Microcruncher*
Post:
I uploaded 24 WUs a little bit ago, only to have 9 of them go Validation inconclusive.

For some obscure reason WUs are listed as "Completed, validation inconclusive" instead of "Completed, waiting for validation" even if there is no other deviating result that would make the validation inconclusive. Currently I see 8 of 10 of your WUs in the "validation inconclusive" state although there are no deviating results.

One WU is labeled as "Completed, waiting for validation" with one task "Completed, waiting for validation" and the other task "Completed, validation inconclusive".

The validator is still buggy in this regard.

"Completed, waiting for validation" = waiting on another task
"Completed, validation inconclusive" = wu wasn't quite on target, and another was sent out and waiting for it to come back.


The entry "Completed, validation inconclusive" should only be set if there are deviating results and not if the result is the only one sent back. If the other WU is unsent or no result is reported back the entry should be set to "Completed, waiting for validation".

Just my two cents...
3) Message boards : News : testing new validator (Message 38836)
Posted 18 Apr 2010 by Microcruncher*
Post:
I uploaded 24 WUs a little bit ago, only to have 9 of them go Validation inconclusive.

For some obscure reason WUs are listed as "Completed, validation inconclusive" instead of "Completed, waiting for validation" even if there is no other deviating result that would make the validation inconclusive. Currently I see 8 of 10 of your WUs in the "validation inconclusive" state although there are no deviating results.

One WU is labeled as "Completed, waiting for validation" with one task "Completed, waiting for validation" and the other task "Completed, validation inconclusive".

The validator is still buggy in this regard.
4) Message boards : Number crunching : **UPDATE: ATI 58x issue resolved! (Message 38437)
Posted 9 Apr 2010 by Microcruncher*
Post:
I could be wrong but I think the automatically downloaded Windows 32-bit 0.23 version will need the file to be called "brook32a_ati.dll" because the brook32a_ati.dll file is downloaded and copied and used as brook32.dll:
<file_ref>
<file_name>brook32a_ati.dll</file_name>
<open_name>brook32.dll</open_name>
<copy_file/>

I don't have the automatically downloaded Windows 32-bit v0.23 currently installed but going by the previous version the above code or something like it will be found in the "sched_request_milkyway.cs.rpi.edu_milkyway.xml" file in the BOINC folder.

I'm not certain why the _ati was added to the filename, but it was possibly to distinguish it from planned _amd versions of the brook file (for Cat 8.12 and Cat 9.1). The auto _amd versions ended up not being deployed at MilkyWay. Just a guess but the extra "a" in the auto downloaded brook file probably denotes the recently updated brook version that includes the Cypress fix.



You're exactly right. The boinc client should download brook32a_ati.dll from the server (which is at http://milkyway.cs.rpi.edu/milkyway/download/brook32a_ati.dll) and then rename it to brook32.dll

I think I might email the dev lists to see if there's some bug that would make this not overwrite a previous brook32.dll


Maybe this isn't a bug. If a MW WU was running during the download then the "old" DLL was in use and so it couldn't be replaced by the "new" one.
5) Message boards : News : testing new validator (Message 38051)
Posted 5 Apr 2010 by Microcruncher*
Post:
Here is another one:

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

errors: Too many success results

Bug already fixed.

Check the third post in this thread.


Thank you. I think I need more coffee...
6) Message boards : News : testing new validator (Message 38049)
Posted 5 Apr 2010 by Microcruncher*
Post:
Here is another one:

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

errors: Too many success results

One 0.19 result on a CPU and two 0.20b results on a HD 47xx/48xx and on a HD 58xx lead to this weird result.
7) Message boards : News : testing new validator (Message 38045)
Posted 5 Apr 2010 by Microcruncher*
Post:
Shouldn't it read:

Completed, waiting for validation

instead of

Completed, validation inconclusive

if one result is returned and no other results are reported?

[EDIT]: Fixed a typo...
8) Message boards : Number crunching : more credits :) (Message 37076)
Posted 9 Mar 2010 by Microcruncher*
Post:
I think it is in the responsibility of any self respecting BOINC project to make sure that WUs with expected runtimes of only one eighth of the "normal" WUs are paid appropriately. Just to hope that nobody sees it and all crunchers will crunch the same mix of WUs is naive when every half-baked programmer can come up with means to automatically abort the "longer" WUs in less than 5 minutes.




©2019 Astroinformatics Group