|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
 |
|
01 Apr 2025, Lukas Gerritzen, Suggestion, Sequencer ODBSET feature requests
|
01 Apr 2025, Lukas Gerritzen, Suggestion, Sequencer ODBSET feature requests
|
01 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests
|
01 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests
|
01 Apr 2025, Konstantin Olchanski, Suggestion, Sequencer ODBSET feature requests
|
01 Apr 2025, Pavel Murat, Suggestion, Sequencer ODBSET feature requests
|
02 Apr 2025, Konstantin Olchanski, Suggestion, Sequencer ODBSET feature requests
|
02 Apr 2025, Stefan Ritt, Suggestion, Sequencer ODBSET feature requests
|
|
Message ID: 3025
Entry time: 02 Apr 2025
In reply to: 3024
|
Author: |
Stefan Ritt |
Topic: |
Suggestion |
Subject: |
Sequencer ODBSET feature requests |
|
|
And there is one more argument:
We have a Python expert in our development team who wrote already the Python-to-C bindings. That means when running a Python
script, we can already start/stop runs, write/read to the ODB etc. We only have to get the single stepping going which seems feasible to
me, since there are some libraries like inspect.currentframe() and traceback.extract_stack(). For single-stepping there are debug APIs
like debugpy. With Lua we really would have to start from scratch.
Stefan |