Application
Theory Simulation 302.00 (docker)
Name
Theory_2922-4889256-482
State
Running
Received
2/2/2026 8:43:40 AM
Report deadline
2/12/2026 8:43:40 AM
Estimated computation size
3,600 GFLOPs
CPU time
08:14:14
CPU time since checkpoint
08:14:14
Elapsed time
08:33:58
Estimated time remaining
---
Fraction done
100.000%
Virtual memory size
2.26 MB
Working set size
337.27 MB
Directory
slots/14
Process ID
15668
Progress rate
11.520% per hour
Executable
docker_wrapper_17_windows_x86_64.exe
Application Name
Theory
Plan Class
docker

---

Theory docker tasks don't survive a PC-shutdown and will restart from the beginning after PC and BOINC restart.

Task sits at 100 percent for many hours before shutdown...

---

Theory tasks are a mixed bag of runtimes. 1 hour to 6days (even 10day tasks sometimes) is normal.

Boinc manager has no idea what is happening inside the virtualbox or docker container. So the % shown there is not relevant.

You may show the progress when using "Show Graphics" from BOINC Manager.
Highlight the running task and press the "Show Graphics" button. A local webpage will popup. Press the Logs link and then the running.log.
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6438&postid=52989

Some tasks have a first step with "217 of 760 integrations done" or the second step that have all tasks that is counting up to "100k events processed'

Hmmm. I've got one of these: initial estimated time 6 hours.
It got to 100% and has been sitting there like that for a over a day.

It won't allow me to Show Graphics - button is greyed out.

Properties says this:

Application
Theory Simulation 302.00 (docker)
Name
Theory_2922-4762162-608
State
Running
Received
11/02/2026 01:56:43
Report deadline
21/02/2026 01:56:41
Estimated computation size
3,600 GFLOPs
CPU time
22:54:46
CPU time since checkpoint
22:54:46
Elapsed time
1d 01:02:23
Estimated time remaining
---
Fraction done
100.000%
Virtual memory size
2.37 MB
Working set size
609.76 MB
Directory
slots/0
Process ID
11000
Progress rate
3.960% per hour
Executable
docker_wrapper_17_windows_x86_64.exe
Application Name
Theory
Plan Class
docker


If I go onto the web and click for info on the WorkUnit I get this:
The bold bits are what I am questioning:

Name Theory_2922-4762162-608_0
Workunit 239073517
Created 10 Feb 2026, 12:01:02 UTC
Sent 11 Feb 2026, 0:56:41 UTC
Report deadline 22 Feb 2026, 0:56:41 UTC
Received ---
Server state In progress
Outcome ---
Client state New
Exit status 0 (0x00000000)
Computer ID 10842933
Run time 0 sec
CPU time 0 sec
Priority 0
Validate state Initial
Credit 0.00
Device peak FLOPS 3.96 GFLOPS
Application version Theory Simulation v302.00 (docker)
windows_x86_64

So - advice is to leave it... ? Right? I don't normally turn my laptop off, so I can leave it running if it is doing something useful....[/img]

In reply to The Real Weasle's message of 12 Feb 2026:

Hmmm. I've got one of these: initial estimated time 6 hours.
It got to 100% and has been sitting there like that for a over a day.

It won't allow me to Show Graphics - button is greyed out.
..
..
..
So - advice is to leave it... ? Right? I don't normally turn my laptop off, so I can leave it running if it is doing something useful....

Yeah, Advice is ... let it run.
Theory tasks can run from 5 minutes to over 10 days, so don't look at the % done or remaining time. That's of no use.

The Show Graphics button is only available for VBox-tasks, not for the docker version.

I see your task is running in slot 0
In that slot is a folder named 'shared'.
In the shared folder is a file called 'runRivet.log'.
The process running in the container is writing the progress of the event processing into that file.

Cool, thanks for that last tip about the runRivet.log file. At least there I can keep an eye on it.
Very useful.



In reply to Crystal Pellet's message of 12 Feb 2026:
Yeah, Advice is ... let it run.
Theory tasks can run from 5 minutes to over 10 days, so don't look at the % done or remaining time. That's of no use.

The Show Graphics button is only available for VBox-tasks, not for the docker version.

I see your task is running in slot 0
In that slot is a folder named 'shared'.
In the shared folder is a file called 'runRivet.log'.
The process running in the container is writing the progress of the event processing into that file.[/quote]