I suspect you need to change the first version_num in the file to 418. :)

Yes you're right on that one.

whoops, got that. (referring to my signature ;-))
updated the zip file at my download site.

I conjure you to read the included readme and not to use this app_info.xml unless you got the 4.18!!
Otherwise you risk to lose all your workunits that are on your pc!

AndyK

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

In the absence of an optimised 4.18 client, is it safe to modify the app_info.xml to use the 4.11 optimised client for workunits requiring 4.18?

That question has my very interest too, cause we don't know, if the results will verify... :)

Hmm, I cannot see why they would'nt. Remember that we still have an old Linux client about, and as long as this client is there in its current format, then the math should be the same, hence the wu's should verify ok

Very good point, and since the YAOSCW clients don't include graphics anyway, that removes the stated benefit for upgrading to 4.18.

Modified app_info.xml now in place, but I can't test it with 4.18 as Berkeley are still giving out 4.11 work. If anyone wants it, I'm happy to upload.

---

Stats site - http://www.teamocuk.co.uk - still alive and (just about) kicking.

Modified app_info.xml now in place, but I can't test it with 4.18 as Berkeley are still giving out 4.11 work. If anyone wants it, I'm happy to upload.

quoting my own answer:

updated the zip file at my download site.

And

Only WUs which were downloaded with the 4.18, require the 4.18 for crunching...

But I can't tell you, if we automatically get downloaded the 4.18 while using the app_info.xml referring only to the 4.11.

Time will tell...

AndyK

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

Modified app_info.xml now in place, but I can't test it with 4.18 as Berkeley are still giving out 4.11 work. If anyone wants it, I'm happy to upload.

quoting my own answer:

updated the zip file at my download site.

And

Only WUs which were downloaded with the 4.18, require the 4.18 for crunching...

But I can't tell you, if we automatically get downloaded the 4.18 while using the app_info.xml referring only to the 4.11.

Time will tell...

AndyK

On this pc here at work, I got a wu downloaded at about 9:20 local time today. This 1 gotta be a 4.18 wu. In the work tab, Boinc reports that he will use 4.11 for this wu. And I have not edited the xml file in any way. Its the goos old 1 with 4.09 to 4.11 and 4.11 to 4.11 from the 10/6 2005

---

Best regards / B52

Some info from here. The wu that I mentioned in the above post have now been crunched by 1 pc

http://setiathome.berkeley.edu/result.php?resultid=76900577

And the result clearly says that it is a 4.18 wu. So without any changes to the xml file, wu's will be crunched with TMR's 4.11

---

Best regards / B52

ok, reverting my assumptions.
Sorry, for beeing such skeptical.

please make search as described and in addidtion please take a look at the <file_ref><file_name> tag
which files are referred to?

I got a wu downloaded at about 9:20 local time today. This 1 gotta be a 4.18 wu.

What makes you presuming it's gotta be a 4.18 wu?

Did you look into the client_state.xml and looked for it?
make a copy of the client_state.xml, name it look.txt or whatever you want.
open that copied file in you favorite text editor.
do a search for <app_name>setiathome</app_name>
scroll down and take a look at the workunit tags <version_num>

Do you find 1 with value set to 418?

btw:
A wu does not contain version information, there is no 4.11wu nor a 4.18wu.
It's just the reference which version is to be used to crunch this wu.

AndyK

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

I got a wu downloaded at about 9:20 local time today. This 1 gotta be a 4.18 wu.

What makes you presuming it's gotta be a 4.18 wu?

Did you look into the client_state.xml and looked for it?
make a copy of the client_state.xml, name it look.txt or whatever you want.
open that copied file in you favorite text editor.
do a search for <workunit>
scroll down and take a look at the tags <version_num>

Do you find 1 with value set to 418?

btw:
A wu does not contain version information, there is no 4.11wu nor a 4.18wu.
It's just the reference which version is to be used to crunch this wu.

AndyK

Hi Andy

I have just examined the client_state.xml file, and here on my pc, it says that it will be done by tmr's 4.11, but as said, then the wu have allready been crunched by another pc using 4.18, so it seems as if nowt have to be done to retain the 4.11 cruncher.

That was my point m8

---

Best regards / B52

On this pc here at work, I got a wu downloaded at about 9:20 local time today. This 1 gotta be a 4.18 wu. In the work tab, Boinc reports that he will use 4.11 for this wu. And I have not edited the xml file in any way. Its the goos old 1 with 4.09 to 4.11 and 4.11 to 4.11 from the 10/6 2005

I have just downloaded two workunits - one on a PC with an optimised client, and one on a PC without. The unoptimised PC got 4.18 work, the optimised PC got 4.11 work. Version numbers confirmed as correct by checking version_num in the client_state.xml (one was 418, the other 411). Looks like you are correct. :)

quoting my own answer:

updated the zip file at my download site.

Since an optimised 4.18 doesn't exist yet, those who download work for the 4.18 client and then choose to optimise will need an app_info.xml that uses the current 4.11 client to process 4.18 work (otherwise these new workunits will be deleted).

---

Stats site - http://www.teamocuk.co.uk - still alive and (just about) kicking.

crap! I wrote here...

Since an optimised 4.18 doesn't exist yet, those who download work for the 4.18 client and then choose to optimise will need an app_info.xml that uses the current 4.11 client

Berserker, you can still use the old link for the 4.11 app_info.xml

I hoped I pointed out enough, that the danger of losing workunits using the new app_info.xml without having the 4.18 application is the logical conclusion.

AndyK

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

Hi B52

Think we're talking to cross purposes.

Of course you will crunch this workunit with 4.11, even if it was crunched already by a pc with 4.18.
I just wanted to point out, that the workunit is not coming with any version information from the server.
It depends what version (your 4.11) made the download

If you look at all the other results for that workunit 18511023, you see the "application version" is still blank.
It will be filled when you upload the finished result.

AndyK

PS: I love the song "Love Shack" from the B52's! ;-)

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

Berserker, you can still use the old link for the 4.11 app_info.xml

Hope this clears up the problem. I have a computer that has 4.18 work now and I want to optimize it. If I use your 4.11 app_info.xml, that doesn't have an application to process the 4.18 work, so BOINC won't know what to do with it and it will be deleted.

I have the unoptimised 4.18 client, so your 4.18 app_info.xml will work for me, but I would not get any benefit from doing that.

My solution is to modify the 4.11 app_info.xml to process new 4.18 work using the existing 4.11 optimised client. Since Berkeley seem to allow workunits to be processed with either 4.11 or 4.18, this shouldn't cause any problems, but we won't know for sure until some workunits are finished and validated.

---

Stats site - http://www.teamocuk.co.uk - still alive and (just about) kicking.

but we won't know for sure until some workunits are finished and validated.

Right.

Here's another information I'm assuming:
More and more crunchers without optimized client and without app_info.xml get the 4.18 application, but me.
I think I can say that using an optimized client with the appropriate app_info.xml prevents you from getting new versions.
In this case you have to look at upgrading the appliction on your own!

AndyK

---

Want to know your pending credit?


The biggest bug is sitting 10 inch in front of the screen.

Hi B52

Think we're talking to cross purposes.

Of course you will crunch this workunit with 4.11, even if it was crunched already by a pc with 4.18.
I just wanted to point out, that the workunit is not coming with any version information from the server.
It depends what version (your 4.11) made the download

If you look at all the other results for that workunit 18511023, you see the "application version" is still blank.
It will be filled when you upload the finished result.

AndyK

PS: I love the song "Love Shack" from the B52's! ;-)

hehe, think that you are correct there m8.

You are warning pps about the danger of using the new app xml file unless they specifically wants their wu's to be crunched with the new 4.18, whilst I was trying to tell pps that if they left the xml as is, then they would continue to use tmr's 4.11 cruncher.

Correct m8 ?? Anyway, I think that pps have gotten both your and my point.

And yes, The B52's have written a lot of great stuff, and cause I really love their music, hence my nick/handle :)))

---

Best regards / B52

It sounds like all this means

1. If you're currently using 4.11 don't make any changes. You will continue using 4.11 and 4.18 will NOT be downloaded to your machine.

2. Do not expect an optimized 4.18 since the changes were to graphics functions which are not included in the optimized versions anyway.

---

Help and BOINC documentation is available here.

You will continue using 4.11 and 4.18 will NOT be downloaded to your machine.

Except I don't think that's true. I had 4.11 with the xml file and 4.18 was d/l'd to my P4.

---

Nope, no 4.18 with original 4.11 xml by AndyK.

Happy crunching,

---

I think I can say that using an optimized client with the appropriate app_info.xml prevents you from getting new versions.
In this case you have to look at upgrading the appliction on your own!

Correct. The app_info.xml causes BOINC to ignore whatever version Berkeley happens to be sending out, and will process with whatever optimized version you happen to be running.

In other words, your PC will not download 4.18 if you have a previous app_info.xml file in place. It can't. That's the whole purpose of the anonymous platform function.

I can forsee this causing validation problems as peoples optimized science apps get further and further out of date. Luckily, I think the type of person running an optimized app is the type that will keep on top of things, and will upgrade to a new optimized app as soon as it's available. :)

Do you have any for linux using IPP4.1 and new Intel C++ compiler 9.0? I currently have yours but it's using IPP4.1 and Intel C++ compiler 8.1.

Here is my own P version. (statically linked) No other versions.

This is the fastest on my P4 Prescott.

YAOSCL-P-r8.1.tar.gz

Incredibly bizzare

./setiathome-4.7.i686-pc-linux-gnu

Fatal Error : This program was not built to run on the processor in your system.

CPU: Intel(R) Xeon(TM) CPU 3.06GHz

Makes no sense to me. Oh well, I'll just use the ICC 8.1 version. That works for me.

---

I just installed Boinc 4.45 on a new PC and it then downloaded the new 4.18 for Seti.

But when I copied TMR's 4.11 and AnyK's latest app_info.xml, nothing happened except it ignored the changes and keeps crunching 4.18. The 4.11 is gone and no trace of it, but all WU's and the new app_info.xml are still there. New WU's downloads and they're assigned to 4.18.

I didn't lose any work, but it seems the new app_info needs some tweaking...

I didn't lose any work, but it seems the new app_info needs some tweaking...

Looking in the app_info.xml, the .exe name is the same as the official 4.18 app. So basically, the app_info.xml is telling BOINC to associate any WUs tied to older .exe's to run with the new official 4.18 spp. It's even telling the new 4.18 WUs to run with 4.18.

Not quite sure how useful this is... Unless the optimized app has a different name/version number, it will be difficult to tell if you are running the optimized app or not. The only way to tell would be to run a WU and check the completion time.

Perhaps the concept is that the user will edit the app_info.xml?