LHC@home

8/29/2005 1:23:00 PM|LHC@home|Requesting 3611 seconds of work, returning 0 results
8/29/2005 1:23:01 PM|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
8/29/2005 1:23:01 PM|LHC@home|Message from server: No work sent
8/29/2005 1:23:01 PM|LHC@home|Message from server: (won't finish in time) Computer on 97.4% of time, BOINC on 100.0% of that, this project gets 100.0% of that
8/29/2005 1:23:01 PM|LHC@home|Message from server: (Your network connection interval is longer than WU deadline)


How is this possible with a 1 day connect interval?

---

<img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83">

Can you zip up your TXT files in the BOINC directory? I would like to look at them, I don't think I have an example of this error ...

p.d.buck@comcast.net

Thanks!

And, no, I don't understand this either ...

Check in the file: global_prefs.xml

for: <work_buf_min_days>1.0</work_buf_min_days>

If this is not correct, then, well, that is why. For example, if you made the change in SETI@Home the interval change would not have been propagated down... I am interesteed in either case...

---

I just got a 5-day deadline workunit:
29/08/2005 18.39.17|LHC@home|Started download of wjun3C_v6s4hhnom_mqx__1__64.296_59.3176__8_10__6__55_1_sixvf_boinc390.zip
It is normal to have such short deadlines?

---

I to have had this message but I used my computer to do Einstein so I have Seti 200 Einstein 100 and LHC 100 is this causing a problem as I am doing no work with Einstein on this computer at this moment. I joined when Seti was down so it was only doing Einstein and LHC but I told my computer not to accept any more work from Einstein at this moment. Should I increase my percentage from 100 to 200 for LHC?

---

<blockquote>Can you zip up your TXT files in the BOINC directory? I would like to look at them, I don't think I have an example of this error ...</blockquote>


They are on their way Paul. Let me know if you get them.

-P

---

<img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83">

<blockquote>I just got a 5-day deadline workunit:
29/08/2005 18.39.17|LHC@home|Started download of wjun3C_v6s4hhnom_mqx__1__64.296_59.3176__8_10__6__55_1_sixvf_boinc390.zip
It is normal to have such short deadlines?</blockquote>

LHC has intrudiced a deadline optimiser that is supposed to estimate the deadline required to give the fastest completion of each batch of WUs. The deadline used to be 14 days, but since the optimiser was introduced it's been dropping - first to eight, and now to five.

Whilst the needs of the project are the main driver here, I can't help but think that shortening deadlines will cause some participants to leave in favour of a less demanding schedule. Not everyone can, or wants to devote enough processing time to meet these short deadlines.

---

Gaspode the UnDressed
http://www.littlevale.co.uk

Jeez. I just got over the excitement of Einstein giving us some slack on their tight deadlines, to be hit with this today from LHC.

As much as I hope the 14 day deadline works for Einstein, I hope LHC will give us our slack back. But I trust the devs here will do what is right for the project.

Oh well, most of us will try to roll with the punches. Just makes things not so easy...

---

I've also been getting the same error message. It started when using 10 day interval, lowering it stopped it for a while, now it says it on 5 day interval.

What's going on?

---

doesnt seem to be a bug.
there is SOME work in the queue dl 7.9.
and ALOT 3.9. is seems
so if you want that 4 days max now.

guess their really trying how fast it can go now ;)

---

<blockquote>They are on their way Paul. Let me know if you get them.</blockquote>
Pete,

Got them... the bad news is I am worse today ... so, not even sure I will be done with my simple work today ... :(

But, if nothing else, I have the logs you sent. Thanks!

Paul

---

My network connektion ?????
my pc is on since many Days 24 hours
only dissconeted by 24h dissconekt via ISP...

dont make me lol...
i left Einstein@home for that, now the same dam thing hits me on LHC...

Well it seems they all dont want my workpower
and i start to think about leaving Boinc complede...



29.08.2005 19:44:39|LHC@home|Message from server: No work sent
29.08.2005 19:44:39|LHC@home|Message from server: (won't finish in time) Computer on 56.5% of time, BOINC on 68.2% of that, this project gets 100.0% of that


this system is pissing me off realy...
i set my settings to 5 Days..
but i only get enough Work for one day...



29.08.2005 19:44:39|LHC@home|Message from server: (Your network connection interval is longer than WU deadline)
29.08.2005 19:44:39|LHC@home|No work from project
29.08.2005 19:44:40|LHC@home|Deferring communication with project for 22 hours, 30 minutes, and 56 seconds
29.08.2005 19:45:10||May run out of work in 5.00 days; requesting more
29.08.2005 20:44:40|LHC@home|Deferring communication with project for 21 hours, 30 minutes, and 56 seconds
29.08.2005 20:45:10||May run out of work in 5.00 days; requesting more
29.08.2005 21:44:40|LHC@home|Deferring communication with project for 20 hours, 30 minutes, and 56 seconds
29.08.2005 21:45:11||May run out of work in 5.00 days; requesting more
29.08.2005 22:44:50|LHC@home|Deferring communication with project for 19 hours, 30 minutes, and 52 seconds
29.08.2005 22:45:30||May run out of work in 5.00 days; requesting more
29.08.2005 23:44:44|LHC@home|Deferring communication with project for 18 hours, 30 minutes, and 52 seconds
29.08.2005 23:45:34||May run out of work in 5.00 days; requesting more
30.08.2005 00:44:45|LHC@home|Deferring communication with project for 17 hours, 30 minutes, and 52 seconds
30.08.2005 00:45:29||May run out of work in 5.00 days; requesting more
30.08.2005 01:44:45|LHC@home|Deferring communication with project for 16 hours, 30 minutes, and 51 seconds
30.08.2005 01:45:30||May run out of work in 5.00 days; requesting more
30.08.2005 02:44:45|LHC@home|Deferring communication with project for 15 hours, 30 minutes, and 51 seconds
30.08.2005 02:45:30||May run out of work in 5.00 days; requesting more
30.08.2005 03:44:46|LHC@home|Deferring communication with project for 14 hours, 30 minutes, and 50 seconds
30.08.2005 03:45:31||May run out of work in 5.00 days; requesting more
30.08.2005 04:44:47|LHC@home|Deferring communication with project for 13 hours, 30 minutes, and 49 seconds
30.08.2005 04:45:32||May run out of work in 5.00 days; requesting more
30.08.2005 05:44:48|LHC@home|Deferring communication with project for 12 hours, 30 minutes, and 49 seconds
30.08.2005 05:45:33||May run out of work in 5.00 days; requesting more
30.08.2005 06:44:48|LHC@home|Deferring communication with project for 11 hours, 30 minutes, and 48 seconds
30.08.2005 06:45:33||May run out of work in 5.00 days; requesting more
30.08.2005 07:44:49|LHC@home|Deferring communication with project for 10 hours, 30 minutes, and 48 seconds
30.08.2005 07:45:33||May run out of work in 5.00 days; requesting more
30.08.2005 08:44:49|LHC@home|Deferring communication with project for 9 hours, 30 minutes, and 47 seconds
30.08.2005 08:45:33||May run out of work in 5.00 days; requesting more
30.08.2005 09:44:55|LHC@home|Deferring communication with project for 8 hours, 30 minutes, and 46 seconds
30.08.2005 09:45:41||May run out of work in 5.00 days; requesting more
30.08.2005 10:44:50|LHC@home|Deferring communication with project for 7 hours, 30 minutes, and 46 seconds
30.08.2005 10:45:37||May run out of work in 5.00 days; requesting more
30.08.2005 11:44:50|LHC@home|Deferring communication with project for 6 hours, 30 minutes, and 46 seconds
30.08.2005 11:45:38||May run out of work in 5.00 days; requesting more
30.08.2005 18:15:40|LHC@home|Message from server: No work sent
30.08.2005 18:15:40|LHC@home|Message from server: (Your network connection interval is longer than WU deadline)
30.08.2005 18:45:03|LHC@home|Deferring communication with project for 30 minutes and 36 seconds
30.08.2005 18:45:49||May run out of work in 5.00 days; requesting more
30.08.2005 18:58:13||request_reschedule_cpus: project op
30.08.2005 18:58:14|LHC@home|Sending scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi
30.08.2005 18:58:14|LHC@home|Requesting 417597 seconds of work, returning 0 results
30.08.2005 18:58:16|LHC@home|Scheduler request to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded
30.08.2005 18:58:16|LHC@home|Message from server: No work sent
30.08.2005 18:58:16|LHC@home|Message from server: (Your network connection interval is longer than WU deadline)
30.08.2005 18:58:16|LHC@home|No work from project
30.08.2005 18:58:17|LHC@home|Deferring communication with project for 59 minutes and 58 seconds
30.08.2005 19:26:40||Running CPU benchmarks
30.08.2005 19:27:37||Benchmark results:
30.08.2005 19:27:37|| Number of CPUs: 1
30.08.2005 19:27:37|| 1719 double precision MIPS (Whetstone) per CPU
30.08.2005 19:27:37|| 3160 integer MIPS (Dhrystone) per CPU
30.08.2005 19:27:37||Finished CPU benchmarks



now i work with changed settings of 3 Days and also get the same amonth of Work for one day...
this hole System of WU and % of Worktime is a Pice of Junk...

also my WU´s allways come in with will be finished in 6 hours
but most the time i finish the WU´s in 50% of that time most WU´s finish between 3-4 Hours...

i realy realy dont understand how this system work and for what this dam Timing is good if it wont display the truth....
makes me think if Boinc dont work proplerly whats about the WUs ......

i was using Seti@home bevore Boinc but since it is on Boinc it never runs well, so i left and had a long time Einstine running, then i joined LHC and then Einstein hits me cuz they dont realy want shared work they want 100% just for theyr Projekt, and they dont accept computer sleeptimes..,
so i droped Einstein to... now the same dam Thing on LHC to....
makes me go mad...

piece of Junk realy annoyed User....


just one Question
were is the dam button were i can reset this Boinc Junk % Time counter piece to ZERO
so it noticed iam not longer in Vaccation and back 24h a day for LHC

---

Estimating the time a WU will take is harder on LHC@home than for many of the other projects. If the WU creates an orbit which is instable it can finish very quickly. Fiding out when orbits are stable is the point of this projects so varying WU times is unavoidable.

---

-
My 2 cents....This is just plain old stupid code. Whoever FUBAR'ed it go ahead and fix it.

Thankyou.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=2575&amp;prj=5" />

<blockquote>now i work with changed settings of 3 Days and also get the same amonth of Work for one day...
.
.
.
also my WU´s allways come in with will be finished in 6 hours
but most the time i finish the WU´s in 50% of that time most WU´s finish between 3-4 Hours...
</blockquote>
That's not a BOINC problem, that's an LHC problem. Because of how variable the work units are, it's difficult to know beforehand just how long one will take. Because of this, LHC provides a worst-case guess, which usually is off by quite a bit. I usually finish an LHC WU in a hair over 5 hours, yet the esitmate is over twice that. Just the nature of the beast.

<blockquote>this hole System of WU and % of Worktime is a Pice of Junk...</blockquote>
It seems to be a bit buggy (as can be seen with BOINC claiming 50% uptime for your 24/7 cruncher), but the concept is definatly nice to have IMO. A computer that is on (or has BOINC open) only 6 hours a day is going to need a lot less work to fill a N day cache than a 24/7 cruncher.


<blockquote>just one Question
were is the dam button were i can reset this Boinc Junk % Time counter piece to ZERO
so it noticed iam not longer in Vaccation and back 24h a day for LHC</blockquote>
It's probably hiding in one of the many XML files residing in your BOINC directory. I'm not sure which, but if you find it, closing BOINC and resetting it back to 100% should do the trick I'd think.

Puffy

---

<blockquote>
It's probably hiding in one of the many XML files residing in your BOINC directory. I'm not sure which, but if you find it, closing BOINC and resetting it back to 100% should do the trick I'd think.

Puffy</blockquote>

It can be found in the files: 'client_state.xml' and 'client_state_prev.xml'. there you have to write the suggested values in both files when the client is exited (see quote below).

(Quote from another user (I still not remember his name))
I suggest editing client_state.xml and 'client_state_prev.xml' under section of LHC and clear long term debt to zero

(master_url)http://lhcathome.cern.ch/(/master_url)
(project_name)LHC@home(/project_name)
...
- You have to search the line.
(short_term_debt)0.000000(/short_term_debt)
(long_term_debt)0.000000(/long_term_debt)

- Set time statistics to 1.000. (normally at the beginning (ca. 7th to 20th line)
Set each of the 3 lines at 1.0000!
(This is an example, where the host is 58% on)
(The '(' should be brackets, but then they react as HTML-tags)

(time_stats)
(on_frac)0.580293(/on_frac)
(connected_frac)1.000000(/connected_frac)
(active_frac)0.998390(/active_frac)
(cpu_efficiency)0.972158(/cpu_efficiency)
(last_update)xxxxx(/last_update)
(/time_stats)

- This will says BOINC that your computer is 100% of time on.
- edit both files!
- restart the client
(/quote)

A faster and harder methode is:
- exit the BOINCMGR
- delete the files 'client_state.xml' and 'client_state_prev.xml' (make a temp. copy before)
- restart the BOINCMGR

greetz littleBouncer

---

Used to run three boinc on this computer now only doing two my computer says this;02/09/2005 16:08:28|LHC@home|Message from server: (won't finish in time) Computer on 56.1% of time, BOINC on 100.0% of that, this project gets 33.3% of that
How do I download more work?

---

Do the math...

86400 seconds to a day. Your pc is on 56.1% of that. This = 48470 seconds.

Boinc crunches 100% of the remainder = 48470 seconds per day.

LHC@ Home is allocated 33.3% of the remainder = 15995 seconds per day.

15995 seconds = 266 minutes = 4 hours, 26 minutes per day to cruch LHC@Home.

Knowing that, your main PC's average WU time is 14135 seconds. BOINC 4.4x+ clients estimate WU completion time at a factor of (best approx guess) 2.25x to your actual crunch time. So.. your BOINC client thinks it needs 38104 seconds per workunit; in other words BOINC thinks you need 2.38 days per workunit. With a 5 day deadline, it's no wonder your client isn't D/L any L@H workunits.

My best suggestion is to reduce your "connect to network every x days" setting in your LHC@Home account to 2.5 days. It'll keep 1 wu in your posession at any time. Othwerise keep your pc on more, adjust LHC's project share, or both.

Good Luck!

---