LHC@home

I have a Theory task (Theory_2922-4905151-252_1) that has now been running for over 6d, 5.5 hr.

Latest Windows 10, on an older machine. The BOINC app is "301.00 (vbox64_theory)".

BoincTasks shows the task taking around 45% CPU, so it's apparently still going. Another Theory task (same application) that is still in progress shows in the BOINC Manager a total elapsed/remaining runtime of about 3.5 hours, which is a pretty huge difference.

Is all this expected? Should I be concerned about this 6+ day task?

Thanks.

doug

Is all this expected? Should I be concerned about this 6+ day task?

no, don't be concerned. The lengh of Theory tasks varies to a high extent (recently I had one which ran about 16 days, and also before my machines received rather long tasks at times).
With the LHC tasks, the progess and time indications from the BOINC manager don't tell a thing.
However, for Theory tasks, you can click on the "Graphics" button in the left hand part of the BOINC Manager, then a Browser window opens, there you click on "logs", and then on "running log" - this shows the progress of the task

To add to Erich56's reply:
On the first line of that running.log you'll find something like ===> [runRivet] Thu Sep 25 02:13:29 PM UTC 2025 [boinc pp jets 13000 25 - pythia8 8.244 CP2-CR1 100000 282]
The forelast number (mostly 100000) is the number of events to be processed.
Go to the end of the running log to find how many events are processed so far.

Of course at first: Is the task using cpu-cycles?

Some of them run up to 10 days.
Locate the runRivet.log in ...\slots\x\shared\ and check it's "last modified" timestamp.
If that is older than a day the task most likely got stuck and you should cancel it.

If the log gets updated at least every now and then check it's content for the newest "nnn events processed" lines.
Tasks usually process 100000 events, so you can estimate the time left.

BOINC can't do this as it doesn't know where it can find those numbers.

Thanks all. You've set my mind at ease.

Following Crystal Pellet's instructions, I found this:

===> [runRivet] Thu Sep 25 01:55:56 PM UTC 2025 [boinc ppbar jets 1960 37 - pythia8 8.230 tune-4c 100000 282]

Following Erich56's instructions, I found this:

Pythia::next(): 49000 events have been generated
49000 events processed
49100 events processed
49200 events processed
49300 events processed
49400 events processed
49500 events processed
49600 events processed
49700 events processed

So apparently only HALF done after well over 6 days!

Also, BoincTasks shows the task taking around 45% CPU, so I was pretty sure the task was still alive in some way or other.

Finally, the timedate stamp on the file mentioned by computezrmle was updated in the last few minutes.

Thanks to all of you!

doug

Also, BoincTasks shows the task taking around 45% CPU, so I was pretty sure the task was still alive in some way or other.

From another Theory task of yours:

Run time 5 hours 0 min 11 sec
CPU time 2 hours 15 min

You should find the reason that your tasks are running < 50% CPU
Maybe something in your BOINC settings, if that is not the intention.

I have had many long Valid Theory's over the years but I always watch the running logs since you can get a Sherpa that will run 10 days and fail
( I save stuff) here is one from last June
Run time 8 days 18 hours 41 min 28 sec
CPU time 8 days 17 hours 14 min 35 sec
Validate state Valid
Credit 7,539.68
and many others but you can always abort if you want to run another project

Also, BoincTasks shows the task taking around 45% CPU, so I was pretty sure the task was still alive in some way or other.

From another Theory task of yours:

Run time 5 hours 0 min 11 sec
CPU time 2 hours 15 min

You should find the reasom that your tasks are running < 50% CPU
Maybe something in your BOINC settings, if that is not the intention.

The reason can be found in stderr.txt:

Setting CPU throttle for VM. (40%)

@doug
For vbox apps it is not recommended to throttle the CPU via BOINC's computing preferences since it may cause timing issues.
Instead, leave it at 100 % and limit the # CPUs via <ncpus>N</ncpus> in cc_config.xml.

.... Instead, leave it at 100 % and limit the # CPUs via <ncpus>N</ncpus> in cc_config.xml.

.... or in BoincTasks -> Menu Extra -> BOINC Preference -> On multiprocessor systems, use at most ...... % of the processors