LHC@home

I have gotten 3 new Tasks int he past 15 minutes and they all run for about 15~25 seconds and then the completion bar goes to 100% and they report. When I look at my Tasks they indicate Completed and waiting for validation.

Is there something wrong or is this what everybody is seeing?

I'm concerned about running too many Tasks and having them not validate then getting thrown out of the New Task queue.

If the work units finish very quickly there are two main reasons this could happen; The Work Unit has an error, or the particle beam the Work Unit is trying to simulate crashed into the wall and did not make a circuit round the LHC (or similar analogy).

When you are waiting for validation then the Work Unit was not in error but has finished for whatever reason, and is just waiting to see if the a second run by another computer confirms your results.

I don't believe you have anything to worry about. Mixed in with the short ones are much longer ones.

Conan

---

Yes; I am exploring phase space at rather high amplitudes
and I exoect all particles to be lost rtaher quickly at
these values. There are also cases which are much more stable
and will run longer. I am also comparing two different methods of
computing the beam-beam inetraction. Once I have identified
the more stable region there will be more longer cases to run.
Eric.

---

Out of 1142 tasks since June 25th batch, I still have 560 pending. Looks like 98% of the pending are the short 2-5 second tasks.

Me thinks there is a problem when half the tasks run short and we never get credit... not even 0.01 points for the download/upload bandwidth used...

LOL!

8-)

As an update, still got a few of the shorter tasks, but seems a lot more stable now running (typically) from 600 secs (10 min) to the absolute longest of 23,000 secs (6 hrs 22 min) on AMD 1100T/1090T systems running 1600MHz DDR3 @ 3.6GHz speed.

Looks like we got a winning batch here...

:)

Tasks I am getting now are running full length.

Thanks for that feedback. I am now running ba detailed
comparison of two beam beam algortithms in a region of
reasonable stability.

We are not out of trouble yet but I am preparing 3 executables for
Linux and 3 for Windows and a colleague is producing a MAC exeutable.
The 3 versions are
Run anywhere
Use SSE2
Use SSE3
Eric.

---

Tasks I am getting now are running full length.

Well, I spoke too soon. Tasks seem to be running very short. Indicated times are for 14~15 hours but they finish in about 30 minutes (or less). They do seem to validate okay and there is no error showing up.

Thanks for that feedback. I am now running ba detailed
comparison of two beam beam algortithms in a region of
reasonable stability.

We are not out of trouble yet but I am preparing 3 executables for
Linux and 3 for Windows and a colleague is producing a MAC exeutable.
The 3 versions are
Run anywhere
Use SSE2
Use SSE3
Eric.

How do you recognize the different versions? I have seen only executables named Sixtrack.exe, current version is 443.07. All my computers are SSE3 capable so how do I know it was detected right?

---

it say's 444.01 (sse3)

My Opteron 1210 at 1.8 GHz, SSE3 capable, is running a task which has taken 18+ hours to reach 44% on my Linux box. A wingman of mine with an AMD Phenom II running Windows has completed the task in two seconds. How is this possible? Is he using his Radeon HD 6900 graphic board?
Tullio

Seems like your task isn't the new AMD optimised tasks. It will take a while for you to complete this task or you could abort it and get the new ones.

when you report your task, it will be an inconclusive validation, and will be sent to a third host.

Probably some kind of error for this 2 second computation.

see this work unit for example.

No GPU computing in this project.

Filipe

---

What are the necessary conditions to get your CPU capabilities recognized correctly? My Vista 32 bit with Q9400 + Boinc 6.10.58 does not list the SSE3 support which CPU-Z recognizes. Boinc messages list sse2 and ssse3 though but LHC still sends me the standard version of sixtrack.exe (444.01). Same happens with Win XP 32 bit, T9500 + Boinc 6.10.43.

My Win7 64 bit laptop with i7 + Boinc 6.12.34 and Win xp64 with E5645 + Boinc 6.12.34 get the correct sse3 application although boinc does not list sse3 available on them either.

So you should have at least 6.12.34 to get the right application?

Edit: correct signature and avatar

---

Maybe your BOINC client is too old ?

Here is what I get on my i7 920 with 7.0.28 client :

04/07/2012 20:15:45 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm vmx tm2 popcnt pbe

My reports similar to toTOW.

I don't know how BOINC decides what tasks to send.

It doesn't seem like the version is the problem?

Maybe your BOINC client is too old ?

Here is what I get on my i7 920 with 7.0.28 client :

04/07/2012 20:15:45 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm vmx tm2 popcnt pbe

The message I see on my i7 is similar using boinc 6.12.34. And that gets the correct version of the application (sse3). Note that boinc detects ssse3 not sse3.

The Q9400 using boinc 6.10.58 gets this message:

Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 nx lm vmx smx tm2 pbe

and this computer gets only the standard version of sixtrack.exe.

And that is why I am asking what are the right conditions. Which OS and Boinc versions you should have to get it working right?

---

I always use the latest version of BOINC, I don't see any reason to not do that.

You said 6.12.x works fine so if you perfer an older vresion then upgrade to that?

Once you upgade to 7.x its tricky to drop back.