LHC@home

Just a quick list I'd like to see happen with LHC prior to them going into 'production'.

1. WU Completion Estimate. I'd like to see this set as a little more realistic than what it currently is. I know the next release of BOINC starts to address this issue, but so far it is way off and it would be nice if it was a little closer to reality.

2. WU granted credit is more consistent. There is currently a huge difference between the amount of credit that a linux host and a windows host claim. Is this something that LHC can address or is this an overall BOINC issue? I know of people who do not do certain projects due to the perceived unfairness of the credit system.

I'll add to this as they hit me.

Live long and crunch.

---

Paul
(S@H1 8888)
BOINC/SAH BETA

> Just a quick list I'd like to see happen with LHC prior to them going into
> 'production'.
>
> 1. WU Completion Estimate. I'd like to see this set as a little more
> realistic than what it currently is. I know the next release of BOINC starts
> to address this issue, but so far it is way off and it would be nice if it was
> a little closer to reality.
>
> 2. WU granted credit is more consistent. There is currently a huge
> difference between the amount of credit that a linux host and a windows host
> claim. Is this something that LHC can address or is this an overall BOINC
> issue? I know of people who do not do certain projects due to the perceived
> unfairness of the credit system.
>


funny.. your wishes match my wish list as well

But I'm still hoping for a 64 bit version of the Windows Sixtrack client (call it wish #3)

---

I think one wish has been granted, was just checking my time to comp on Boincview for LHC and it has 10:49:41 and Boinc ver 4.70 has it at 6:15:33, so me thinks it is working.......

---

BOINC Wiki

Let me start from the bottom.

#3
What is the problem with the 64 bit version? are you unable to get work?

#2
The credit issue is a general boinc issue there is no way we can affect how a client claims credit.

#1
There are a couple of issues with the work time estimates:
1. We estimate how many flops a WU is going to need. The time estimate is then calculated from the boinc benchmark.
2. We stop calculating as soon as the particles are lost. It is impossible to predict when this will happen, which is why we need to do the calculations in the first place. This means that we will often over estimate the run time of a WU.

The new client should, hopefully, address these problems.

---

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

LHC is now at 5:40.26

---

BOINC Wiki

#4 a project member on my editing staff that can add LHC@Home information to the Wiki ...

p.d.buck@comcast.net

Just thought I would add that one ... :)

---

#5 Please post some info as to what the current WUs are simulating.

Michael

---

Team Linux Users Everywhere

>
> #3
> What is the problem with the 64 bit version? are you unable to get work?
>
is there a 64 bit sixtrak client? did I really miss that?

---

#5

Would it be possible to use smaller WU naming?

11.07.2005 23:46:14|LHC@home|Starting result wjun1B_v6s4hvnom_mqx__6__64.27_59.28__4_6__6__25_1_sixvf_boinc7146_1 using sixtrack version 4.67

when using a GUI, it takes nearly the double space as WU naming from other projects.
It's not so important but would be nice

the long names also uses much more "space" in the various logs

#7 - (I think one of the #5's should be #6) - I seem to remember reading somewhere that the graphics were just showing a canned simulation that had nothing to do with the WU data being crunched. If this is indeed true, would it be possible to make the graphics relate in some way to the data? How about making the number of particles in the graphics track the real number being crunched?

---

Hi folks

If this is a wish list.

#8 - I would like like to see the atoms smash into to something at the end.

Why not

You could even simulate the path the resultant particals take.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=2104" />

#0 - more work ...

Oh, we do have more work ... sorry ... I will be quiet now ...

---