Development for LHC@home

This version has a new dependency and hopefully will result in less network traffic on startup.

In reply to Laurence CERN's message of 1 Jul 2025:

This version has a new dependency and hopefully will result in less network traffic on startup.

This newest Theory VBox version is running fine.
Also the files from the older previous Theory versions are cleaned up this time.

Maybe on purpose, but with the last versions 'Remote Desktop' gives no useful information anymore.

The only info you can fetch is from runRivet.log in the slot/shared map.
Here is a mini powershell script to track the progress of a task to adapt and expand for more machines and more and other slots.

Set-Executionpolicy -Scope CurrentUser -ExecutionPolicy ByPass
$LT1slot0 = "D:\boinc1\slots\0\shared\runRivet.log"
1..105120 | ForEach {
cls
if(Test-path $LT1slot0 -PathType leaf) {echo "==========================================================>> LT1 slot 0 <<=========================================================="
 Get-Content $LT1slot0 | Select-Object -First 1
 echo "===================================================================================================================================="
 Get-Content $LT1slot0 -tail 10
 echo ""}
Start-Sleep -m 10000}

Thanks for the feedback. Yes, the remote desktop is no longer supported. It is not really needed and there are licensing issues with requiring the extension pack to be installed. The graphics option should work and you can view files there. As you mentioned, the runRivet.log can be seen in the slot directory if you wish to monitor the running job.

I will put this in production.

I switched back and forth several times last weeks between this Theory VBox version and the Theory docker version.

My strong preference is the vbox version, because it runs much smoother on my Windows machine.
I use this laptop for daily activities and with the docker app using WSL the laplop is freezing for seconds more often.

In reply to Crystal Pellet's message of 14 Jul 2025:

My strong preference is the vbox version, because it runs much smoother on my Windows machine.
I use this laptop for daily activities and with the docker app using WSL the laplop is freezing for seconds more often.

Uh, that's strange.
On both my Windows machines, Docker is clearly better than vbox version....

In reply to boboviz's message of 14 Jul 2025:

Uh, that's strange.
On both my Windows machines, Docker is clearly better than vbox version....

Have also no problems with Docker so far.

In reply to boboviz's message of 14 Jul 2025:

In reply to Crystal Pellet's message of 14 Jul 2025:

My strong preference is the vbox version, because it runs much smoother on my Windows machine.
I use this laptop for daily activities and with the docker app using WSL the laplop is freezing for seconds more often.

Uh, that's strange.
On both my Windows machines, Docker is clearly better than vbox version....

It's a laptop with 16 GB RAM and the processor is a meanwhile outdated i5-6200U. The bottleneck could be that it has only two real cores feeding 4 threads.
I already reduced the max RAM for WSL Ubuntu to 4,108GB in stead of taking its default of 8GB.
Windows vmmem.exe seems to be very aggressive for claiming the processor. 1 task uses 32% of the CPU in stead of 25% even when reducing the process priority to 'below normal'.
During the startup/initializing phase of a Theory job sometimes over 2GB of RAM is used.