Welcome to MilkyWay@home

Unexpected App of Unknown Origin


Advanced search

Message boards : Number crunching : Unexpected App of Unknown Origin
Message board moderation

To post messages, you must log in.

AuthorMessage
steveplanetary
Avatar

Send message
Joined: 19 May 09
Posts: 16
Credit: 20,273
RAC: 0
10 thousand credit badge12 year member badge
Message 34470 - Posted: 11 Dec 2009, 20:58:44 UTC

Because of a couple of issues it was necessary for me to detach from and reattach to MW. I had been using the SSE opti app although, after some time, the name changed from astronomy 0.20 to milkyway 0.20. So after I reattached I again downloaded the SSE version of the opti app. What follows is the app_info.xml file:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.20_SSE.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>19</version_num>
<file_ref>
<file_name>astronomy_0.20_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<file_ref>
<file_name>astronomy_0.20_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

When I downloaded a WU the app was named milkyway 0.19. The first time this happened the app had downloaded with the WU, since milkyway 0.19 had appeared in the ...projects\milkyway.cs.rpi.edu_milkyway subdirectory. So I deleted milkyway 0.19 from the subdirectory, aborted the WU, and downloaded another WU. This time the app named in BOINC Manager again was milkyway 0.19 (the complete name was milkyway_0.19_windows_intelx86.exe), but the app didn't show up in ...projects\milkyway.cs.rpi.edu_milkyway. Interestingly, when I downloaded the most recent WU, the file astronomy_0.20_SSE.exe asked permission from my AV software to connect to the internet. Given the contents of app_info.xml it looks to me that astronomy_0.20_SSE.exe will play nice with either v0.19 or v0.20 WUs, and it looks to me like the stock app is crunching the WU, although I can't explain why the app is not listed in ...projects\milkyway.cs.rpi.edu_milkyway. Can anybody explain what's goin on?

Steve
ID: 34470 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileConan
Avatar

Send message
Joined: 2 Jan 08
Posts: 108
Credit: 66,472,998
RAC: 1,704
50 million credit badge13 year member badge
Message 34474 - Posted: 12 Dec 2009, 2:28:30 UTC - in response to Message 34470.  

Because of a couple of issues it was necessary for me to detach from and reattach to MW. I had been using the SSE opti app although, after some time, the name changed from astronomy 0.20 to milkyway 0.20. So after I reattached I again downloaded the SSE version of the opti app. What follows is the app_info.xml file:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.20_SSE.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>19</version_num>
<file_ref>
<file_name>astronomy_0.20_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<file_ref>
<file_name>astronomy_0.20_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

When I downloaded a WU the app was named milkyway 0.19. The first time this happened the app had downloaded with the WU, since milkyway 0.19 had appeared in the ...projects\milkyway.cs.rpi.edu_milkyway subdirectory. So I deleted milkyway 0.19 from the subdirectory, aborted the WU, and downloaded another WU. This time the app named in BOINC Manager again was milkyway 0.19 (the complete name was milkyway_0.19_windows_intelx86.exe), but the app didn't show up in ...projects\milkyway.cs.rpi.edu_milkyway. Interestingly, when I downloaded the most recent WU, the file astronomy_0.20_SSE.exe asked permission from my AV software to connect to the internet. Given the contents of app_info.xml it looks to me that astronomy_0.20_SSE.exe will play nice with either v0.19 or v0.20 WUs, and it looks to me like the stock app is crunching the WU, although I can't explain why the app is not listed in ...projects\milkyway.cs.rpi.edu_milkyway. Can anybody explain what's goin on?

Steve


Edit your app_info.xml file to put app 20 first and app 19 second in the list.

It has been found that the first one is loaded rather than the second even if the second is the one you want and is available.
ID: 34474 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
steveplanetary
Avatar

Send message
Joined: 19 May 09
Posts: 16
Credit: 20,273
RAC: 0
10 thousand credit badge12 year member badge
Message 34495 - Posted: 13 Dec 2009, 7:30:10 UTC - in response to Message 34474.  

Thanks for the info, Conan. I'll try that, and see what happens.

Steve
ID: 34495 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
steveplanetary
Avatar

Send message
Joined: 19 May 09
Posts: 16
Credit: 20,273
RAC: 0
10 thousand credit badge12 year member badge
Message 34496 - Posted: 13 Dec 2009, 7:43:11 UTC - in response to Message 34474.  

I shutdown BOINC and edited my app_info.xml file. When I restarted BOINC the client deleted the WU I had been working on, but when it downloaded a new WU BOINC Manager showed the app to be milkyway 0.20. Strange bug, that. One would think the client would identify the fastest app and go with that.
ID: 34496 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileGary Roberts

Send message
Joined: 1 Mar 09
Posts: 56
Credit: 1,984,937,499
RAC: 0
1 billion credit badge12 year member badge
Message 34505 - Posted: 13 Dec 2009, 13:35:31 UTC - in response to Message 34496.  

I shutdown BOINC and edited my app_info.xml file. When I restarted BOINC the client deleted the WU I had been working on, but when it downloaded a new WU BOINC Manager showed the app to be milkyway 0.20. Strange bug, that. One would think the client would identify the fastest app and go with that.

In reading not just the above but also some of your earlier statements, there are quite a few things you are getting confused about.

Firstly in the above quote, you say that showing the app in BOINC manager as "milkyway 0.20" is a bug. In fact there is no bug and it is perfectly correct because that is exactly what your app_info.xml says the description in BOINC manager should be. I have explained this in response to another question so please feel free to read the explanation of why this is so here. Warning: You may need to start at the beginning of the thread to get the full picture.

Secondly, you say that the client should identify the fastest app and go with that. How is it supposed to do that? The whole point of AP is to make sure that both the client and the server have ZERO choice in the matter. The precise app to be used is specified in app_info.xml. It is NEVER downloaded by the client. It MUST exist in the project folder before the client starts up. You will always get an error if the app specified in app_info.xml doesn't exist.

You said in an earlier message that an app was downloaded with a task. When that happened, you could not have had a valid app_info.xml in place and what was downloaded would have been the normal stock app and not an optimised one. You were correct to get rid of that app and start again.

The app_info.xml file you published implies the following facts/conditions

  • You must supply an app called 'astronomy_0.20_SSE.exe'.
  • The app will be called 'milkyway 0.20' when displayed in BOINC manager.
  • You must place the app called 'astronomy_0.20_SSE.exe' in the MW project folder.
  • This program must already exist before the client is started.
  • This program will never be downloaded by a client request.
  • If this program doesn't exist, it will be a fatal error.
  • This program can be used to crunch any existing tasks already 'branded' as 0.19 or 0.20
  • Any new tasks downloaded will be branded 0.20


If you need further details about this, please read the message I linked in the 2nd paragraph above.

Also, you were given incorrect information that version 20 has to be listed before version 19. The natural way is to list 19 first but it will work either way. BOINC always assumes that the bigger number numerically is the latest version.


Cheers,
Gary.
ID: 34505 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileConan
Avatar

Send message
Joined: 2 Jan 08
Posts: 108
Credit: 66,472,998
RAC: 1,704
50 million credit badge13 year member badge
Message 34524 - Posted: 14 Dec 2009, 11:41:51 UTC - in response to Message 34505.  

I shutdown BOINC and edited my app_info.xml file. When I restarted BOINC the client deleted the WU I had been working on, but when it downloaded a new WU BOINC Manager showed the app to be milkyway 0.20. Strange bug, that. One would think the client would identify the fastest app and go with that.

In reading not just the above but also some of your earlier statements, there are quite a few things you are getting confused about.

Firstly in the above quote, you say that showing the app in BOINC manager as "milkyway 0.20" is a bug. In fact there is no bug and it is perfectly correct because that is exactly what your app_info.xml says the description in BOINC manager should be. I have explained this in response to another question so please feel free to read the explanation of why this is so here. Warning: You may need to start at the beginning of the thread to get the full picture.

Secondly, you say that the client should identify the fastest app and go with that. How is it supposed to do that? The whole point of AP is to make sure that both the client and the server have ZERO choice in the matter. The precise app to be used is specified in app_info.xml. It is NEVER downloaded by the client. It MUST exist in the project folder before the client starts up. You will always get an error if the app specified in app_info.xml doesn't exist.

You said in an earlier message that an app was downloaded with a task. When that happened, you could not have had a valid app_info.xml in place and what was downloaded would have been the normal stock app and not an optimised one. You were correct to get rid of that app and start again.

The app_info.xml file you published implies the following facts/conditions

  • You must supply an app called 'astronomy_0.20_SSE.exe'.
  • The app will be called 'milkyway 0.20' when displayed in BOINC manager.
  • You must place the app called 'astronomy_0.20_SSE.exe' in the MW project folder.
  • This program must already exist before the client is started.
  • This program will never be downloaded by a client request.
  • If this program doesn't exist, it will be a fatal error.
  • This program can be used to crunch any existing tasks already 'branded' as 0.19 or 0.20
  • Any new tasks downloaded will be branded 0.20


If you need further details about this, please read the message I linked in the 2nd paragraph above.

Also, you were given incorrect information that version 20 has to be listed before version 19. The natural way is to list 19 first but it will work either way. BOINC always assumes that the bigger number numerically is the latest version.



G'Day Gary,
Yes I know that it should make no difference and on other projects where I have used an app_info.xml file I have placed the various apps listed from oldest to youngest (some of the Einstein app_info files from a while back were very long so as to include all the various apps running at the time with the Beta releases).
However I have not been the only one to have to had modified my app_info file both here and I think Collatz was the other place, in order to get the latest app to download.
As for incorrect information, well if the syntax is wrong that is unfortunate, BOINC is an amazing thing that is often hard to fathom, but as you have seen it worked and it works for me also.

I currently get round the problem by running out all the old work and then just adding the new app_info.xml file with only the new app listed in it.

Conan.

ID: 34524 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Unexpected App of Unknown Origin

©2021 Astroinformatics Group