Repository navigation
probelms with DT and chromaticity calculations on ACCML #43
Description
my attempt at running
apptainer run oras://registry.hzdr.de/digital-twins-for-accelerators/containers/pyat-softioc-digital-twin:default-v0-5-1-bessy.2711893
which results with a lot of errors.
I have tried the SOLEIL apptainer and it responded well,so one can finally open the ATK gui.
2026-02-02T17:22:52.043147829 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:58312 Protocol decode fault. Force disconnect.
2026-02-02T17:22:52.044646990 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58336 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-02T17:22:52.045431375 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:58352 Protocol decode fault. Force disconnect.
2026-02-02T17:22:52.047177072 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58366 closed with socket error 104 : Connection reset by peer
executor.join(1)
File "/twin/python/venv/lib/python3.12/site-packages/pymongo/periodic_executor.py", line 211, in join
self._thread.join(timeout)
File "/usr/lib/python3.12/threading.py", line 1151, in join
self._wait_for_tstate_lock(timeout=max(timeout, 0))
File "/usr/lib/python3.12/threading.py", line 1167, in _wait_for_tstate_lock
if lock.acquire(block, timeout):
0000 : 00000114 FFFFFFFF
2026-02-02T17:22:52.048451840 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:58380 Protocol decode fault. Force disconnect.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyboardInterrupt:
2026-02-02T17:22:52.050737317 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58400 closed with socket error 104 : Connection reset by peer
2026-02-02T17:22:52.052018973 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58414 closed with socket error 104 : Connection reset by peer
2026-02-02T17:22:52.052937974 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58428 closed with socket error 104 : Connection reset by peer
2026-02-02T17:22:52.053977638 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:58434 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-02T17:22:52.055511582 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:58438 Protocol decode fault. Force disconnect.
Another thing is that I would like to run bessy2-chroma.py, but I have some errors. Any hint welcome
(pyat_conda) [marapo@accdev-0 BESSY2_example]$ python bessy2-chroma.py
02 Feb% 2026, 17:47:44 | WARNING | PyAML OA control system binding (0.1.1) initialized with name 'live' and prefix='a3744:'
Traceback (most recent call last):
File "/home/marapo/.conda/envs/pyat_conda/lib/python3.11/site-packages/ophyd_async/epics/core/_signal.py", line 52, in
from ._aioca import CaSignalBackend
File "/home/marapo/.conda/envs/pyat_conda/lib/python3.11/site-packages/ophyd_async/epics/core/_aioca.py", line 11, in
from aioca import (
ModuleNotFoundError: No module named 'aioca'
Activity
PierreSchnizer commentedon Feb 3, 2026
I think you need to install the module aioca
python3 -m pip install aioca
PierreSchnizer commentedon Feb 3, 2026
Background:
EPICS provides 2 transport layers
There different python packages providing implementation of the protocol
TL:DR: please install aioca and p4p. Please check the installation ends up in the environment used
marlibgin2 commentedon Feb 3, 2026
PierreSchnizer commentedon Feb 3, 2026
please could you show me the full back trace?
PierreSchnizer commentedon Feb 3, 2026
No there should be no need to restart the digital twin
marlibgin2 commentedon Feb 3, 2026
Hi Pierre, backtrace of the errors.
/gpfs/offline1/staff/common/marapo/pyAML_WORKSHOP_2026/accml/src
[marapo@accdev-0 src]$ apptainer run oras://registry.hzdr.de/digital-twins-for-accelerators/containers/pyat-softioc-digital-twin:default-v0-5-1-bessy.2711893
INFO: Downloading oras image
254.9MiB / 254.9MiB [======================================================================================] 100 % 3.4 MiB/s 0s
Environment variable MONGODB_URL is not defined, using default: mongodb://localhost:27017/bessyii
2026-02-03 12:16:27,629 - WARNING - Environment variable MONGODB_URL is not defined, using default: mongodb://localhost:27017/bessyii
WARNING:dt4acc:Environment variable MONGODB_URL is not defined, using default: mongodb://localhost:27017/bessyii
matplotlib is unavailable => plotting is disabled.
To enable plotting functions, run "pip install matplotlib".
Environment variable MONGODB_URL is not defined, using default: mongodb://localhost:27017/bessyii
/twin/python/venv/lib/python3.12/site-packages/pydantic/_internal/_config.py:383: UserWarning: Valid config keys have changed in V2:
warnings.warn(message, UserWarning)
2026-02-03 12:16:32,045 - INFO - Starting Twiss calculation (get_optics)
INFO:dt4acc:Starting Twiss calculation (get_optics)
2026-02-03 12:16:32,323 - INFO - Starting orbit calculation (find_orbit)
INFO:dt4acc:Starting orbit calculation (find_orbit)
2026-02-03 12:16:32,359 - WARNING - AcceleratorManager initialized successfully.
WARNING:dt4acc:AcceleratorManager initialized successfully.
Python 3.12.3 (main, Jan 8 2026, 11:30:50) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
EPICS 7.0.10.1-DEV
Rev. 7.0.10.99.0.0
Rev. Date 7.0.10.99.0.0
############################################################################
iocRun: All initialization complete
2026-02-03 12:16:34,380 - WARNING - VS3P2T5R:set_current updating setpoint val=0.001
WARNING:dt4acc:VS3P2T5R:set_current updating setpoint val=0.001
2026-02-03 12:16:34,385 - WARNING - VS3P2T5R:set_current updating setpoint val=0.0
WARNING:dt4acc:VS3P2T5R:set_current updating setpoint val=0.0
2026-02-03 12:16:34,389 - WARNING - Heartbeat loop initial start or it was terminated unexpectedly. Restarting...
WARNING:dt4acc:Heartbeat loop initial start or it was terminated unexpectedly. Restarting...
2026-02-03 12:16:34,389 - INFO - Heart beat loop executing at 2026-02-03 12:16:34.389183
INFO:dt4acc:Heart beat loop executing at 2026-02-03 12:16:34.389183
2026-02-03 12:16:34,489 - INFO - Starting orbit calculation (find_orbit)
INFO:dt4acc:Starting orbit calculation (find_orbit)
2026-02-03 12:16:34,535 - WARNING - CalculationResultView Orbit pushing view orbit result is none ? False
WARNING:dt4acc:CalculationResultView Orbit pushing view orbit result is none ? False
2026-02-03 12:16:34,536 - INFO - Starting Twiss calculation (get_optics)
INFO:dt4acc:Starting Twiss calculation (get_optics)
2026-02-03 12:16:34,784 - INFO - Orbit pushed view
INFO:dt4acc:Orbit pushed view
2026-02-03T12:16:34.814804300 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45902 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.816328446 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45906 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.818705949 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45932 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.819661860 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45946 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.821740350 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45974 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.822741239 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:45980 Protocol decode fault. Force disconnect.
2026-02-03T12:16:34.829697601 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:45998 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.830771384 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46012 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.832360437 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46026 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.833327719 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46034 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.834951442 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46064 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.835723788 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46066 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.837110109 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46096 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.837981971 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46102 Protocol decode fault. Force disconnect.
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.840276484 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46122 Protocol decode fault. Force disconnect.
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.840363608 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46124 Protocol decode fault. Force disconnect.
2026-02-03T12:16:34.842184230 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46148 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.843253387 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46160 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.843769932 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46170 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.845227535 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46178 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.845989485 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46190 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.847472848 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46202 Protocol decode fault. Force disconnect.
2026-02-03T12:16:34.848620484 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46216 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.850203106 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46236 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.851842324 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46246 Protocol decode fault. Force disconnect.
2026-02-03 12:16:34,853 - WARNING - Pushed bpm / orbit data
WARNING:dt4acc:Pushed bpm / orbit data
2026-02-03T12:16:34.859369250 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46270 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.860399282 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46284 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.862197176 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46288 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.863134893 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46304 Protocol decode fault. Force disconnect.
2026-02-03T12:16:34.864477345 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46318 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.865444096 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46322 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.884242642 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46336 closed with socket error 104 : Connection reset by peer
0000 : 00000114 FFFFFFFF
2026-02-03T12:16:34.885031868 ERR pvxs.tcp.io Client [::ffff:127.0.0.1]:46344 Protocol decode fault. Force disconnect.
2026-02-03T12:16:34.887938264 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46368 closed with socket error 104 : Connection reset by peer
2026-02-03T12:16:34.890767793 ERR pvxs.tcp.io connection to Client [::ffff:127.0.0.1]:46384 closed with socket error 104 : Connection reset by peer
KeyboardInterrupt
PierreSchnizer commentedon Feb 3, 2026
I see that the bessyii twin is running. I assume that you started in a separate shell
PierreSchnizer commentedon Feb 3, 2026
Now I get to it slowely ...
I reckon that there is some name mismatch of an involved process variable.
Normally what I do:
from epics tools (e.g. available in a container at registry.hzdr.de/digital-twins-for-accelerators/epics-tools:latest)
I would use
There you can then see all the (EPICS) process variables that the twin provides.
Now one needs to understand which request is made. I come to that in a second
marlibgin2 commentedon Feb 3, 2026
Well yesterday I have launched to apptainers from different shells, following the instuctions given in the workshop website
How can you check that the bessyii twin is running? Which one of the two cases you refer to? For me case (1) never worked properly, producing an avalanche of error messages.
marlibgin2 commentedon Feb 3, 2026
PierreSchnizer commentedon Feb 3, 2026
I'd assume you have a firewall running on your machine which stops any EPICS communication
I had the same problem on my machine.
Thus IT support disabled the firewall on my machine
marlibgin2 commentedon Feb 3, 2026
PierreSchnizer commentedon Feb 3, 2026
Do you have nc, ncat or netcat installed ? If not, it is contained in the epics tools container.
This would allow verifying if that is the case.
Then one could start a server on 5064 TCP and see if one can connect to it:
In EPICS, the standard/default ports are:
Channel Access (CA)
PVAccess (PVA) (EPICS V4 / V7)
marlibgin2 commentedon Feb 3, 2026
marlibgin2 commentedon Feb 3, 2026
PierreSchnizer commentedon Feb 3, 2026
You will need 2 terminals (or shells)
In the first one start a server:
In the second one send something as client:
marlibgin2 commentedon Feb 3, 2026
TeresiaOlsson commentedon Feb 3, 2026
This is interesting because we don't see the same issue on our Athena cluster. But maybe our setup is different or the way we connect to it.