Thanks for your instructions and app_info file, Gary.
Looking good. I still have three S5R3 tasks, having loaded up for the weekend. Two of them were running under 4.36 when I exited from BOINC. Windows task manager now shows them as running under 4.46. Cool. Also the server sent me one S5R4 task, and this time it was accepted ("resent lost result").
FWIW, I also upgraded to BOINC 6.2.14 while I was at it.
Downloaded the S5R4 Linux files and added the relevant sections of the app_info.xml code below to my personal file.
[edit]Guess I should mention this is a Linux box.[/edit]
I downloaded a bunch of new S5R4 WUs along with resends of the 'ghosts' I received previously. When I suspended the S5R3 WUs I was crunching on so the S5R4 WUs would run, they errored out immediately with the following:
8/5/2008 8:54:01 PM|Einstein@Home|Starting h1_0226.95_S5R4__16_S5R4a_0
8/5/2008 8:54:01 PM|Einstein@Home|Starting task h1_0226.95_S5R4__16_S5R4a_0 using einstein_S5R4 version 602
8/5/2008 8:54:02 PM|Einstein@Home|Computation for task h1_0226.95_S5R4__17_S5R4a_0 finished
8/5/2008 8:54:02 PM|Einstein@Home|Output file h1_0226.95_S5R4__17_S5R4a_0_0 for task h1_0226.95_S5R4__17_S5R4a_0 absent
After doing some research on the downloaded 6.02 files, I found that the execute permission was missing. After adding it and downloading a new S5R4 WU, the S5R4 WU seems to be crunching OK.
From the app_info.xml in einstein_S5R4_6.02_i686-pc-linux-gnu.tar.gz:
6.3.0
I suppose it won't make any difference?
I'm not sure where you would have got the gzipped tarfile that you quoted and I'm equally puzzled as to why what is now the stock app would contain an app_info.xml file since it's not needed to just run stock S5R4. I didn't see any tarfiles in the download directory I linked to but perhaps you have found a tarfile where the new app may have been tested internally by project staff and therefore needed to be run under the AP mechanism? How did you get that file?
In any case, I just used the api_version as specified in the last S5R3 test apps that were released a couple of months ago. I don't think it has any significant effect on what I'm trying to do, ie be dual capable under BOINC 5.10.45. If I was trying to run "bleeding edge" BOINC I would probably be a bit more concerned :-). I'm sure if anyone knows more about the significance of that particular variable, they will tell us about it. My testing didn't reveal any problems with the 6.1.0 value.
It seems to work just fine. But, I guess the queue for S5R3 is empty and never will be loaded again....
I think you will find that is not true. Right at the moment, there are plenty of hosts finishing off their caches of S5R3 and each one of those is seen by the scheduler as a suitable target for any resend work it has on its books. Therefore resend work will be hardly available at the moment - it's being sent out faster than it is being created.
Imagine what will happen in 10 days time from now. Virtually 100% of hosts with S5R3 work on board now will have run out and will have been sent all the new stuff by the scheduler. Relatively few hosts will still be announcing to the scheduler that they can immediately accept any S5R3. Tasks that were issued 8 days ago (and have missed the deadline) will be expiring and the scheduler will need to make decisions about what to do with them. If your host "phones home" and tells the scheduler that it can accept S5R3 work, there will be a very good chance that the scheduler will have some to send, more likely at that point than right now.
Thanks for your instructions and app_info file, Gary.
Looking good. I still have three S5R3 tasks, having loaded up for the weekend. Two of them were running under 4.36 when I exited from BOINC. Windows task manager now shows them as running under 4.46. Cool. Also the server sent me one S5R4 task, and this time it was accepted ("resent lost result").
FWIW, I also upgraded to BOINC 6.2.14 while I was at it.
Thanks for the report. It's good to know that all seems to be working as intended.
After doing some research on the downloaded 6.02 files, I found that the execute permission was missing. After adding it and downloading a new S5R4 WU, the S5R4 WU seems to be crunching OK.
Something like this (missing execute permission under Linux) was reported some time ago but my brain is a bit useless these days and I don't recall the details. Somebody more on the ball than me will probably chime in with a link to the previous info.
I downloaded all the files for S5R4 from the EAH download directory (as linked) using firefox and "save link as ..." to place them on a Windows share that all my Linux hosts and Windows hosts could access. My Linux hosts see it as a samba share. Any given Linux host just copies what it needs from the samba share and the files do have the execute bit set. I've just checked and they have rwxr--r-- permissions, the owner being gary:gary as intended.
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.
A word to those who have never tried an app_info.xml file here.
If you add this file, BOINC does exactly what it reads and throws anything
else away - if you've spent 5 hrs on some work and app_info.xml doesnt explicitly
mention the program you crunched it on, that work is deleted immediately.
Best if you (a) wait till you've uploaded your work. and (b) make a copy of all your data before restarting BOINC!
...A word to those who have never tried an app_info.xml file here.
If you add this file, BOINC does exactly what it reads and throws anything
else away - if you've spent 5 hrs on some work and app_info.xml doesnt explicitly
mention the program you crunched it on, that work is deleted immediately....
And another word to the wise, if you have started to use the app_info.xml and then decide to not use it and go back to the standard application, be sure to complete the existing work unit first!
Otherwise (like just happened to me! ;), the unit will trash itself and you will lose all of your time, because a new work unit will start up!
...A word to those who have never tried an app_info.xml file here.
If you add this file, BOINC does exactly what it reads and throws anything
else away - if you've spent 5 hrs on some work and app_info.xml doesnt explicitly
mention the program you crunched it on, that work is deleted immediately....
And another word to the wise, if you have started to use the app_info.xml and then decide to not use it and go back to the standard application, be sure to complete the existing work unit first!
Otherwise (like just happened to me! ;), the unit will trash itself and you will lose all of your time, because a new work unit will start up!
Okay, lets restate:
Best if you (a) wait till you've uploaded your work, (b) made sure you are offline, and (c) make a copy of all your BOINC data and subfolders before restarting BOINC!
Another approach, as the S5R4
)
Another approach, as the S5R4 stock client can make use of SSE, will be to let the S4R3 cache run down completely then D/L the stock client.
I suppose another way would be to detach from the project and reattach, when all the results from completed S5R3s are sent?
Shih-Tzu are clever, cuddly, playful and rule!! Jack Russell are feisty!
Thanks for your instructions
)
Thanks for your instructions and app_info file, Gary.
Looking good. I still have three S5R3 tasks, having loaded up for the weekend. Two of them were running under 4.36 when I exited from BOINC. Windows task manager now shows them as running under 4.46. Cool. Also the server sent me one S5R4 task, and this time it was accepted ("resent lost result").
FWIW, I also upgraded to BOINC 6.2.14 while I was at it.
Downloaded the S5R4 Linux
)
Downloaded the S5R4 Linux files and added the relevant sections of the app_info.xml code below to my personal file.
[edit]Guess I should mention this is a Linux box.[/edit]
I downloaded a bunch of new S5R4 WUs along with resends of the 'ghosts' I received previously. When I suspended the S5R3 WUs I was crunching on so the S5R4 WUs would run, they errored out immediately with the following:
After doing some research on the downloaded 6.02 files, I found that the execute permission was missing. After adding it and downloading a new S5R4 WU, the S5R4 WU seems to be crunching OK.
Seti Classic Final Total: 11446 WU.
RE: RE:
)
I'm not sure where you would have got the gzipped tarfile that you quoted and I'm equally puzzled as to why what is now the stock app would contain an app_info.xml file since it's not needed to just run stock S5R4. I didn't see any tarfiles in the download directory I linked to but perhaps you have found a tarfile where the new app may have been tested internally by project staff and therefore needed to be run under the AP mechanism? How did you get that file?
In any case, I just used the api_version as specified in the last S5R3 test apps that were released a couple of months ago. I don't think it has any significant effect on what I'm trying to do, ie be dual capable under BOINC 5.10.45. If I was trying to run "bleeding edge" BOINC I would probably be a bit more concerned :-). I'm sure if anyone knows more about the significance of that particular variable, they will tell us about it. My testing didn't reveal any problems with the 6.1.0 value.
Cheers,
Gary.
RE: It seems to work just
)
I think you will find that is not true. Right at the moment, there are plenty of hosts finishing off their caches of S5R3 and each one of those is seen by the scheduler as a suitable target for any resend work it has on its books. Therefore resend work will be hardly available at the moment - it's being sent out faster than it is being created.
Imagine what will happen in 10 days time from now. Virtually 100% of hosts with S5R3 work on board now will have run out and will have been sent all the new stuff by the scheduler. Relatively few hosts will still be announcing to the scheduler that they can immediately accept any S5R3. Tasks that were issued 8 days ago (and have missed the deadline) will be expiring and the scheduler will need to make decisions about what to do with them. If your host "phones home" and tells the scheduler that it can accept S5R3 work, there will be a very good chance that the scheduler will have some to send, more likely at that point than right now.
Cheers,
Gary.
RE: Thanks for your
)
Thanks for the report. It's good to know that all seems to be working as intended.
Cheers,
Gary.
RE: After doing some
)
Something like this (missing execute permission under Linux) was reported some time ago but my brain is a bit useless these days and I don't recall the details. Somebody more on the ball than me will probably chime in with a link to the previous info.
I downloaded all the files for S5R4 from the EAH download directory (as linked) using firefox and "save link as ..." to place them on a Windows share that all my Linux hosts and Windows hosts could access. My Linux hosts see it as a samba share. Any given Linux host just copies what it needs from the samba share and the files do have the execute bit set. I've just checked and they have rwxr--r-- permissions, the owner being gary:gary as intended.
I'm sorry that you had that trouble.
Cheers,
Gary.
RE: I have tested this
)
A word to those who have never tried an app_info.xml file here.
If you add this file, BOINC does exactly what it reads and throws anything
else away - if you've spent 5 hrs on some work and app_info.xml doesnt explicitly
mention the program you crunched it on, that work is deleted immediately.
Best if you (a) wait till you've uploaded your work. and (b) make a copy of all your data before restarting BOINC!
RE: ...A word to those who
)
And another word to the wise, if you have started to use the app_info.xml and then decide to not use it and go back to the standard application, be sure to complete the existing work unit first!
Otherwise (like just happened to me! ;), the unit will trash itself and you will lose all of your time, because a new work unit will start up!
RE: RE: ...A word to
)
Okay, lets restate:
Best if you (a) wait till you've uploaded your work, (b) made sure you are offline, and (c) make a copy of all your BOINC data and subfolders before restarting BOINC!