LHC@home

(french) Bonjour
j'ai 4 WU qui m'affichent 0 CPU après complétion. Comme les symptomes sont identiques au tristement célèbre bug, je préfère vous avertir.
Voici les unités incriminées -- je recopie à la main donc ya possibilité qu'il y ai une faute de frappe.
--------------------------

(english) Hello there. I have 4 WU that show 0 CPU time after completion -- since the symptoms are identical to the infamous 0 CPU time bug, I thought it'd be better to tell you.
Below is the WU's ID (handwritten, so there's a possibility of typo)
Using : sixtrack 4.67

v64diponlyinjniskew-22s18_20510.3846_1_sixvf_29235_4

v64diponlyinjniskew-22s18_20512.1154_1_sixvf_29236_1

v64diponlyinjniskew-22s18_20525.9615_1_sixvf_29244_1

v64diponlyinjniskew-22s18_20515.5769_1_sixvf_29238_1

Wolfgang "Darkoneko" ten Weges

edit/there's more now :
v64diponlyinjniskew-22s18_20513.8462_1_sixvf_29237_2

---

Did you read this thread???

(french)As-tu déjà lu cette poste???
Toutes tes results sont de s18_, ça veut dire: c'est possible qu'ils quitte très vite le colidier. Ces results n'ont rien a faire avec le 'real' 0-CPU-time problem.

greetz littleBouncer

[EDIT: 13:17 UTC]
I hope I was not too unfriendly....;-)
[/EDIT]

---

"They have a bigger amplitude at the beginn ('bang') of the simulation and could abort."
ok, so that's why... (well, I looked partly at the "'0 cpu' problem solved?", but since it started some weeks ago, I thought this was about the original problem)

---