1) Message boards : News : More work coming now. (Message 25559)
Posted 10 May 2013 by David Ball
Post:
I was able to get some work units but they all run for 2 seconds and get validation inconclusive. They get the error message mentioned previously about the zip file having a problem.

The work units have an estimated run time of about 24 hours and I wasn't able to get any until I increased how much boinc requests at once to allow for that much time. Even that doesn't seem to work now. I haven't gotten any work units since

9 May 2013, 14:44:47 UTC




2) Message boards : Number crunching : Two announcements (Message 22191)
Posted 3 Apr 2010 by David Ball
Post:

I finally got re-attached to LHC. I hadn\'t even been able to reach the website since sometime last year. It looked like my IP address was blocked for some reason. I compared traceroutes with my teammates and mine always stopped at the last hop (161.23.3.204) before the LHC server while theirs continued on to hepboinc.ph.qmul.ac.uk [138.37.50.115]. Glad to see whatever it was got cleared up.

Thanks for the work you do. I\'m looking forward to being able to crunch WUs again.
3) Message boards : LHC@home Science : LHC magnets failed during test (Message 16992)
Posted 6 Jun 2007 by David Ball
Post:
For anybody that doesn't know, Fermilab are keeping an archive of magnet news items.


Thanks Henry!

That's a good link for info.

-- David
4) Message boards : LHC@home Science : LHC magnets failed during test (Message 16981)
Posted 5 Jun 2007 by David Ball
Post:
Repair of the triplet magnets would begin after validation by the reviewers. The immediate goal is to have a repaired triplet in another sector of the accelerator ready to participate in a pressure test scheduled for June 1.


Does anyone know if the scheduled June 1 pressure test took place and what happened ?

-- David



5) Message boards : Number crunching : LHC@home server being reconfigured today !! (Message 14807)
Posted 21 Sep 2006 by David Ball
Post:
Docking@home was just having the same problem with file downloads and found a fix.

See this forum post

It has something to do with the no_delete flag in the workunit template.

-- David
6) Questions and Answers : Windows : Time to completion always about 14 hours before workunit start (Message 8382)
Posted 10 Jul 2005 by David Ball
Post:
I have 2 very different machines running LHC. One always says a little over 14 hours and one always says a little under 14 hours for time to completion(TTC) until they start running. Both machines are running BOINC 4.45 and have BOINC jobs set to remain in memory when preempted. They each have 2+ GB of swap space and both run 3+ BOINC projects.

Machine # 1
OS: Windows XP Pro
CPU: Celeron 2.3
Ram: 1 GB
starting TTC: 14 hours +
Actual TTC: about 4 hours
Internet Connection: 56K Dial On Demand

Machine # 2
OS: Windows Server 2003
CPUS: Dual Xeon 2.8 HT
Virtual CPUS: 4
Max BOINC jobs running at once: 2 (they seem to get distributed evenly across the 4 virtual CPUs according to the performance graphs for the 4 virtual CPUs. With 2 BOINC jobs running my total CPU usage runs 50% - 55%.)
Ram: 1 GB
starting TTC: just under 14 hours
Actual TTC: about 3.25 hours
Internet Connection: 100 Mbps Ethernet


Any idea why the TTC is off by +10 hours until the job starts. Does this keep boinc from doing as much work on LHC since these jobs say they will take 14 hours until they actually get a little run time. I presume that BOINC bases how much work it fetches at once for each project on the TTC of jobs in the work queue (among other things) so it fetches less work at a time and work might not be available when it finally figures out that the work unit is 10 hours shorter than expected. This can also cause BOINC to go into it's time critical scheduling method because it thinks it has more work in the queue than it really does.

-- David




©2024 CERN