LHC@home

LHC has been set to receive work at all times, since the recent work available cycle my computer did not ask for any. I have updated a few times & reset the project.

Now LHC has ran out of work, and guess what!, my computer has started to request work. I have not been overcommited. How can I can make sure I get work next time?

Alan

---

LHC has been set to receive work at all times, since the recent work available cycle my computer did not ask for any. I have updated a few times & reset the project.

Now LHC has ran out of work, and guess what!, my computer has started to request work. I have not been overcommited. How can I can make sure I get work next time?

Alan

One thing you can try is to suspend the other projects when you see LHC next has work. This should force a download from LHc once the client spots that it has no work it is allowed to run.

Sometimes (I do not understand why) with some versions of the client (sorry I do not remember which) it works better to suspend the indidual results (in the work tab) rather than the projects (in the project tab). Whichever you do, to get them working again you must resume in the sameplace - resuming a project will not restart a result if you suspended it from the work tab. You can resume the other projects as soon as the LHC work has downloaded.

Be careful doing this, you can end up over committed.

If you do find that you have more work than can be done in time then it is considerate to abort some unstarted WU from any of your projects, then the client will inform the project in due course and that work will be re-issued to other crunchers. Do this as soon as you can, so that the work is re-issued as soon as possible. Sadly it can take a while for the client to get round to sending the message back.

----

For more adventurous users, another thing you can try is to fix LHC with an implausibly large long term debt. This will force the other projects to download only one result at a time but allow LHC to grab a full cache whenever it can.

To do this stop BOINC from crunching, then edit the client_state.xml file. There is already a backup as a syntax error can break your client - but if you are nervous you may want to keep a manual backup as well. Under the LHC project find the long term debt and fill in a number like 333333333 (that is 9 digits). This represents about ten years debt, so you will not need to do this again soon! Save the file, restart BOINC. To balance the books, the client will force all other projects into negative debt, meaning they will only download work when LHC has none, and only one result at a time.

This kludge is fine if you want to crunch the max possible LHC whenever it is available, but will not allow a smaller proportion than that, as the client will run LHC flat out trying to eradicate its "debt".

(A bit like my Visa card really)

This works with all current clients, but strictly speaking it counts as a misuse of the debt system so it is not guaranteed to work with future releases. And don't tell JM7 ;-)

----

I hope one of these ideas proves of use.

---

LHC has been set to receive work at all times, since the recent work available cycle my computer did not ask for any. I have updated a few times & reset the project.

Now LHC has ran out of work, and guess what!, my computer has started to request work. I have not been overcommited. How can I can make sure I get work next time?

Alan

I set my resource share for LHC about 3 times higher than the other 8 projects I have attached and it seems to get a few units in during any batch and does not require me to notice work avalibility.
Loren

---

One thing you can try is to suspend the other projects when you see LHC next has work. This should force a download from LHc once the client spots that it has no work it is allowed to run.

Be careful doing this, you can end up over committed.

----

To do this stop BOINC from crunching, then edit the client_state.xml file. There is already a backup as a syntax error can break your client - but if you are nervous you may want to keep a manual backup as well. Under the LHC project find the long term debt and fill in a number like 333333333 (that is 9 digits). This represents about ten years debt, so you will not need to do this again soon! Save the file, restart BOINC. To balance the books, the client will force all other projects into negative debt, meaning they will only download work when LHC has none, and only one result at a time.
----

I hope one of these ideas proves of use.[/quote]


Many thanks for the info - certainly something to think about for next time

Alan

---

I just joined the project and it says no work available, is this because I'm overcommitted with other projects or is their no work being distrubuted at the current moment in time?

---

I just joined the project and it says no work available, is this because I'm overcommitted with other projects or is their no work being distrubuted at the current moment in time?

Hello Stefan,

Welcome to the club of the crunchers here. LHC@Home is a project that send out WU's in packets of some several days and afterwards the results of the work our hosts have been doing has to be analyzed by the physicians. During that time, we have to wait for new WU's.

As you can see on the homepage, the server status indicates "out of work". The last WU's have been send out this time some 2 or 3 days ago.

After some several days, which can be also some weeks, new WU's will be available again. Stay tuned.

---

Best greetings from Belgium
Thierry

LHC@Home is a project that send out WU's in packets of some several days and afterwards the results of the work our hosts have been doing has to be analyzed by the physicians.

To check, if they catched bird flu....

SCNR

Michael

---

Team Linux Users Everywhere