Two of those files
MultiBeam_Kernels_r3584.cl_GeForceGTX950.bin_V7_SoG_35900
r3584_IntelRCoreTMi76700KCPU400GHz_x86.wisdom
Are created when you run the app.

So, copying the other 3 files will be all that is needed, aside from editing app_info.xml?

Two of those files
MultiBeam_Kernels_r3584.cl_GeForceGTX950.bin_V7_SoG_35900
r3584_IntelRCoreTMi76700KCPU400GHz_x86.wisdom
Are created when you run the app.

So, copying the other 3 files will be all that is needed, aside from editing app_info.xml?

mb_cmdline-8.22_windows_intel__opencl_nvidia_SoG.txt
Is only necessary if you want to get more from the application for your particular hardware, and is used when running stock.
It's worth it IMHO.

EDIT-
If you're running Lunatics the configuration file is
mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt

---

Grant
Darwin NT

mb_cmdline-8.22_windows_intel__opencl_nvidia_SoG.txt
Is only necessary if you want to get more from the application for your particular hardware, and is used when running stock.
It's worth it IMHO.

EDIT-
If you're running Lunatics the configuration file is
mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt

OK, so I will only need to copy two files then?

♦   MultiBeam_Kernels_r3584.cl
♦   setiathome_8.22_windows_intelx86__opencl_nvidia_SoG.exe

That sounds right, you can create the txt file if you use it, but it also might complain if it's not there too.

That sounds right, you can create the txt file if you use it, but it also might complain if it's not there too.

OK, I'll let my cache run out before making the attempt.

You have to do EVERYTHING right.... cross your fingers ...... and hold your tongue - just so to use the method you describe.

. . Well yes, the tongue position is a very important part of the process :)

. . But seriously that is why I modified it from the one originally posted. Even though it is fiddly it will now work every time, unless you fail to follow the procedure as listed. I am just in the end phase of recovering 140 or so ghosts on Mi_Burrito. But I have to confess the repetitive runs to gather them all in lots of 20 is tedious. Just one more lot to go ....

In my case of 600 "ghosted" tasks the process would take forever at 20 tasks retrieved every sequence. Also when you are constantly at your server defined limits because you process work so quickly you would have to run your onboard tasks down to nil after a NNT to even begin the sequence.

. . Actually that part is not true, you only have to have enough head room in your cache to accommodate the 20 tasks it will recover. So if you have 600 tasks cached on a 5 GPU rig and 600 ghosted you only have to set NNT and wait until you have processed say about 30 tasks, do an upload and report with NNT still set then begin the recovery process. It will download a nice little package of 20 "lost" tasks.

I found out the hard way that what you would think is a simple task of restoring an old backup of client_state.xml has its own dangers. I lost 5 years of work history at Einstein because the backup restoration caused a change in cross-project ID and a new computer Host ID to be created at Einstein because BOINC detected a unexpected change in <rpc_seqno>. This also caused a "phantom" Host ID at Einstein and loss of 13 million credits because they are attached to the old Host ID. If you try to merge the old and new hosts BOINC always chooses the newest Host ID.

That fiasco is why I will never edit app_info manually anymore. I'll just have to wait for Richard to crank out a new Lunatics installer with r3584 in it or whatever Raistmer is working on his latest revision.

. . Been there and done that. One of the earlier times things went awry and I realised I had "ghosted" a cache ful of work units I tried restoring them by copying back the old client_state.xml, and things went nuts. As soon as things get screwed up some part of BOINC does some housekeeping and deletes ALL files it thinks are unnecessary, so after restoring the old client_state it looks for tasks where the file is no longer cached on your HDD. You get a whole lot of runtime errors as each one tries then crashes out, one after another :(

. . But that is why I am also happy to sit back and wait for a new Lunatics Beta release. I really appreciate Richards efforts because then I can get to use what is becoming available.

. . Like you I have had issues with Host IDs. I re-installed BOINC on two machines because of hardware upgrades and got it wrong in the process so that BOIC created new Host IDs and I lost the original ones. I executed the meld option, hoping it would restore the original ID, but like you I was disappointed when the old ID was then lost.

. . It's all part of the fun (?) ....

Stephen

:)

Consider ARM6 phone crunching only when charging.
http://setiathome.berkeley.edu/host_app_versions.php?hostid=7435236

Среднее время обработки 25.85 days

That is, ~4 weeks. No need to touch deadlines.
If "97%" complete "just in one-two days" then fine, those tasks will be validated and deleted from BOINC database faster. They even not need to be kept week, just those 2 days.
But other still have chance to participate.

P.S. What need to be touched instead is quota system that fails to catch hyper-fast broken GPU hosts. That can produce thousands of broken results per day - amount that slow crunchers will not accumulate through whole year!

. . Yes, many of us have seen the results of rigs like that ....

Stephen

:(

"Inflated database" it's quite relative term. As long as it works OK it's not "inflated". And as I already said, the influence of slow hosts on that perceived "inflation" over-estimated.
So yes, it is right to provide ability to help SETI on everything that can compute.

. . I think the main thrust of his comment was that it does not require 6 week time out periods to keep such a low end device participating in SETI

That's right spirit. And spirit much more valuable than revenue. Should be even in "free market" world :P

. . LOL ... I love that

Stephen

:)

First of all it is Richards decision when he will release a new Installer.

From my testing point of view and being part of the installer crew the work is done.

Of course we shouldn't forget you either Mike! People write the code, people need to test the code, people then provide installers for the tested code, it's a team effort all round.

Happy New Year to all Setizens.

Yes, +1 Chris. And a Happy New Year to all Setizens, too.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

First of all it is Richards decision when he will release a new Installer.

From my testing point of view and being part of the installer crew the work is done.

Of course we shouldn't forget you either Mike! People write the code, people need to test the code, people then provide installers for the tested code, it's a team effort all round.

Happy New Year to all Setizens.

. . H A P P Y
. . . . . . . . . .N E W
. . . . . . . . . . . . . . . Y E A R !

Stephen

:)

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

---

With each crime and every kindness we birth our future.

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

. . Hi Mike

. . As I understand it the process involves copying the 2 application files (.cl and .exe) into the project/setiathome directory and editing the app_info.xml file. But does that editing require adding a new app listing for V8.22 in every appropriate place or simply find and replace all occurrences of V8.20? Or is it something else completely. I have never attempted to do this.

Stephen

:(

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

. . Hi Mike

. . As I understand it the process involves copying the 2 application files (.cl and .exe) into the project/setiathome directory and editing the app_info.xml file. But does that editing require adding a new app listing for V8.22 in every appropriate place or simply find and replace all occurrences of V8.20? Or is it something else completely. I have never attempted to do this.

Stephen

:(

It depends you are running optimized already or stock application.
I see you are running optimized already so no need to change the plan class.
But you need to copy the 2 files also into the slots directory so you don`t loose work.
Check in boinc manager which slots are running GPU apps suspend boinc and copy the files.
Triple check the files names don`t have any typos in appinfo.xml

---

With each crime and every kindness we birth our future.

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

. . Hi Mike

. . As I understand it the process involves copying the 2 application files (.cl and .exe) into the project/setiathome directory and editing the app_info.xml file. But does that editing require adding a new app listing for V8.22 in every appropriate place or simply find and replace all occurrences of V8.20? Or is it something else completely. I have never attempted to do this.

Stephen

:(

It depends you are running optimized already or stock application.
I see you are running optimized already so no need to change the plan class.
But you need to copy the 2 files also into the slots directory so you don`t loose work.
Check in boinc manager which slots are running GPU apps suspend boinc and copy the files.
Triple check the files names don`t have any typos in appinfo.xml

Wouldn't it be safer/easier to suspend other tasks and just let the running tasks finish before making the changes, just to be sure? But I am still unclear about what to edit in app_info. I thought I would need to replace the references to V8.20 with V8.22 since V8.20 is what Lunatics has set as the default app to use. I can see why this makes many people feel nervous.

Stephen

:(

Greetings

Happy New Year to all.

Safest thing to do, is complete all outstanding workunits you have in your cache. Then do they required editing of the app_info file.

That way you will not ghost any workunits.

Bit rusty myself on editing that file, but if you have a nice short one, its not to bad, but some have some pretty big app_info files.

Got a big run of some hot weather coming my way, so whilst the machines are down, I have some time to do some reading and editing.

Happy crunching all.

PS. Thats all I can offer at the moment, as I am bit rusty, and dont want to put up wrong information.

Here are some posts on how to avoid ghosting WUs:

•  Message 1770911
•  Message 1770950 (the 3rd & 4th ¶)
•  Message 1770956

For those who want to install r_3584 ( setiathome_8.22) manually, its available now on my website.

. . Hi Mike

. . As I understand it the process involves copying the 2 application files (.cl and .exe) into the project/setiathome directory and editing the app_info.xml file. But does that editing require adding a new app listing for V8.22 in every appropriate place or simply find and replace all occurrences of V8.20? Or is it something else completely. I have never attempted to do this.

Stephen

:(

You have to replace every instance of the old app in your app_info with the name of of the new app with Notepad. Same for .CL file. You have to use the Find function with the Replace All option. DON'T try to type the name yourself, use a Copy/Paste of the new app name from the Properties page of the new app. Raistmer has a tendency to change his naming conventions from time to time between revision releases. He caught a lot of people off guard with a double underline between the revision number and the SoG part of the name once. Was very easy to miss the double length of the underline which caused everyone to dump their work because the app_name was called out incorrectly in app_info. Best plan to avoid dumping and "ghosting" work is to run your GPU work down to nil and then edit app_info. You can also change the version number of the app if you want to if you have run your work out but it isn't really necessary,

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I seem to remember that it was Eric who did the double underline thing....But Raistmer been know to move where SoG appears in the name of the exe line

---

Yes, I believe you are correct. Didn't mean to put the blame on Raistmer by mistake. Just wanted to point out the dangers of trying to input the app name manually.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Greetings

Happy New Year to all.

Safest thing to do, is complete all outstanding workunits you have in your cache. Then do they required editing of the app_info file.

That way you will not ghost any workunits.

Bit rusty myself on editing that file, but if you have a nice short one, its not to bad, but some have some pretty big app_info files.

Got a big run of some hot weather coming my way, so whilst the machines are down, I have some time to do some reading and editing.

Happy crunching all.

PS. Thats all I can offer at the moment, as I am bit rusty, and dont want to put up wrong information.

H A P P Y
. . . . . . N E W
. . . . . . . . . . . Y E A R !

. . to you too Tazzduke.

. . I am cautious but still manage to screw things up from time to time, so that makes me even more cautious ...

. . I want to know EXACTLY what to do before I even think about trying it :)

Stephen

:)