LHC@home

I got a couple of v64boince WU a few hours ago.
I checked my message log and have been working on
v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
It has been paused twice and apparently it has a similar problem to the old LHC WU. It reset to 0% and 0 CPU time when it is restarted.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

> I got a couple of v64boince WU a few hours ago.
> I checked my message log and have been working on
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> It has been paused twice and apparently it has a similar problem to the old
> LHC WU. It reset to 0% and 0 CPU time when it is restarted.
>
>
>
@ Aurora Borealis
From which WU do you talk about? Please copy/paste the WU ID or the Link.
And 4.64 are 'old' WU's; the 'new ones' call: 4.66.

I didn't see any in your resultstable from today an yesterday (8/9.April)!
(you didn't report it yet)

greetz littleBouncer

---

> From which WU do you talk about? Please copy/paste the WU ID or the Link.
> And 4.64 are 'old' WU's; the 'new ones' call: 4.66.
>
> I didn't see any in your resultstable from today an yesterday (8/9.April)!
> (you didn't report it yet)
>
> greetz littleBouncer
>
It's hard to report a WU that keeps resetting at O% processed. I now need to suspend all my other projects to allow this one to be completed. I will be doing so now and will post again, in four to six hr, when I have completed a WU.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

I just reported 2 WU's that took about 11 hours each and they showed 0:00:00 Time, they were the 4.64 applications ... Here's one of WU's ... I'm host 30594 ... I've had numerous other ones with the 4.64 application show 0:00:00 time also on my other Computers ...

I have one as well, this one. It has been crunching all night and has reset a couple of times, starting from scratch. I hope to have it finished in a few hours though (crossing fingers ;-)).

---

My first WU with the new app 4.66 seems to checkpoint ok.
I shutdown boinc to defrag my harddrive and when I restarted it continued from the 10% it reached before the shutdown. All seems fine so far.

This is the WU
I'm host 21859.

---

No, I can't finish any LHC units on this computer, since it constantly restarts due to faulty hardware (I think). I've been through 4 wus now that resume at 0%. Any chance this will get fixed? I now it worked before.

After several hours of processing,
v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
I had to reboot my computer, and reluctantly decided to abort it.
The second WU
v64boince6ib1-25s14_16615_1_sixvf_1069_0 using sixtrack version 4.64
completed successfully in only a few minutes.
I am now processing
v64boince6ib1b-37s14_16630_1_sixvf_28681_1 using sixtrack version 4.66
it seems to pauses and restarts properly.

edit:: The above just completed. I had just checked it and it was at 15% a few seconds later it was finished. Successfully !!! I have my doubts.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

> After several hours of processing,
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> I had to reboot my computer, and reluctantly decided to abort it.
-----
For this : I have no explain yet. There is a lot to tell about, but as 4.64 will be gone soon, it isn't worth to open a new 'construction site'...

> The second WU
> v64boince6ib1-25s14_16615_1_sixvf_1069_0 using sixtrack version 4.64
> completed successfully in only a few minutes.
> I am now processing
> v64boince6ib1b-37s14_16630_1_sixvf_28681_1 using sixtrack version 4.66
> it seems to pauses and restarts properly.
-----
This two WU's are 's14_' and will take 10 min. (average) or about 1.38889% of the time which a 's6_' will take.
So for me the behaviour was 'normal' .

>
> edit:: The above just completed. I had just checked it and it was at 15% a few
> seconds later it was finished. Successfully !!! I have my doubts.
>
-----
Don't doubt! It will work, let your client play....;-)
greetz littleBouncer

---

> I got a couple of v64boince WU a few hours ago.
> I checked my message log and have been working on
> v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> It has been paused twice and apparently it has a similar problem to the old
> LHC WU. It reset to 0% and 0 CPU time when it is restarted.
>
i have the same problem on at least 4 computers.
all intel/winxp/sixtrack4.64
after every switch between projects the lhc@home wu's restart at 0%.
this way i never get any work done and lhc@home is wasting my donated time.

resetting these computers makes no difference.
i am not going to stop the other projects i am donating too, to resolve this problem.

can i just delete the lhc wu's and hope to get wu's that do work?

---

> > I got a couple of v64boince WU a few hours ago.
> > I checked my message log and have been working on
> > v64boince6ib1-25s8_10630_1_sixvf_1055_4 using sixtrack version 4.64
> > It has been paused twice and apparently it has a similar problem to the
> old
> > LHC WU. It reset to 0% and 0 CPU time when it is restarted.
> >
> i have the same problem on at least 4 computers.
> all intel/winxp/sixtrack4.64
> after every switch between projects the lhc@home wu's restart at 0%.
> this way i never get any work done and lhc@home is wasting my donated time.
>
> resetting these computers makes no difference.
> i am not going to stop the other projects i am donating too, to resolve this
> problem.
>
> can i just delete the LHC wu's and hope to get wu's that do work?

If you use Boinc V4.2x you can abort individual WU by highlighting them in the Work tab and selecting Abort result in the tasks window. Other than that you could detach from the project, that would kill all the WU.
I am not sure what file you need to delete to make WU error out.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

> If you use Boinc V4.2x you can abort individual WU by highlighting them in the
> Work tab and selecting Abort result in the tasks window. Other than that you
> could detach from the project, that would kill all the WU.
> I am not sure what file you need to delete to make WU error out.
>
@ aurora borealis: thank you for your answer. i did not know there was a new boinc version.
maybe the boinc people could find a way to let us know???

i will try your solution.

i see in the lhc download section only version 4.19, which i was using.
i am now running boinc 4.25. let's see what happens now.....

and some time later i see the problem still is there.
as usual there is no info from lhc. so i am going to abort results.

---

I have processed a few of the new work units and they vary in time from 2 to 35 minutes.

---

> I have processed a few of the new work units and they vary in time from 2 to
> 35 minutes.
>
Different WU have various processing time.
The S## is your clue. The smaller number seem to take longer.
e.g.
v64boince6ib1b-37s14 was only 17 min
v64boince6ib1b-38s12 was 1 hr
currently processing
v64boince6ib1b-41s8 already over 3hr

Boinc V4.27 alpha

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

I just discovered this: If you let units stay in memory when suspended, they won't restart after having been suspended. Strangely enough, they also continue after the machine has been restarted.
The setting is found under "Your Account" -> "General Preferences" -> "Leave applications in memory while preempted?".

Hope this helps you, it certainly helped me.

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.
-----
It helps!

I forgot to suggest it, sorry
greetz littleBouncer

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.

Now I understand why I didn't have this problem. I turned this setting on, when I read somwhere, that CPDN backs 170TS on restart if app. isn't preempted.

Happy crunching,

---

> when I read somwhere, that CPDN backs 170TS on restart if app. isn't

Actually, UP TO 144 TS.

Has anyone bothered to find out how often a checkpoint is in LHC WUs? (or has admin said it somewhere?)

Also if Aurora Borealis kept having the entire WU reset to 0, might there be a long time between each checkpoint or are his BOINC timeslices really short?

---

> I just discovered this: If you let units stay in memory when suspended, they
> won't restart after having been suspended. Strangely enough, they also
> continue after the machine has been restarted.
> The setting is found under "Your Account" -> "General Preferences" ->
> "Leave applications in memory while preempted?".
>
> Hope this helps you, it certainly helped me.
>
I forgot to mention this.... because it causes other problems with Windows 98.
You end up with several projects apparently running at the same time, and getting very long crunch time to nowhere. I think youre OK with other OS.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

When we checkpoint depends on the specific study and sixtrack version, but i believe it is about every 1000 turns.

BUT!!! We only checkpoint if the boinc_time_to_checkpoint() function returns true.
This function is there to limit how often we write to disk, so that people on laptops, for example, can save power.

How often we can checkpoint is therefore something that you can limit in your preferences.

---

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