LHC@home

TY Dora. Six-Track is only the name of the program they're running. It has no real connecton with the actual number of tracks in the LHC. In several places they are at minimum space so six tracks wouldn't fit equipment wise and the redundancy would be a waste.

The length of the old LEP and the LHC may be primarily the same at 27 Km, but the equipment in the LHC is significantly bigger.

It has to be when you're out to destroy the universe, like Mike. :)

---

I am a Geek. We surf in the dark web pages no others will enter.
We stand on the router and no one may pass.
We live for the Web. We die for the Web.

.... What happens when two particles traveling in opposite directions at nearly the speed of light hit each other? A collision at nearly twice the speed of light!
....
.

hmmm....

Sort of like setting your
" Connect to network about every..."
to 20 (twice the max allowed...)

....
....
I don't know what this "Cache" thing is....
....
.

It seems so!

Take a look at your general preferences for:
Connect to network about every
(determines size of work cache; maximum 10 days)

Bigger numbers allow you to get more work.

But, you should set your "Connect to network about every"
to no more than one-tenth.
That is the "fair" thing to do...

My machines that are always connect (usually) have a cache of 0.1 days. My machines that can only connect once a day have a cache setting of 1.0 days. If it were any less, they would not be able to crunch all of the time (they are attached to enough projects so that I don't really care which project they crunch for at any given time). The reason that I say usually 0.1 days is that I work on the CPU scheduler and work fetch algorithms - sometimes I need to test some boundary conditions (and I have not yet gotten an LHC result when the cache was set high on the dev machines).

---

BOINC WIKI

I think they are 'restricting' the workunits from the hog by doing smaller batch sizes. They run out of work in just an hour or two. Big Cache helps more now. It knocked two of my computers out because one has a internet connection that has to compete with Emule P2P (because I'm not getting rid of it) and the other that is only online when I swap the vzw pc-card to it. So only my work computer will ever get work now because it has a internet conncection that is good for it begging for work every few minutes.

---

My... LinkSite | Blog | Pictures

Quote fron Rosetta@Home RSS-Newsfeed:
"Jul 15, 2006
A note from David Baker: We desperately need as much CPU power as possible for the next two weeks--there are more than 25 CASP targets due, including some that are our best shots at really high resolution models. Frustratingly, we won't be able to do anywhere near as much sampling as we had planned for these proteins as there are so many coming due near the same time, and thus can't really expect the accuracy we had hoped for. So if it is at all possible for you to increase your rosetta@home cpu time for the next two weeks please do--it will make a huge difference for our collective efforts!"

Well, it looks like there are people desperately needing your crunchin'.. mighte be developing DC-apps to better investigate the way your (and your relatives and friends') proteins fold and make you (and your relatives and frineds) either healthy or (badly) ill is not as worthwhile and attarctive as developing the right tuning for some superconductive electromagnets driving hadrons around to inevstigate what the universe is, but a volunteer cruncher should be a generous person by definition.. so why not giving David a chance for next the 4 days nad let the LHC-hungries try to feed thir caches up with the few hadron-WU the CERN-people are releasing these days?

---

By the way, the LHC-alpha project has just some 141510 (!!!) WUs available for crunching... but account creation is disabled!
I hope not to be too much assertive, but it looks to me that having to do with the fundamenatals of the universe has somehow led the CERN-people to lose some common sense.. GIVE US GREEDY CRUNCHERS THOSE BLOODY ALPHA-WUs!!!!!

---

Oops, I just forgot something:
;)

---

If I remember correctly: LHC Alpha uses the same old WUs again and again to test apps in state of development. I guess this projekt is on autopilot.

And now something commpletly different:
One of the mainproblems with Garfield is the lack ob a dedicaded Admin, so we have to wait again.

I do not think the problem lies with the user caching the workunits. This can be easily solved by the project adjusting the deadlines as appropriate....

Ok, I have to admit I get confused easily; but, if there is no problem why does it have to be solved?

---

I am a Geek. We surf in the dark web pages no others will enter.
We stand on the router and no one may pass.
We live for the Web. We die for the Web.