Is it necessary to use "Reset Project" to force the download of 4.05? I've tried "Update" and switched BOINC off/on but no sign of an upgrade yet. Or will it only download next time a WU is complete to avois losing it mid-flow?

Any advice?

When your client contacts the scheduler to get more units, it will download the new app automatically. Units are tied to the current app version in use when downloaded, so the few units left in the cache will finish with the old app and the new units downloaded with the new app will use it when the client gets to them.

> Is it necessary to use "Reset Project" to force the download of 4.05? I've
> tried "Update" and switched BOINC off/on but no sign of an upgrade yet. Or
> will it only download next time a WU is complete to avois losing it mid-flow?
>
> Any advice?
>

BOINC will download it when it needs it - sit tight

The core client does not automatically upgrade. You have to go to http://setiweb.ssl.berkeley.edu/download.php/ You will find 4.09 of the CC there.

Are you sure? Seems the new version change is the Seti@home 4.03 to 4.05, not Boinc 4.09.

ya'll are getting the seti@home science app confused with the BOINC core client. The current BOINC core client version is 4.09. It was at 4.05 until a couple weeks ago. This software will NOT update itself. The seti@home science app just switched from 4.03 to 4.05. This WILL auto-update itself as soon as you get a new work unit that requires the 4.05 client.


---------------------------------------
- A member of The Knights Who Say NI!
Possibly the best stats site in the universe:
http://boinc-kwsn.no-ip.info

Please don't confuse people with that "Core Client" because it is too easy to confuse with the client application which is the science application.

The correct term is BOINC Work Manager and Science Application.

However, the rest is correct. The BOINC program that you interact with has to be downloaded and installed using the normal windows install process for an application. Once installed you then "attach" the BOINC Work Manager to projects.

Once attached, the BOINC WOrk Manager will automatically download and use the correct science application to process the work units. If the science application is updated, a new version will be downloaded as and when the BOINC Work Manager contacts the projects.

In some cases you will have several versions of science application tied to different work units. For example, right now I have some PCs with work units still in progress with the 4.03 science application and some work units tied to the new 4.05 version. If there is a major flaw with a version of the science application, the project can update the BOINC Work Manager so that it will use the latest science application on all of the work units.

The whole point to all of this is that now we have traceability of the results down to the specific version of the components that were used to process the work. This makes the science more rigerous and allows for the ability to reproduce the "lab" conditions exactly so the expiriment can be repeated if desired.
<p>
For BOINC Documentation: Click Me!

Running 4.11 (at my own risk of course,
just a note, have had no probs. at all).
A question specific to PDB and JM7 I know
you guys are Alpha testers, any news or
guesstimates as to when linux will get a
new client version? core 4.09 is still
using S@H 4.02 for Linux.

I know it's not wise to run 4.11, but I
could not resist. Please forgive me for
jumping the gun :)

Regards,

Joe

Joe,

> Running 4.11 (at my own risk of course,
> just a note, have had no probs. at all).
> A question specific to PDB and JM7 I know
> you guys are Alpha testers, any news or
> guesstimates as to when linux will get a
> new client version? core 4.09 is still
> using S@H 4.02 for Linux.
>
> I know it's not wise to run 4.11, but I
> could not resist. Please forgive me for
> jumping the gun :)

Actually, I am not an alpha tester ... never got asked. Though, likely if asked I would have said no ...

The main reason is that I can't read C code for beans, Java either since it is more or less C in disguise. Why they could/did not select a decent language, like Pascal, to copy is beyond me ...

I suspect that with the press on to get the new cross-platform GUI going it will happen at that time, unless some new problem crops up that mandates a patch. Rom said a couple weeks ... so, assuming normal programmer bravado, I would suspect that the latest and greatest will not be seen till about the end of next month.

Because we are dumping (aparently) the wiindows GUI (good riddance) and going to the concept of a command-line style executable and a remotely connected GUI, I would further say that it will be mid/late November before we have the bugs worked out... Now, go ahead and prove me wrong!

By the way, you should be happy, your version did not need fixing!

:)

<p>
For BOINC Documentation: Click Me!

> Rom said a couple weeks ... so, assuming normal programmer bravado, I
> would suspect that the latest and greatest will not be seen till about the end
> of next month.

(looks on then your message was posted...)
So you're saying nothing before end of November. ;)

>
> Because we are dumping (aparently) the wiindows GUI (good riddance) and going
> to the concept of a command-line style executable and a remotely connected
> GUI, I would further say that it will be mid/late November before we have the
> bugs worked out... Now, go ahead and prove me wrong!
>

To be consistent with the above lines, you must be meaning mid/late December, so has already proved you wrong. ;)

My only hope is they've got some decent new hardware till the new gui is released, so then the bugs are fixed they're ready to kill off "classic". :)

> To be consistent with the above lines, you must be meaning mid/late December,
> so has already proved you wrong. ;)

For whatever reason, probably because I rarely care ... I thought this morning was the 31 of september ...

> My only hope is they've got some decent new hardware till the new gui is
> released, so then the bugs are fixed they're ready to kill off "classic". :)

Killing off Classic won't take place (to my knowledge till M3 ... Of course, I don't know if the task base is still being used to track current progress, or not, ...
<p>
For BOINC Documentation: Click Me!

>
> For whatever reason, probably because I rarely care ... I thought this morning
> was the 31 of september ...
>

LOL...

>
> Killing off Classic won't take place (to my knowledge till M3 ... Of course,
> I don't know if the task base is still being used to track current progress,
> or not, ...

They're still using the Taskbase, just look on the time for the latest additions. ;)

From a post 18. March 2004:
> M2: decommission old SETI@home
> (i.e. turn off the current SETI@home data server)
> The major gating items:
> - Separate-GUI architecture
> - GUIs available for Win, Mac OSX, Unix/X11

So then the separate gui is finished & the servers can take the load they'll kill off "classic". :)
Of course, it's possible the servers can't take the load before all M3-tasks is finished...

BTW, the other milestones was:
> M1: public launch of SETI@home on BOINC
> The major gating items are:
> - No critical/high priority bugs in BOINC
> - SETI@home failures under 5%
> - preparations for increased server load
> In this release, the client versions will be as they
> currently are (GUI/screensaver for Win, CLI for Mac/unix)
>
> M3: support for Climateprediction.net and other projects
> Gating items:
> - client data management
> - directory structure in project dirs
> - WU interleaving
> - trickle messages
> - file compression
> - support for non-CPU-intensive applications
>

> By the way, you should be happy, your version did not need fixing!
>
> :)

Paul,

I am very glad, actually the linux cores and client versions
have had no problems, for which I am very grateful. I am
anxiously awaiting the new gui, as are the rest of us, including
you my good sir, who run linux. As always Paul thank you for your
kind response, and the time and effort you put in to the
documentation project, peace and best regards to you always.

Your Fellow Crunching Friend,

Joe :)

My BIONIC will not upgrade seti to 4.05... help?
:: iSONEWS

SETI@home - 2004-10-02 03:40:20 - Message from server: No work available (your core client is out of date - please upgrade)


:: iSONEWS

> SETI@home - 2004-10-02 03:40:20 - Message from server: No work available (your
> core client is out of date - please upgrade)
>

Upgrade here

> SETI@home - 2004-10-02 03:40:20 - Message from server: No work available (your
> core client is out of date - please upgrade)
>
>

The core client must always be manually downloaded & installed.

For download, http://setiweb.ssl.berkeley.edu/sah/download.php

I can see how it can confuse people though ...

I already had 4.05 Boinc (from Climate Prediction).
The download site says latest is version 4.09 from 17th September 2004
The front news page says:
"September 30, 2004
UPDATED: A new version (4.05) of the windows SETI@home client is available (and will be automatically picked up by your core clients next time you contact our servers)."
My current Seti@home is 4.03 and did not get upgraded to 4.05 last time I connected - maybe it will when I move Boinc to 4.09 but I won't risk it until the current outstanding work is completed.

> I can see how it can confuse people though ...

Having a bent toward well written material that can communicate the design I was appalled in the early days of the Beta (well, *MY* early days) that they were using the term core client and client a a few other bad names. Even worse, then, was they in fact had about 4 names for the same item on the web site.

I had coined one pair that I thought then (and still do) that better described the system where we have as the BOINC Framework (currently the name for that component is BOINC Work Manager) and Plug-In science modules. I thought that not only did they meet the technical intentions well, they were less threatening to the lay public (the bulk of the participants).

Truce was declared and I agreed to stop using the better name if they would stop using the bad ones ... of course I see that we have another name for the science applications (called "the worker" in some places in the developer site).

Anyway, the legacy of confusion lingers on as people persist in using the depreciated terms... and all i can do is write it up and explain it as best I can ... and I soldier on ...

@Joe

I plan to move one of my computers to Linux soon (when I get more time and have caught up with many of the changes that I am trying to finish) because even without the GUI I can use BOINC View (I still wonder how I got along without it)... So I now can look at what is happening on my Mac as I bask in the glories of OS-X ...

:)

But I need to get more experience as the Linux parts of my writing stinks because of the lack of hands on ...

<p>
For BOINC Documentation: Click Me!

In what can only be called a ridiculous oversight by the magnificent dev team, upgrading BOINC to 4.09 means that all half finished units have been lost as i am required to reattach to all my projects. This is also a tedious task as i have to go hunting around for projects ID's and such.

Surely when it a simple upgrade proceedure the projects (and the current workunits) details can be stored on my PC and picked up again after the upgrade has been completed? Wouldn't thake make beter sense? It'd sure make life easier for me. And i'm sure ClimatePrediction won't be too happy that they are getting plenty of info from the first half of their workunits but nothing from the last half.

Just my thoughts post BOINC upgrade.