Why don't I receive S@H V7 WUs when entry for that put in app_info.xml file?

Message boards : SETI@home Enhanced : Why don't I receive S@H V7 WUs when entry for that put in app_info.xml file?
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile CElliott
Volunteer tester

Send message
Joined: 16 Aug 05
Posts: 79
Credit: 71,936,490
RAC: 0
United States
Message 45674 - Posted: 1 May 2013, 14:25:52 UTC

I put the following record in app_info.xml to receive S@H V7 WUs, but none were received:
<app>
<name>setiathome_v7</name>
<user_friendly_name>SETI@home v7 BETA</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>
<file_info>
<name>setiathome_7.00_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3_upx.dll</file_name>
<open_name>libfftw3f-3-3_upx.dll</open_name>
</file_ref>
</app_version>

The only way I could process S@H WUs with the version 700 executable was by changing all the 697 and 698 references in app_info.xml to point to the Version 700 executable, viz:

<app_version>
<app_name>setiathome_v7</app_name>
<version_num>698</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
</app_version>

What do you want us to do to be able to exercise the setiathome_7.00_windows_intelx86.exe program? What can't we use it just by putting a new entry for it in the app_info.xml file?
ID: 45674 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1451
Credit: 3,272,268
RAC: 0
United Kingdom
Message 45676 - Posted: 1 May 2013, 15:44:54 UTC - in response to Message 45674.  

CElliott,

If you're going to insist on using app_info.xml - and you've been told, many times, that it's undesirable when applications are being prepared for release and may be subject to rapid change without notice - please at least teach yourself the practicalities of how to prepare and update an app_info.xml file efficiently. Read The format of app_info.xml (again), if you haven't recently.

I can see at least three problems with what you've posted - two cosmetic, and one fatal. There may be more, but I stopped reading at that point.

1) <user_friendly_name>: not needed, delete for simplicity (KISS principle)
2) <non_cpu_intensive>: not needed, delete (ditto)
3) You have a <file_info> for libfftw3f-3-1-1a_upx.dll, but a <file_ref> for libfftw3f-3-3_upx.dll. They have to match.

Download, and learn to use, http://www.dependencywalker.com/, so you can work out for yourself which DLL setiathome_7.00_windows_intelx86.exe is compiled against.
ID: 45676 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 0
United Kingdom
Message 45677 - Posted: 1 May 2013, 17:44:10 UTC - in response to Message 45676.  
Last modified: 1 May 2013, 17:46:11 UTC

3) You have a <file_info> for libfftw3f-3-1-1a_upx.dll, but a <file_ref> for libfftw3f-3-3_upx.dll. They have to match.

Make sure you use the libfftw3f-3-3_upx.dll too, that is what the 7.00 app comes with, it produces runtimes of around 10% faster than with the older .dll


Claggy
ID: 45677 · Report as offensive
Richard Haselgrove
Volunteer tester

Send message
Joined: 3 Jan 07
Posts: 1451
Credit: 3,272,268
RAC: 0
United Kingdom
Message 45678 - Posted: 1 May 2013, 17:56:06 UTC - in response to Message 45677.  

"If you give a man a fish you feed him for a day. If you teach a man to fish you feed him for a lifetime."

Lao Tzu
ID: 45678 · Report as offensive
Profile Mr. Kevvy
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 21 Apr 13
Posts: 23
Credit: 2,253,909
RAC: 0
Canada
Message 45681 - Posted: 1 May 2013, 18:40:34 UTC - in response to Message 45678.  

"Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life."

Terry Pratchett
ID: 45681 · Report as offensive
Profile CElliott
Volunteer tester

Send message
Joined: 16 Aug 05
Posts: 79
Credit: 71,936,490
RAC: 0
United States
Message 45782 - Posted: 11 May 2013, 0:56:03 UTC - in response to Message 45676.  

CElliott,

If you're going to insist on using app_info.xml - and you've been told, many times, that it's undesirable when applications are being prepared for release and may be subject to rapid change without notice - please at least teach yourself the practicalities of how to prepare and update an app_info.xml file efficiently. Read The format of app_info.xml (again), if you haven't recently.


Thank you for your prompt offer of assistance.

No one has ever told me not to use app_info.xml. When I rejoined this project last year, I originally was not using an app_info, but despite having several computers attached to the project my ranking was in the middle of the pack. So I looked at what apps the leaders were using, and they were all optimized. So, I joined them, using the anonymous platform. As I recall, I sent Eric Korpela an email telling him what I was doing as said something like, if you don't want that, just tell me. I don't recall receiving a reply.

I have 4 computers attached to the Beta project, two using the anonymous platform and 2 not using it. If that bothers you, send a message to Eric suggesting that he ask me to stop using the anonymous platform.

Again, thank you for your help and for all your contributions to S@H.

Charles Elliott
ID: 45782 · Report as offensive

Message boards : SETI@home Enhanced : Why don't I receive S@H V7 WUs when entry for that put in app_info.xml file?


 
©2021 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.