Hello,

I have now the optimized Crunch3r client 4.11.
And the "old" app_info.xml.
When I do nothing, I don´t become the new original Seti@home 5.12.

Now there are the new app_info.xml and the optimized Seti@home 5.12 client at the Crunch3rs homepage.

What must I do now, to become the Enhanced WUs?

I think:
First I download the new app_info.xml from Crunch3rs homepage and take it "over" the old one.
Then I start Boinc again and then the new original Seti@home 5.12 must be download.
Then I take Crunch3rs optimized Seti@home 5.12 and take it "over" the original Seti@home 5.12.

And then everythink is O.K. ...

I have the Boinc 5.3.12.tx36 from Truxoft.
I must now delete the CC calibration for Seti@home.
Or is the name of the Enhanced Project: Seti@home Enhanced.
Then the calibration is going okay when I have calibration only for Seti@home?
I think not, but... maybe yes...


Is everything right, or completely wrong?

Greetings!

---

Hello,

I have now the optimized Crunch3r client 4.11.
And the "old" app_info.xml.
When I do nothing, I don�t become the new original Seti@home 5.12.

I had four machines with almost exactly your situation.

stock boincmgr, running tx36 client, running crunch3r 4.11 SETI ap with calibration and also Einstein.

My most recent, and most successful, conversion, I did this way:

1. set SETI to "no new work" in BOINCmgr, and set a short queue size in BOINC global preferences
2. when existing SETI work is finished, assure all results uploaded and reported.
3. stop BOINCmgr
4. unzip the appropriate crunch3r 5.12 zip package to your SETI directory
5. replace the app_info.xml in your boinc directory with the one on crunch3r's web page.
6. edit trux_prefs.xml to disable calibration for SETI. (no, this entry makes no distinction for seti_enhanced).
7. restart BOINCmgr
8. re-enable "new work" for SETI

When things appear to be working for a result or two, gradually push up your queue length to your preferred value. (a sudden change may give you gross overfetch, especially if you have a low resource share project).

---

I originally installed BOINC as a service. I ran my cache down, restarted, and am now crunching with SE. How do I stop setiathome_5.12_windows_intelx86.exe long enough to replace it with Crunch3r's optimized app? I can kill BOINC Manager in the the Task Manager but when I kill the SETI worker, it re-appears after a few seconds.

Thanks.

I originally installed BOINC as a service. I ran my cache down, restarted, and am now crunching with SE. How do I stop setiathome_5.12_windows_intelx86.exe long enough to replace it with Crunch3r's optimized app? I can kill BOINC Manager in the the Task Manager but when I kill the SETI worker, it re-appears after a few seconds.

Thanks.

You need to kill the boinc.exe otherwise it starts the apps. all over again.

---

Join BOINC United now!

5. replace the app_info.xml in your boinc directory with the one on crunch3r's web page.

As this thread is revived, I'll just say that as of a minute ago, the app_info.xml on crunch3r's web site appears not to handle version 513.

However, I posted one I've been using for some hours here:

app_info.xml for 418, 512, 513 using crunch3r aps

I believe this one works for running non-enhanced SETI using un-renamed crunch3r 4.11, and for running enhanced SETI 512 and 513 using un-renamed crunch3r 5.12.


If you first click on the reply button, you can see a copy of the text with the indentations preserved. I think that version is better for copy/paste, since it is easier to edit.

---

Thanks for the quick response, Crunch3r! I didn't see that in the list.

One follow-up: Does app_info.xml go in the SETI project directory or just in the BOINC directory?

Thanks again.
QS

One follow-up: Does app_info.xml go in the SETI project directory or just in the BOINC directory?

The seti directory.

Ouch, you caught an error in my suggested conversion sequence, but the post is too old for me to edit. Thanks. I apologize to anyone I led astray on this point.

---

Thanks archae86.

QS

5. replace the app_info.xml in your boinc directory with the one on crunch3r's web page.

As this thread is revived, I'll just say that as of a minute ago, the app_info.xml on crunch3r's web site appears not to handle version 513.

However, I posted one I've been using for some hours here:

app_info.xml for 418, 512, 513 using crunch3r aps

I believe this one works for running non-enhanced SETI using un-renamed crunch3r 4.11, and for running enhanced SETI 512 and 513 using un-renamed crunch3r 5.12.


If you first click on the reply button, you can see a copy of the text with the indentations preserved. I think that version is better for copy/paste, since it is easier to edit.

Are 5.13 WU's already in the wild?

I thought those were just in the Seti Beta project still. Current Seti Apps page: http://setiathome.berkeley.edu/apps.php still shows 5.12 as the current build for the regular Seti Enhanced.

---

When I move to Enhanced I'll follow the script given below by archae86 for Dirk Sadowski on my 4 Windoz machines.

Like archae86, I'll be coming from the Crunch3r SETI clients (4.11) to the Enhanced versions using the archae86 script. As directed I'll put the app_info.xml the SETI client folder.

As a precaution I have have down loaded copies of Crunch3r's optimised Enhanced clients (both 5.11 and 5.12) for P3s (with MMX and SSE) and Xeons (with MMX, SSE and SSE2 - older Xeons).

Some questions of you, please?

1. What is the difference between 5.11 and 5.12 in both types (P3 and Xeons)?

2. Is there any problems using 5.11 rather than 5.12? Does 5.11 have problems that 5.12 solves, for example?

3. I noticed 5.11, after unzipping, for both the P3 and the Xeons contains -

* The setiathome_5.11_windows_intelx86 application file (2240KB size)
* The setiathome_5.11_windows_intelx86 PDB file (1539KB size)
* And the app_info xml file

While the same for 5.12 contains -

* The setiathome_5.12_windows_intelx86 application file (1624KB size)
* And the app_info xml file

For 5.12, the rest of the files are WordPad read read me, copyright, authors, etc, files. The most noticable file missing was the -

setiathome_5.1x_windows_intel86 PDB file.

Does the optimised Enhanced Ver 5.12 not need the PDB file, or should the 5.11 PDB file be included?

A further point, if you please?

I saw that in the BOINC folder, for those using the optimised 5.2.12 version, that the truxoft_pref xml file needs to be modified to allow the correct completed WU claim to be given!

Is this correct?
and, how is it amended?
to what should it be amended, if at all?

---

It's good to be back amongst friends and colleagues

1. What is the difference between 5.11 and 5.12 in both types (P3 and Xeons)?

5.11 does not meet the current credit claiming standards--it will overclaim substantially. There may be other issues, that is the one I know about.

The most noticable file missing was the setiathome_5.1x_windows_intel86 PDB file.

I've had no 5.xx PDB file in my directories for several days (since I upgraded to crunch3r 5.12). I've not noticed a problem nor seen message log or stderr entries suggesting this is a problem.

As you may have noticed, there are some frequent-posting forum members with strong hostility to the optimized applications. Not using 5.11, with its over-claiming, will be a small measure to damping that hostility.

---

1. What is the difference between 5.11 and 5.12 in both types (P3 and Xeons)?

5.11 does not meet the current credit claiming standards--it will overclaim substantially. There may be other issues, that is the one I know about.

The most noticable file missing was the setiathome_5.1x_windows_intel86 PDB file.

I've had no 5.xx PDB file in my directories for several days (since I upgraded to crunch3r 5.12). I've not noticed a problem nor seen message log or stderr entries suggesting this is a problem.

As you may have noticed, there are some frequent-posting forum members with strong hostility to the optimized applications. Not using 5.11, with its over-claiming, will be a small measure to damping that hostility.

Thanx

This means I'll look to using the 5.12 application without the 5.11 PDB file?

While looking around I saw for those using the optimised BOINC 5.2.13, that it was suggested the truxoft_pref xml file needs to be modified to allow the correct completed WU claim to be given!

Is this correct?
and, how is it amended?
to what should it be amended, if at all?

---

It's good to be back amongst friends and colleagues

This means I'll look to using the 5.12 application with the 5.11 PDB file?

No, I think you can do without any 5.xx PDB file, though if you are intending to run crunch3r 4.11, I'd certainly leave the 4.11 PDB file in the directory.

---

This means I'll look to using the 5.12 application with the 5.11 PDB file?

No, I think you can do without any 5.xx PDB file, though if you are intending to run crunch3r 4.11, I'd certainly leave the 4.11 PDB file in the directory.

Sorry I should have stated "without", and you were so quick I had not amended it before you replied.

Correction taken on board!!

I'll run without a PDB file, as I plan to switch fully to 5.12 soon!

---

It's good to be back amongst friends and colleagues

I saw that in the BOINC folder, for those using the optimised 5.2.12 version, that the truxoft_pref xml file needs to be modified to allow the correct completed WU claim to be given!

Is this correct?
and, how is it amended?
to what should it be amended, if at all?

The claim is that tx36 output is ignored for the actual credit claimed for enhanced SETI so some are advocating leaving calibration on.

I was disconcerted to see that back when I was running crunch3r 5.11 with tx36 calibration still turned on, the message log claim from the tx36 client as to the adjustment it had made in credit claim matched the credit claim on the site. Hence I wondered ...

Even assuming the standard position that tx36 calibration does not affect claim is correct it is still true that the adjusted (falsified) CPU time tx36 calculates is uploaded. It is also true that tx36 treats enhanced/unenhanced as one project, so the adjustments for unenhanced will rapidly diverge from the good values you are used to.

My personal advice is to turn tx36 calibration off for SETI in this case. As I run Einstein using akosf applications for which the calibration is helpful, I choose to do this by changing the line in my ...\\boinc\\truxoft_prefs.xml from:

<calibrate_credit>all</calibrate_credit>

to:

<calibrate_credit>Einstein@Home</calibrate_credit>

---

Even assuming the standard position that tx36 calibration does not affect claim is correct it is still true that the adjusted (falsified) CPU time tx36 calculates is uploaded. It is also true that tx36 treats enhanced/unenhanced as one project, so the adjustments for unenhanced will rapidly diverge from the good values you are used to.

My personal advice is to turn tx36 calibration off for SETI in this case. As I run Einstein using akosf applications for which the calibration is helpful, I choose to do this by changing the line in my ...\\boinc\\truxoft_prefs.xml from:

<calibrate_credit>all</calibrate_credit>

to:

<calibrate_credit>Einstein@Home</calibrate_credit>

I only crunch SETI at present, and this is likely to continue.

If the SETI Enhanced "completed WU times" are the only things to be afffected and SETI is the only project being supported. Then it could be argued that the tuxoft_pref.xml file could be renamed -old and left unused!

Would this be OK?

---

It's good to be back amongst friends and colleagues

So what happens to a 4.18 WU? I've been through a couple of 5.12 WUs, and now have a 4.18 WU listed in my queue as the next to process.

Does the 5.12 worker know what to do with this? Or do I have to find a copy of the 4.18 worker first?

QS

So what happens to a 4.18 WU? I've been through a couple of 5.12 WUs, and now have a 4.18 WU listed in my queue as the next to process.

Does the 5.12 worker know what to do with this? Or do I have to find a copy of the 4.18 worker first?

QS

Just do nothing. You should still have the 4.18 applicaton on your drive. If you had been running an optimized version and have removed the app_info.xml file to get the enhanced 5.12 work units, then boinc will download a standard 4.18 application to crunch it with.

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

So what happens to a 4.18 WU? I've been through a couple of 5.12 WUs, and now have a 4.18 WU listed in my queue as the next to process.

Does the 5.12 worker know what to do with this? Or do I have to find a copy of the 4.18 worker first?

QS

Just do nothing. You should still have the 4.18 applicaton on your drive. If you had been running an optimized version and have removed the app_info.xml file to get the enhanced 5.12 work units, then boinc will download a standard 4.18 application to crunch it with.

Jim-R - thanks for the comments, but ...

Unlike QSilver, I am currently planing to stay with the 4.11 optimised application for all this week and most of next. Or, that is until the numbers of BOINC Manager "messages tab" are heavily red and read "Message from server: no work. No work from project". To do this I will leave the app_info.xml file active.

Clearly this will apply only to the 4.11 optimised SETI client.

When things start becoming difficult to grab 4.11 WUs then, at this point, I will move exclusively over to the optimised 5.12 client as described below.

At least that is what I plan!

So, should I revise this and plan to crunch both versions, as many are doing, but not using the optimised versions (as downloaded by BOINC Manager?)

---

It's good to be back amongst friends and colleagues

Just do nothing. You should still have the 4.18 applicaton on your drive. If you had been running an optimized version and have removed the app_info.xml file to get the enhanced 5.12 work units, then boinc will download a standard 4.18 application to crunch it with.

No, just converted to Crunch3r's 4.11 optimized worker after I saw your note. But thanks for the comment...I caught it right before it started the 4.18 WU.

John Clark--I just converted over to 5.12 about 10 hours ago. Based on what I've run through today and what's in the queue, it's at an exact 50/50 split between 4.18 and 5.12 WUs.

QS