|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
07 Jul 2026, Marius Koeppel, Suggestion, Multithreaded PySequencer
|
08 Jul 2026, Konstantin Olchanski, Suggestion, Multithreaded PySequencer
|
03 Aug 2026, Mark Grimes, Suggestion, Multithreaded PySequencer
|
06 Aug 2026, Konstantin Olchanski, Suggestion, Multithreaded PySequencer
|
06 Oct 2026, Marius Koeppel, Suggestion, Multithreaded PySequencer
|
06 Oct 2026, Ben Smith, Suggestion, Multithreaded PySequencer
|
|
|
Message ID: 3284
Entry time: 06 Oct 2026
In reply to: 3283
|
| Author: |
Ben Smith |
| Topic: |
Suggestion |
| Subject: |
Multithreaded PySequencer |
|
|
> I looked into this now and it seems to work but the issue is that even when using only one sequencer with -c MyUniqueName
> the page does not work anymore. We tried to create our own custom page for this now but maybe a nice addition would be to
> simply change the custom page to also support multiple sequencers.
The sequencer webpage does support multiple sequencers (and that's how it supports both the original sequencer and the python-
based sequencer). The choice of sequencer is based on the `SeqODB` URL parameter.
To create a link that will show up in the menu, create an entry in `/Alias` in the ODB.
e.g. for original sequencer:
odbedit -c "create string '/Alias/My new sequencer'"
odbedit -c "set '/Alias/My new sequencer' '?cmd=Sequencer&SeqODB=/SequencerMyUniqueName'"
e.g. for pysequencer:
odbedit -c "create string '/Alias/My new pysequencer'"
odbedit -c "set '/Alias/My new pysequencer' '?cmd=Sequencer&SeqODB=/PySequencerMyUniqueName'"
You can of course create this entry using the ODB web interface instead. |