I found the problem. What a royal pain in the butt :P

Line 84, evaluation_state.c

fprintf(file, "background integral: %.20lf\n", ia->background_integral);

needs to be:

fprintf(file, "background_integral: %.20lf\n", ia->background_integral);

facepalm. damned underscores.

I think that should be the last of it. I'll update to v0.16 today.


*edit*

v0.16 is released with the above change and looks like it's running smoothly.

---

I found the problem. What a royal pain in the butt :P

Line 84, evaluation_state.c

fprintf(file, "background integral: %.20lf\n", ia->background_integral);

needs to be:

fprintf(file, "background_integral: %.20lf\n", ia->background_integral);

facepalm. damned underscores.

I think that should be the last of it. I'll update to v0.16 today.

You should read my posts in the first checkpointing thread a bit better! ;)

I found the problem. What a royal pain in the butt :P

Line 84, evaluation_state.c

fprintf(file, "background integral: %.20lf\n", ia->background_integral);

needs to be:

fprintf(file, "background_integral: %.20lf\n", ia->background_integral);

facepalm. damned underscores.

I think that should be the last of it. I'll update to v0.16 today.

You should read my posts in the first checkpointing thread a bit better! ;)

oh geez how did i miss that :( probably distracted by people complaining about credits :P

---

Damn...

---

mic.

you've probably noticed by now, but all the v0.16's are erring at download:

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>milkyway_0.16_windows_intelx86.exe</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

</message>
]]>

Likewise on XP64, running on a Core 2 Duo E6750, I am getting a string of errors along the lines of:

26/01/2009 03:15:32|Milkyway@home|Finished download of milkyway_0.16_windows_x86_64.exe
26/01/2009 03:15:32|Milkyway@home|[error] Signature verification failed for milkyway_0.16_windows_x86_64.exe
26/01/2009 03:15:32|Milkyway@home|[error] Checksum or signature error for milkyway_0.16_windows_x86_64.exe
26/01/2009 03:17:13|Milkyway@home|Sending scheduler request: To fetch work. Requesting 1401608 seconds of work, reporting 4 completed tasks
26/01/2009 03:17:38|Milkyway@home|Scheduler request completed: got 4 new tasks
26/01/2009 03:17:40|Milkyway@home|Started download of milkyway_0.16_windows_x86_64.exe
26/01/2009 03:17:40|Milkyway@home|Started download of nm_s79_e28_search_parameters_65527_1232939798
26/01/2009 03:17:48|Milkyway@home|Sending scheduler request: To fetch work. Requesting 1349849 seconds of work, reporting 0 completed tasks
26/01/2009 03:17:52|Milkyway@home|Finished download of nm_s79_e28_search_parameters_65527_1232939798
26/01/2009 03:17:52|Milkyway@home|Started download of nm_s79_e28_search_parameters_65511_1232939797
26/01/2009 03:17:54|Milkyway@home|Finished download of nm_s79_e28_search_parameters_65511_1232939797
26/01/2009 03:17:54|Milkyway@home|Started download of nm_s79_e28_search_parameters_65512_1232939797
26/01/2009 03:17:55|Milkyway@home|Finished download of nm_s79_e28_search_parameters_65512_1232939797
26/01/2009 03:17:55|Milkyway@home|Started download of nm_s79_e28_search_parameters_65513_1232939797
26/01/2009 03:17:56|Milkyway@home|Finished download of nm_s79_e28_search_parameters_65513_1232939797
26/01/2009 03:18:03|Milkyway@home|Finished download of milkyway_0.16_windows_x86_64.exe
26/01/2009 03:18:03|Milkyway@home|[error] Signature verification failed for milkyway_0.16_windows_x86_64.exe
26/01/2009 03:18:03|Milkyway@home|[error] Checksum or signature error for milkyway_0.16_windows_x86_64.exe

etc etc

Needless to say it will not keep the wu for an app that has failed to download...

you've probably noticed by now, but all the v0.16's are erring at download:

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>milkyway_0.16_windows_intelx86.exe</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

</message>
]]>

Common cause.. VERY SLOW NETWORK.. I am also having trouble loading the web pages. and upload issues.

1/25/2009 8:21:21 PM|Milkyway@home|Temporarily failed upload of nm_s82_u28_43279_1232933264_0_0: system connect


Maybe one of the "big dogs" joined up and is sucking down all the bandwidth...

---

.

you've probably noticed by now, but all the v0.16's are erring at download:

6.2.19

app_version download error: couldn't get input files:

milkyway_0.16_windows_intelx86.exe
-120
signature verification failed



]]>

It looks like Dave might have had an issue with the permissions on the files he updated. I think this should be fixed now. Let me know if it's still happening. I'm assuming this is just for windows because all linux/osx versions seem to be crunching fine.

---

i just had 3 more fail on download

Well, the push to v0.17 (not bad - is that 10 updates in a week? Do we have a world record yet, or is there a way to go yet? LOL) seems to have fixed it, as mentioned in another thread :)

i just had 3 more fail on download

It looks like there was a problem with the signature files Dave used. I resigned it myself and released a v0.17 so hopefully that will work.

---

Looks like my very last 0.14 WU is being crunched, and I have started crunching my first 0.17. The WUs that are ready to start are all 0.17, so I assume there was no D/L problems.

On my slow rigs I have a few 0.14s to work through before reaching the 0.17s.

Seems to be OK at this early stage.

(Oh! Windose and the stock client)

NOTE: Before the successful D/L of the 0.17 WUs, I see one rig had 38 V0.16 WUs client error on download. Looks like that was quite a problem for over an hour about 02.25an and 03.45am.

This was a message repeated on two of my other rigs, but the slowest did not have problems.

I bet the servers were being hammered then with repeated requests for more work. How did they cope, Travis?

the download problem seems to be gone. i only have one machine that's actually ran v0.17 yet, but they ran fine. thanks, travis.

i looked back through my tasks and found one v0.17 that did not download, but the next person got it fine:

Task ID 64578598
Name nm_s79_l28_42108_1232959219_0
Workunit 64548247
Created 26 Jan 2009 8:40:20 UTC
Sent 26 Jan 2009 8:42:22 UTC
Received 26 Jan 2009 10:29:58 UTC
Server state Over
Outcome Client error
Client state Downloading
Exit status -186 (0xffffffffffffff46)
Computer ID 41037
Report deadline 29 Jan 2009 8:42:22 UTC
CPU time 0
stderr out <core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>nm_s79_l28_search_parameters_42108_1232959219</file_name>
<error_code>-200</error_code>
</file_xfer_error>

</message>
]]>

Validate state Invalid
Claimed credit 0
Granted credit 0
application version 0.17

I bet the servers were being hammered then with repeated requests for more work. How did they cope, Travis?

No crashes or fires, so I think they handled it ok :D

---

Hi I am fairly new to MilkyWay, to the devs, if possible could you add your Visual Studio solution/project files to the source release? I have VS 2005, but I am not sure how to get the BOINC source and milkyway to talk in VS.

Alternatively, if you could just put the entire source tree (plus the required boinc source code) in SVN/CVS/Git it would be much easier. Just checkout and click the solution.

I say this because I don't mind test compiling milkyway on windows, but I need to figure out how to compile it on Windows first ><, I do most of my development work on Linux (MPI/cluster applications).

Anyway, good luck on get windows optimized!

Hi I am fairly new to MilkyWay, to the devs, if possible could you add your Visual Studio solution/project files to the source release? I have VS 2005, but I am not sure how to get the BOINC source and milkyway to talk in VS.

I don't have any solution/project files since that's all done by Dave P. I'll see if I can get him to make a post about what he does.

Alternatively, if you could just put the entire source tree (plus the required boinc source code) in SVN/CVS/Git it would be much easier. Just checkout and click the solution.

I can talk to our labstaff about having a remotely accessible CVS or SVN repository... although they've been pretty reluctant to set something like that up in the past. But I'll see what we can do here.

I say this because I don't mind test compiling milkyway on windows, but I need to figure out how to compile it on Windows first ><, I do most of my development work on Linux (MPI/cluster applications).

Anyway, good luck on get windows optimized!

Yeah, I hear you, thats mainly what i do too :D Windows can be a pain... Unix/Linux/OSX is so much easier once you're used to the command line tools :)

---

I use VS2008 (bad decision, should've stayed with 2005). I can give you the sln files if you wish but i doubt you'll be able to use them in 2005.

---

Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute

I use VS2008 (bad decision, should've stayed with 2005). I can give you the sln files if you wish but i doubt you'll be able to use them in 2005.

I use VS2008 and have the evaluation version of the Intel Compiler (looking for somewhere is Aus that sells the student version so I can get it much cheaper). So if you wish, I can use the sln file(s). Put them in the code release or mail them to me (you have my email in your database :)

Thanks.

---

Never surrender and never give up. In the darkest hour there is always hope.