Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread), what do I have to do to start using it? It is my understanding that Seti will automagically update from 5.15 to 5.17 when each computer phones home after the release. I think that you replied to an earlier thread that your current apps would continue to run, but 5.17 is supposed to have the new credit adjustment factor, isn't it? Please advise how to proceed, and correct me on any of the above if I am in error. Would like to get onboard with 5.17 as soon as practical.

---

"Time is simply the mechanism that keeps everything from happening all at once."

If you are using an optimized app you have to run your cache empty.
Then delete your appinfo.xml otherwise the client will not update automatically.

regards
Mike

---

With each crime and every kindness we birth our future.

If you are using an optimized app you have to run your cache empty.
Then delete your appinfo.xml otherwise the client will not update automatically.

regards
Mike

Mike....I am not sure you are quite correct about running the cache empty. If I just rename the appinfo file and relaunch Boinc, it resumes crunching using the stock 5.15 app. If I then correct the appinfo file name and relaunch again, it goes back to optimized crunching.
So if I rename the appinfo file and am crunching with 5.15, it would do the update, wouldn't it?
And to clarify in my mind, will the 5.17 app when updated start crunching the existing wu's in my cache, or would they finish running on 5.15?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

The 5.17 S@H science application isn't ready to be released here yet.

                                                           Joe

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

The 5.17 S@H science application isn't ready to be released here yet.

                                                           Joe

Joe...Thank you for your clarification. My misunderstanding.
But perhaps Simon can take advantage of this thread to prequel how the transition to 5.17 will work when it IS ready for release.
I would assume we will have to download a new Chicken app and replace the program and appinfo file with the new ones. Will it still crunch the old wu's in my cache?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

The 5.17 S@H science application isn't ready to be released here yet.

                                                           Joe

Joe...Thank you for your clarification. My misunderstanding.
But perhaps Simon can take advantage of this thread to prequel how the transition to 5.17 will work when it IS ready for release.
I would assume we will have to download a new Chicken app and replace the program and appinfo file with the new ones. Will it still crunch the old wu's in my cache?

I'm sure Chicken, when he releases an optimized version of the 5.17 application, will have an updated app-info.xml file that will be just dropped in place to allow crunching with both apps.

However if the new app is released "before" Chicken gets his ready and you want to start using it, you will have to crunch your cache down and remove Chicken's app-info.xml file. This will let you download the new application and start crunching. It is possible to add the standard 5.17 application alongside Chicken's 5.15 but I don't know how you would get it unless Berkeley makes it available on a web page somewhere to download. You would then just copy the new 5.17 app into the directory and edit the app-info file to add the new application. If you are not very careful in editing this file you can trash work units, so when the time comes, maybe someone can post an already edited file to use without editing the file you have.

Hopefully it won't be too much of a delay between the time the standard application is released and Chicken has his optimized app ready so it wouldn't hurt a thing to keep crunching like you are for the time being.

You could possibly set your project to "no new tasks" when it is released and begin to crunch down your cache at that time. That way if there is a considerable delay in Chicken releasing his versions you will be ready to remove your app-info file and download the stock 5.17 app that much faster.

---

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.

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

The 5.17 S@H science application isn't ready to be released here yet.

                                                           Joe

Joe...Thank you for your clarification. My misunderstanding.
But perhaps Simon can take advantage of this thread to prequel how the transition to 5.17 will work when it IS ready for release.
I would assume we will have to download a new Chicken app and replace the program and appinfo file with the new ones. Will it still crunch the old wu's in my cache?

I'm sure Chicken, when he releases an optimized version of the 5.17 application, will have an updated app-info.xml file that will be just dropped in place to allow crunching with both apps.

However if the new app is released "before" Chicken gets his ready and you want to start using it, you will have to crunch your cache down and remove Chicken's app-info.xml file. This will let you download the new application and start crunching. It is possible to add the standard 5.17 application alongside Chicken's 5.15 but I don't know how you would get it unless Berkeley makes it available on a web page somewhere to download. You would then just copy the new 5.17 app into the directory and edit the app-info file to add the new application. If you are not very careful in editing this file you can trash work units, so when the time comes, maybe someone can post an already edited file to use without editing the file you have.

Hopefully it won't be too much of a delay between the time the standard application is released and Chicken has his optimized app ready so it wouldn't hurt a thing to keep crunching like you are for the time being.

You could possibly set your project to "no new tasks" when it is released and begin to crunch down your cache at that time. That way if there is a considerable delay in Chicken releasing his versions you will be ready to remove your app-info file and download the stock 5.17 app that much faster.

Are you sure this is going to be as complicated as all that? I have already found that I can disable the optimized app by simply renaming the appinfo file and relaunching Boinc. At that time I am processing with the standard 5.15 app. It should update to 5.17 at the next upload/download cycle then, correct?
When 5.17 does update, what happens to the 5.15 work in the cache? Does the new 5.17 app process it, or is the 5.15 app retained to use in processing the remaining wu's?

---

"Time is simply the mechanism that keeps everything from happening all at once."

[
Are you sure this is going to be as complicated as all that? I have already found that I can disable the optimized app by simply renaming the appinfo file and relaunching Boinc. At that time I am processing with the standard 5.15 app. It should update to 5.17 at the next upload/download cycle then, correct?
When 5.17 does update, what happens to the 5.15 work in the cache? Does the new 5.17 app process it, or is the 5.15 app retained to use in processing the remaining wu's?

Each wu is "tagged" with the application to use to crunch it when it is downloaded so unless I'm badly mistaken if you just remove the app-info file BOINC will still crunch the wu's with the application it's tagged for. The problem comes if you downloaded any wu's while you didn't have the app-info file. They will be tagged for the standard app so if you reinstall the app-info file these wu's won't be able to find the application to use to crunch them unless you put the filename into the app-info file. And since the presence of the app-info file suspends downloading the apps from Berkeley you will have to get the proper application and put it into the directory yourself. It's much simpler and safer to crunch your cache down then make any changes.
Try renaming "both" the app-info file "and" the application itself! WARNING, don't do this unless you feel like trashing a couple of wu's!

---

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.

Actually,

I'm reasonably sure that I will have a 5.17 compatible version ready before the official release happens here (since I'm already working on it).

Also, it should be just adding an extra line to app_info.xml - you can add one for 5.17 and give the file name of the new stock app, should mine not be ready, or drop in the app_info that will be included, which will go up to 5.17 and list my apps.

All that is required in both cases is a BOINC restart. The WUs get "tagged" only with a specific application version, not the app name itself.

HTH,
Simon

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

Actually,

I'm reasonably sure that I will have a 5.17 compatible version ready before the official release happens here (since I'm already working on it).
...
---CUT---

Hello!

this is very nice to know...











Greetings!

---

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

I wonder if Rom is still on schedule as planned.

---

me@rescam.org

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

I wonder if Rom is still on schedule as planned.

Perhaps these?

boinc_5.5.13_i686-pc-linux-gnu.sh 14-Aug-2006 21:12 3.0M
boinc_5.5.13_i686-pc-linux-gnu_debug.sh 14-Aug-2006 21:15 7.7M
boinc_5.5.13_windows_intelx86.exe 14-Aug-2006 19:29 9.6M

                                                Joe

Simon....if 5.17 is being launched today (as reported by misfit's post in 'Did 5.17 get released here' thread),
...

Misfit was saying that a new version of the BOINC client would probably appear today. That will have the fix to avoid the conflict of setiathome_enhanced version numbers here and on Beta Test.

The 5.17 S@H science application isn't ready to be released here yet.

                                                           Joe

Joe...Thank you for your clarification. My misunderstanding.
But perhaps Simon can take advantage of this thread to prequel how the transition to 5.17 will work when it IS ready for release.
I would assume we will have to download a new Chicken app and replace the program and appinfo file with the new ones. Will it still crunch the old wu's in my cache?

I think the odds are that 5.17 will never be released in the main project. There were several "bugs" (particularly for WIN9x) and a version 5.18 is being prepped for BETA release and testing (see this thread) in the beta forum. Don't know the details of the differences, but there may be several more versions (or not) before the application goes mainstream.

---

!!Stupidity should be PAINFUL!!

I must agree, since it seems that 5.17 regrettably still has a few rough edges.

Still, it's worth noting that there is some uncommited code in regards to the ALFA multibeam receiver that could also be the reason for 5.18.

It's important to distinguish between BOINC client and Seti@Home app here - some people were mistakenly under the impression a new S@H app would go mainstream, and not a new BOINC development version.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

I must agree, since it seems that 5.17 regrettably still has a few rough edges.

Still, it's worth noting that there is some uncommited code in regards to the ALFA multibeam receiver that could also be the reason for 5.18.

It's important to distinguish between BOINC client and Seti@Home app here - some people were mistakenly under the impression a new S@H app would go mainstream, and not a new BOINC development version.

Regards,
Simon.

Simon - I fully realized the difference between the BOINC version and the application, but I believe the post I replied to was suggesting a migration to 5.17 for your optimized apps in SETI main.

Haven't tried your optimized apps since I am only crunching BET at the moment, but from what I hear it is ALL HAIL THE GREAT CHICKEN of ANGNOR ;-) If I return to crunching SETI main, I will give them a shot.

Don

---

!!Stupidity should be PAINFUL!!

Simon, et al...

I will give some information that I know... Tomorrow it may be obsolete...

Some have said that "releasing here" may not be the best thing... Inviting those that are a participating is Seti Beta is a different story... Identifying that work and progress is happening is fine here... Testing, is normally a control group... So I am not sure how to have you address that... Some are putting the cart before the horse...

So you can sign up and be part of the cutting edge of Seti... It may not be clean but can be Fun and you meet New People... You can view what is happening in the Seti Beta Number Crunching Forum.

So that people know, trying the 5.17 application HERE MAY Cause Issues and Lost Credit...... WE also know that 5.18 should be out shortly... WE also know that there are issues with the first "AFLA" receiver workunits arriving... That is a Tech News thing...

So 5.18 will fix a few issues... The Changes to the BOINC Core Client will also fix a few things... Then YOu have to be willing to upgrade your BOINC Core Client... There is not a way to force an upgraded BOINC Client...

Generally, I am seeing a higher level of optimization on the 5.17 application but there are few problems... That would mean as you get it complied Users would see faster times returning Results...

So Patience is a good thing... Please be patient! Many are working on the issues...

Pappa

Actually,

I'm reasonably sure that I will have a 5.17 compatible version ready before the official release happens here (since I'm already working on it).

Also, it should be just adding an extra line to app_info.xml - you can add one for 5.17 and give the file name of the new stock app, should mine not be ready, or drop in the app_info that will be included, which will go up to 5.17 and list my apps.

All that is required in both cases is a BOINC restart. The WUs get "tagged" only with a specific application version, not the app name itself.

HTH,
Simon

---

Please consider a Donation to the Seti Project.

---CUT---
...So 5.18 will fix a few issues... The Changes to the BOINC Core Client will also fix a few things... Then YOu have to be willing to upgrade your BOINC Core Client... There is not a way to force an upgraded BOINC Client...
---CUT---

Hello!

It´s not possible/ good to let run the new S@H V5.18 for example in a Boinc V5.3.12.tx36?

What will be?

Greetings!

---

Dirk

Simon's stable release of 5.15 is fine... It has been tested and works... So Unless you want to Join Seti Beta... Then Please leave those types alone...

The Current Stable Release of the BOINC Core Client is 5.4.11, and it still has a few issues...

Now for the 5.3.12tx36, it is outdated and holds no advantage with the release of Seti Enhanced... The un installation is not as clean as one would hope... Always Make a Copy of your BONIC Folder before changes happen

Pappa

---CUT---
...So 5.18 will fix a few issues... The Changes to the BOINC Core Client will also fix a few things... Then YOu have to be willing to upgrade your BOINC Core Client... There is not a way to force an upgraded BOINC Client...
---CUT---

Hello!

It´s not possible/ good to let run the new S@H V5.18 for example in a Boinc V5.3.12.tx36?

What will be?

Greetings!

---

Please consider a Donation to the Seti Project.

For the moment I use Crunch3rs S@H V5.12 apps...
Because now Crunch3rs apps are faster on AMDs...

But when S@H V5.17 or 5.18 will be come to main S@H I "must" go to Simons apps... ;)


Greetings!

---

Dirk

This becoming a new thread...

As I am testing Simons on various machines and testing other BOINC Projects to help with the Cross Project Calibration... It makes life tough trying to keep up with what is happening and collecting the statistics that will level the playing field...

To a very large extent is sad that Crunch3r is not with us!
That is an old story... Too many mistakes to recover from... We want to prevent Simon from falling into the same trap...

Pappa

For the moment I use Crunch3rs S@H V5.12 apps...
Because now Crunch3rs apps are faster on AMDs...

But when S@H V5.17 or 5.18 will be come to main S@H I "must" go to Simons apps... ;)


Greetings!

---

Please consider a Donation to the Seti Project.