Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe

There is no c:\program files\boinc\projects folder. If I look in the \all users\application data\boinc\projects\milkyway.cs.rpi.edu.milkyway folder; there is no milkyway_0.7_windows_intelx86.exe file in there at all (not even anything close to it) I have been running the stock app since I started with milkyway and I did not overwrite any files when copying the custom app in.

Becouse you are using the opti app. If you rename the app_info.xml file, then BOINC downloads the stock app in that folder. (after stop and restart BOINC, of course)

Ok; but I was using the standard app yesterday; and didnt delete anything. Would boinc have deleted it by itself?

Boinc deletes the standard app whenever you add an optimized one to the folder.

---

~It only takes one bottle cap moving at 23,000 mph to ruin your whole day~

Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe

There is no c:\program files\boinc\projects folder. If I look in the \all users\application data\boinc\projects\milkyway.cs.rpi.edu.milkyway folder; there is no milkyway_0.7_windows_intelx86.exe file in there at all (not even anything close to it) I have been running the stock app since I started with milkyway and I did not overwrite any files when copying the custom app in.

Becouse you are using the opti app. If you rename the app_info.xml file, then BOINC downloads the stock app in that folder. (after stop and restart BOINC, of course)

Ok; but I was using the standard app yesterday; and didnt delete anything. Would boinc have deleted it by itself?

Yes. Is the standar actuation of BOINC.

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe

There is no c:\program files\boinc\projects folder. If I look in the \all users\application data\boinc\projects\milkyway.cs.rpi.edu.milkyway folder; there is no milkyway_0.7_windows_intelx86.exe file in there at all (not even anything close to it) I have been running the stock app since I started with milkyway and I did not overwrite any files when copying the custom app in.

Becouse you are using the opti app. If you rename the app_info.xml file, then BOINC downloads the stock app in that folder. (after stop and restart BOINC, of course)

Ok; but I was using the standard app yesterday; and didnt delete anything. Would boinc have deleted it by itself?

Yes. Is the standar actuation of BOINC.

Ahhh, well that would explain why I couldnt find it then, lol!! ok, so then I will remove the opti app, let boinc copy down the standard app, then copy the executable for it and ru the test to see if I get the same result. I will let you know what happens!

Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe

There is no c:\program files\boinc\projects folder. If I look in the \all users\application data\boinc\projects\milkyway.cs.rpi.edu.milkyway folder; there is no milkyway_0.7_windows_intelx86.exe file in there at all (not even anything close to it) I have been running the stock app since I started with milkyway and I did not overwrite any files when copying the custom app in.

Becouse you are using the opti app. If you rename the app_info.xml file, then BOINC downloads the stock app in that folder. (after stop and restart BOINC, of course)

Ok; but I was using the standard app yesterday; and didnt delete anything. Would boinc have deleted it by itself?

Yes. Is the standar actuation of BOINC.

Ahhh, well that would explain why I couldnt find it then, lol!! ok, so then I will remove the opti app, let boinc copy down the standard app, then copy the executable for it and ru the test to see if I get the same result. I will let you know what happens!

Don't remove the opti app only rename the app_info.xml. If you remove the opti, BOINC will be return your actual wus with error when it can't find an app with to crunch them. When the next wu is downloaded, then the stock app too.

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Your standard app can typically be found on a Windows PC in

C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.7_windows_intelx86.exe

There is no c:\program files\boinc\projects folder. If I look in the \all users\application data\boinc\projects\milkyway.cs.rpi.edu.milkyway folder; there is no milkyway_0.7_windows_intelx86.exe file in there at all (not even anything close to it) I have been running the stock app since I started with milkyway and I did not overwrite any files when copying the custom app in.

Becouse you are using the opti app. If you rename the app_info.xml file, then BOINC downloads the stock app in that folder. (after stop and restart BOINC, of course)

Ok; but I was using the standard app yesterday; and didnt delete anything. Would boinc have deleted it by itself?

Yes. Is the standar actuation of BOINC.

Ahhh, well that would explain why I couldnt find it then, lol!! ok, so then I will remove the opti app, let boinc copy down the standard app, then copy the executable for it and ru the test to see if I get the same result. I will let you know what happens!

Don't remove the opti app only rename the app_info.xml. If you remove the opti, BOINC will be return your actual wus with error when it can't find an app with to crunch them. When the next wu is downloaded, then the stock app too.

Sure--now you tell me!! Oh; well. The standard and optimized app gave different numbers, so it looks like it does not work properly. In any case; I am back using the standard app and will stay with it for now. Thank You to everyone who walked me thru. I do appreciate it!!

Thanks

Beau

I am having problems doing the comparison. I downloaded the test files without any problem, then duplicated the folder, one to run with the stock app, and one to run with the opt app. Oddly enough, I was able to run the opt app in stand alone mode just fine. It is with the stock app that I am having problems.

The opt app (astronomy_sse3_app) "out" file says:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371



But when I try to run the stock app (milkyway_0.7_windows_x86_64) in stand alone mode, I get no "out" file. The stderr file says:

Will run in standalone mode.
APP: error resolving search parameters file (for write): -108
filename: out
resolved output path: out

So I've hit a wall, in trying to compare the stock app to the opt app. FWIW, this is with XP64.

---

I am having problems doing the comparison. I downloaded the test files without any problem, then duplicated the folder, one to run with the stock app, and one to run with the opt app. Oddly enough, I was able to run the opt app in stand alone mode just fine. It is with the stock app that I am having problems.

The opt app (astronomy_sse3_app) "out" file says:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371



But when I try to run the stock app (milkyway_0.7_windows_x86_64) in stand alone mode, I get no "out" file. The stderr file says:

Will run in standalone mode.
APP: error resolving search parameters file (for write): -108
filename: out
resolved output path: out

So I've hit a wall, in trying to compare the stock app to the opt app. FWIW, this is with XP64.

You might need to remove the previous "out" file (generated by the other app) and the checkpoint file it generates.

---

I am having problems doing the comparison. I downloaded the test files without any problem, then duplicated the folder, one to run with the stock app, and one to run with the opt app. Oddly enough, I was able to run the opt app in stand alone mode just fine. It is with the stock app that I am having problems.

The opt app (astronomy_sse3_app) "out" file says:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371



But when I try to run the stock app (milkyway_0.7_windows_x86_64) in stand alone mode, I get no "out" file. The stderr file says:

Will run in standalone mode.
APP: error resolving search parameters file (for write): -108
filename: out
resolved output path: out

So I've hit a wall, in trying to compare the stock app to the opt app. FWIW, this is with XP64.

You might need to remove the previous "out" file (generated by the other app) and the checkpoint file it generates.

---

You might need to remove the previous "out" file (generated by the other app) and the checkpoint file it generates.

These were in completely separate, duplicated folders, from the top "milkyway" on down. In any case, I deleted the files from the opt folder, tried running the stock app in the stock folder, and got the same problem. I tried deleting the opt folder all together with no success.

---

You might need to remove the previous "out" file (generated by the other app) and the checkpoint file it generates.

These were in completely separate, duplicated folders, from the top "milkyway" on down. In any case, I deleted the files from the opt folder, tried running the stock app in the stock folder, and got the same problem. I tried deleting the opt folder all together with no success.

you might need to just put an empty "out" file in the directory for the stock app... i think i've seen this problem a couple times.

---

@ Travis

Why linux, OSX, and Win stock apps gave different results with the same wu?

Best regards.

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

@ Travis

Why linux, OSX, and Win stock apps gave different results with the same wu?

Best regards.

At what level of accuracy?

---

you might need to just put an empty "out" file in the directory for the stock app... i think i've seen this problem a couple times.

That fixed it. Here are the results. Each app's results is repeatable, but the stock result does not match the SSE3 opt app result. Am I correct in assuming we should be looking at the fitness value?

1st opt app run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371

2nd opt app run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371




1st stockrun:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.046272445362277

2nd stock run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.046272445362277

---

@ Travis

Why linux, OSX, and Win stock apps gave different results with the same wu?

Best regards.

At what level of accuracy?

So I guess this SSE3-Version saves the party for us.

Result of the Test-WU:
fitness: -3.046272445362275

you might need to just put an empty "out" file in the directory for the stock app... i think i've seen this problem a couple times.

That fixed it. Here are the results. Each app's results is repeatable, but the stock result does not match the SSE3 opt app result. Am I correct in assuming we should be looking at the fitness value?

1st opt app run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371

2nd opt app run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.106718478181371




1st stockrun:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.046272445362277

2nd stock run:

searchname
parameters [8]: 0.670000000000000 13.500000000000000 -1.734601060000000 33.352644669999997 27.423781280000000 1.244802812944947 1.914950983451476 2.500000000000000
metadata: this is the metadata
fitness: -3.046272445362277

Yeah the fitness is what we're looking at.

---

has any one checked the sse2 out too see if its working right

---

I just ran the SSE2 app on that same machine. The results matched the SSE3 results. So neither SSE2 or SSE3 match the stock app.

---

I just ran the SSE2 app on that same machine. The results matched the SSE3 results. So neither SSE2 or SSE3 match the stock app.

Are these the apps from the MW.rar download?

If not, would you please specify exactly which apps you tested?

Thanks

---

Calm Chaos Forum...Join Calm Chaos Now

So I guess this SSE3-Version saves the party for us.

Result of the Test-WU:
fitness: -3.046272445362275

Yes, I also got
fitness: -3.046272445362275

But that still does not match the stock app output of
fitness: -3.046272445362277

---