LHC@home

> As long we have host's like <a> href="http://lhcathome.cern.ch/results.php?hostid=11355">this.[/url]....

If you like to look at other peoples hosts, you can look at this this.
:-) :-)

---

> > The problem is that boinc does not bind a WorkUnit to a specific version
> of the executable. (Chrulle)
>
> ??? Is this really true? I'm (almost 100%) positive that on other BOINC
> projects that each WU specifies which EXE it needs to run. Isn't that what
> the "application" column is showing?

A WU is bound to what in BOINC terms is called an APP, whereas a new version is only a new APP_VERSION.

---

Chrulle
Research Assistant &amp; Ex-LHC@home developer
Niels Bohr Institute

>
> > > The problem is that boinc does not bind a WorkUnit to a specific
> version
> > of the executable. (Chrulle)
> >
> > ??? Is this really true? I'm (almost 100%) positive that on other BOINC
> > projects that each WU specifies which EXE it needs to run. Isn't that
> what
> > the "application" column is showing?
>
> A WU is bound to what in BOINC terms is called an APP, whereas a new version
> is only a new APP_VERSION.
>
Allthough I don't do much with the server side of things I think the apps can be bound in 3 different ways but don't ask me how to change it.

1) app and version bound to workunit at creation.
2) app bound to workunit at creation, latest version picked up at download.
3) #2 plus a later version can be picked up at a restart of the client. (Never actually seen this one, just hints of it in CVS.)

Most projects are set up to use version #2. #3 requires a newer version to be downloaded for some other reason and then a restart of the client. #1 is the most entertaining since the workunits might use version 2, 1, 3, 1, 5, 2 if that is the order they are (re)issued in and the version number is changing fairly quickly.

Now that I think about it I may have #3 described wrong, it may be app bound at creation and latest version picked up from the client. If so that would explain why this project is having trouble getting new versions out, the client never realises it should be downloading a new version.

---

BOINC WIKI

BOINCing since 2002/12/8

> > <B><I>PLEASE</B></I> do not continue to take work and then not crunch it
> just
> > because some problem with the client or whatever makes you mad and say
> > "The hell with this project"

> @mlcudd
> Perhaps you did the "project reset" after you saw that you have 4.64 Units?
> If so, you have lost this work units.

Hi KSBA,
I appreciate your comment, however i have not reste the project. i waited patiently for WU's and recieved them when they were available. Some time back I had detached from the project while it was down ( last year) but have been consistentantly connected from that point on. I am at a loss. I make a copy of my project files when I recieve new WU's so that I mark them off when complete. The WU's I listed previously I have no record of.

Respectfully,

Rocky

---

<img src="http://boincwapstats.sourceforge.net/summary.php?name=ML%20Cudd&amp;team=US%20Navy&amp;seti=123863&amp;einstein=4173&amp;lhc=1091&amp;climate=2545&amp;predictor=7916&amp;style=6&amp;ctx=yellow">
WinXP SP2 Boinc - 4.44
Have A Great Day!

For a project that was marked "dead" by some ... well ... OOPS!

They have 2K pending issue ... and I have a fair collection of them on a number of my computers ... they seem to be "short" run time WU though ... not that I care ...

:)

---

I also never Detached or Re-Attached anything with LHC, and now I got everything running smooth without any workarounds required (the last "Loopers" went through after I temporarily set switching time to 12hrs ;) ).

IMHO the Project is just somewhat "special" with it not having a continuous flow of Work.
But if that Computing share they're getting with BOINC is all they need, that's not so bad...

When they come in from time to time, they get processed; otherwise, the other Projects get the full load...

---

Scientific Network : 45000 MHz - 77824 MB - 1970 GB

Logan 5:

"I personally think that every BOINC project has some measure of merit and or potential in it's particular field"

I totally agree with you on that.

Chrulle:

"A WU is bound to what in BOINC terms is called an APP, whereas a new version is only a new APP_VERSION"

Now I'm confused. I've had wu's for different versions of app's on other projects on my computer at the same time. I thought this was the way boinc was supposed to automatically upgrade the science apps - where did I go wrong there?

---

> I sadly think this Project has gone the way of the Predictor Project and
> theres just not enough interest in it anymore ...

Predictor is running well.

It looks like there might be a lack of understanding/information
or people speak about the same but using other wording.


everybody is "right"

APP_VERSION is very well the 4.6x
the APP is sixtrack (for LHC)

a couple of days ago:

What the GUI shows is
APP + APP_VERSION concatinated to 1 string

In yet other words: we can only control minimum application version that can be used when handing out workunits. That is, we cannot say which version of sixtrack should be used for a given workunit. Only that a given workunit is to be processed using some application (always sixtrack, at least for now), and minimum version number of that application.

The reason that there can be multiple application version crunching at the same time is that after a workunit has been started with some application version, it will be used until the workunit is done (or fails).

---

Markku Degerholm
LHC@home admin

> In yet other words: we can only control minimum application version that can
> be used when handing out workunits. That is, we cannot say which version of
> sixtrack should be used for a given workunit. Only that a given workunit is to
> be processed using some application (always sixtrack, at least for now), and
> minimum version number of that application.
>
> The reason that there can be multiple application version crunching at the
> same time is that after a workunit has been started with some application
> version, it will be used until the workunit is done (or fails).
>
I know that S@H links the project app version to the result when it is sent to the computer. I was under the impression that this was standard.

---

BOINC WIKI

> I know that S@H links the project app version to the result when it is sent to
> the computer. I was under the impression that this was standard.

Me too :)

---

> I know that S@H links the project app version to the result when it is sent to
> the computer. I was under the impression that this was standard.

Well, I don't know a way to do that. Except than to create a new application entry for each new version (one can of course link a workunit to an application).

---

Markku Degerholm
LHC@home admin