As I previously indicated just before the servers were upgraded, I am intending to publish app_info.xml files for the express purpose of allowing interested users to support both the new series of S5R4 tasks as well as any resend S5R3 tasks that might happen to come along. I've now had a chance to setup and partially test Windows and Linux app_info.xml files that seem to work as intended. I'm not going to release them just yet as I'm not 100% sure that I'm actually using the correct S5R4 apps. I'm awaiting confirmation on that.
Shortly, when I'm satisfied that everything is in order, I'll post the app_info.xml files here, one for Windows and one for Linux. I don't intend to do files for other platforms since I have no way of testing. People interested in other platforms should be able to use what I post here as an example from which it should be pretty straight forward to edit their own versions.
If you would like to make your host(s) "dual app ready" there are several things you will need to check on besides just getting an app_info.xml file. At the moment I can report that I have both a Windows host and a Linux host, both of which have successfully downloaded new S5R4 work under the control of edited app_info.xml files and using the apps listed below. The Linux host has also downloaded S5R3 resend work. The Linux host is crunching the resend work and the Windows host is crunching the S5R4 work as it had completely drained its supply of S5R3. All seems to be working as expected.
For Windows Users
The assumption is made that you have been crunching the old S5R3 data with either the 4.36 or 4.46 versions of the S5R3 app and that any S5R3 tasks currently in your cache are therefore "branded" as 4.36 or 4.46. This should cover most people who have been using beta test apps. If your cache has already run dry, you wont have to check the branding - it wont be an issue. If you have correctly branded S5R3 tasks left, they will be handled by the new app_info.xml file when I release it.
While you are waiting for the app_info.xml file you should check that you have the following files available.
If any of these aren't there already, you will need to source them from the beta test page.
For the new S5R4 app, I think (but am not 100% sure yet) that you need the following files.
These S5R4 files are currently available in the EAH download directory.
Please note that the anonymous platform (AP) mechanism which uses app_info.xml requires you, the user, to personally supply all files that are listed within the app_info.xml file and make sure they are correctly installed in your EAH projects directory. Under the AP mechanism there is NO auto downloading of executables. If any of this is not immediately obvious and understandable to you, you should probably just let BOINC work normally and not attempt to use the AP mechanism.
For Linux Users
The assumption is made that you have been crunching the old S5R3 data with either the 4.35, 4.38 or 4.49 versions of the S5R3 app and that any S5R3 tasks currently in your cache are therefore "branded" as 4.35, 4.38 or 4.49. This should cover most people who have been using beta test apps.
While you are waiting for the app_info.xml file you should check that you have the following files available.
If any of these aren't there already, you will need to source them from the beta test page.
For the new S5R4 app, I think (but am not 100% sure yet) that you need the following files.
These S5R4 files are currently available in the EAH download directory.
If you have all the executables listed for your OS of choice, the only extra bit you will need is the appropriate app_info.xml file which I intend to publish here - shortly I hope.
Cheers,
Gary.
Copyright © 2024 Einstein@Home. All rights reserved.
App_Info files for S5R3/S5R4 Dual Capability
)
I have just received official confirmation that the S5R4 apps I'm using are the correct ones. Also, I've seen messages posted by users which quote the same apps I'm using.
So here is the app_info.xml file for Windows. If you are currently using an app_info.xml file and are getting nasty messages about the scheduler wanting to send you S5R4 work but that you don't have the correct apps, then setting up the new app_info.xml and providing all the apps I nominated in my previous message will allow you to get S5R4 work as well as any S5R3 work that might be on offer.
I have tested this file on a couple of machines and it works for me. I take no responsibility for what happens to you as a result of using this file. If you don't have a clue what this is all about then you really shouldn't be using it until you do a bit of research on what has been written already about this.
To use this file you need to cut and paste what appears below into a text file which you will call app_info.xml. You will place this file together with all the Windows executables I listed in my previous message, into your Einstein project directory, overwriting any previous app_info.xml that might be there. You will then stop and restart BOINC.
EDIT (8 Aug 2008):
archae86 has provided a very useful tip for anyone trying to cut and paste the app_info.xml file. The text I inserted below does have proper formatting but you can't see it in the displayed version. However, if you start to reply to this message, you will get a reply window where you can actually see the formatting and can also see the leading and trailing [ code ] and [ /code ] tags which show you exactly what you need to cut and paste. In other words, leave out the code tags but cut and paste everything else into a text editor. Then you can simply abandon the reply once you have what you need with the proper formatting.
archae86 had actually provided this tip quite some time ago (probably around the start of S5R3) but I had forgotten about it. Thanks to archae86 for providing it again.
EDIT2 (11 Aug 2008):
In the opening message of this thread, I stated the assumptions about versions of the science apps that the app_info.xml files were designed to handle. I deliberately left out the stock Windows 4.26 version because I assumed that people interested in manual intervention (which is what this all is) would have already been running one of the beta/power user apps and not the stock app. On reflection, I probably should have included the 4.26 stock Windows app just to protect people who decided to try this out without really understanding the dangers. So, better late than never, I added that capability now.
I call the statements I've added, a "clause". It's a term I use to describe a group of statements that apply to a particular version of the science app. You only need to get this modified version of app_info.xml (or add this clause) if you really need to support resend tasks that are already in your cache, ie that have been downloaded while the stock app (4.26) was running.
If you currently have NO resends or if any you have are "branded" as 4.36 or
4.46 already, you do NOT need to do anything concerning the adding of this clause, mentioned above.
einstein_S5R3
einstein_S5R3_4.46_windows_intelx86.exe
einstein_S5R3_4.46_windows_intelx86_0.exe
einstein_S5R3_4.46_windows_intelx86_1.exe
einstein_S5R3_4.26_windows_intelx86.pdb
einstein_S5R3_4.36_windows_intelx86.pdb
einstein_S5R3_4.46_graphics_windows_intelx86.exe
einstein_S5R3
426
6.1.0
einstein_S5R3_4.46_windows_intelx86.exe
einstein_S5R3_4.46_windows_intelx86_0.exe
einstein_S5R3_4.46_windows_intelx86_1.exe
einstein_S5R3_4.26_windows_intelx86.pdb
einstein_S5R3_4.36_windows_intelx86.pdb
einstein_S5R3_4.46_graphics_windows_intelx86.exe
graphics_app
einstein_S5R3
436
6.1.0
einstein_S5R3_4.46_windows_intelx86.exe
einstein_S5R3_4.46_windows_intelx86_0.exe
einstein_S5R3_4.46_windows_intelx86_1.exe
einstein_S5R3_4.26_windows_intelx86.pdb
einstein_S5R3_4.36_windows_intelx86.pdb
einstein_S5R3_4.46_graphics_windows_intelx86.exe
graphics_app
einstein_S5R3
446
6.1.0
einstein_S5R3_4.46_windows_intelx86.exe
einstein_S5R3_4.46_windows_intelx86_0.exe
einstein_S5R3_4.46_windows_intelx86_1.exe
einstein_S5R3_4.26_windows_intelx86.pdb
einstein_S5R3_4.36_windows_intelx86.pdb
einstein_S5R3_4.46_graphics_windows_intelx86.exe
graphics_app
einstein_S5R4
einstein_S5R4_6.04_windows_intelx86.exe
einstein_S5R4_6.04_windows_intelx86_0.exe
einstein_S5R4_6.04_windows_intelx86_1.exe
einstein_S5R4_5.09_0_windows_intelx86.pdb
einstein_S5R4_5.09_1_windows_intelx86.pdb
einstein_S5R4_6.04_graphics_windows_intelx86.exe
einstein_S5R4
604
6.1.0
einstein_S5R4_6.04_windows_intelx86.exe
einstein_S5R4_6.04_windows_intelx86_0.exe
einstein_S5R4_6.04_windows_intelx86_1.exe
einstein_S5R4_5.09_0_windows_intelx86.pdb
einstein_S5R4_5.09_1_windows_intelx86.pdb
einstein_S5R4_6.04_graphics_windows_intelx86.exe
graphics_app
Cheers,
Gary.
Here is the appropriate
)
Here is the appropriate app_info.xml for Linux. Once again, cut and paste this into a file with a text editor and then put the file with all the Linux apps I listed in my first message into the EAH project directory of your Linux machine. When you stop and restart BOINC you will be dual app capable.
einstein_S5R3
einstein_S5R3_4.49_i686-pc-linux-gnu
einstein_S5R3_4.49_i686-pc-linux-gnu_0
einstein_S5R3_4.49_i686-pc-linux-gnu_1
einstein_S5R3_4.49_graphics_i686-pc-linux-gnu
einstein_S5R3
435
6.1.0
einstein_S5R3_4.49_i686-pc-linux-gnu
einstein_S5R3_4.49_i686-pc-linux-gnu_0
einstein_S5R3_4.49_i686-pc-linux-gnu_1
einstein_S5R3_4.49_graphics_i686-pc-linux-gnu
graphics_app
einstein_S5R3
438
6.1.0
einstein_S5R3_4.49_i686-pc-linux-gnu
einstein_S5R3_4.49_i686-pc-linux-gnu_0
einstein_S5R3_4.49_i686-pc-linux-gnu_1
einstein_S5R3_4.49_graphics_i686-pc-linux-gnu
graphics_app
einstein_S5R3
449
6.1.0
einstein_S5R3_4.49_i686-pc-linux-gnu
einstein_S5R3_4.49_i686-pc-linux-gnu_0
einstein_S5R3_4.49_i686-pc-linux-gnu_1
einstein_S5R3_4.49_graphics_i686-pc-linux-gnu
graphics_app
einstein_S5R4
einstein_S5R4_6.02_i686-pc-linux-gnu
einstein_S5R4_6.02_i686-pc-linux-gnu_0
einstein_S5R4_6.02_i686-pc-linux-gnu_1
einstein_S5R4_6.02_i686-pc-linux-gnu_2
einstein_S5R4_6.02_graphics_i686-pc-linux-gnu
einstein_S5R4
602
6.1.0
einstein_S5R4_6.02_i686-pc-linux-gnu
einstein_S5R4_6.02_i686-pc-linux-gnu_0
einstein_S5R4_6.02_i686-pc-linux-gnu_1
einstein_S5R4_6.02_i686-pc-linux-gnu_2
einstein_S5R4_6.02_graphics_i686-pc-linux-gnu
graphics_app
Cheers,
Gary.
Mac OS X on Intel details are
)
Mac OS X on Intel details are where? - or is that the silly question of the day!
RE: Mac OS X on Intel
)
The answer to your question is in the first post on this thread.
To repeat it here, Gary said "I don't intend to do files for other platforms since I have no way of testing. People interested in other platforms should be able to use what I post here as an example from which it should be pretty straight forward to edit their own versions."
RE: einstein_S5R4
)
From the app_info.xml in einstein_S5R4_6.02_i686-pc-linux-gnu.tar.gz:
I suppose it won't make any difference?
Ok, Gary. It seems to work
)
Ok, Gary.
It seems to work just fine. But, I guess the queue for S5R3 is empty and never will be loaded again. I will work with your app_info.xml until new one will come with new power app. Let us see what will go next...
RE: Here is the appropriate
)
Past installing on Win32- and Suse64-host i get following message:
05.08.2008 16:28:40|Einstein@Home|Message from server: No work can be sent for the applications you have selected
05.08.2008 16:28:40|Einstein@Home|Message from server: You have selected to receive work from other applications if no work is available for the applications you selected
05.08.2008 16:28:40|Einstein@Home|Message from server: Sending work from other applications
RE: RE: Here is the
)
Yes, it is normal. It will now download S5R4 files if your version of app_info allows this. Otherwise it will download S5R4 files but it will never start new application on these files unless you download them yourself.
RE: RE: RE: Here is the
)
download yourself? - I restarted on a linux box, didn't manually download any new app/s or change any app_info and get ..
does starting task not mean its running?
RE: download yourself? - I
)
But you did not use an app_info.xml file before, did you? The point is: if you had an app_info.xml file in place when the transition to S5R4 happened (because you were using a beta or power user app for S5R3), then the new 6.xx apps for S5R4 will not get downloaded automatically.