|
|
|
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
|
|
|
Message ID: 3260
Entry time: 06 Aug 2026
In reply to: 3259
|
| Author: |
Konstantin Olchanski |
| Topic: |
Suggestion |
| Subject: |
Multithreaded PySequencer |
|
|
> > > I was wondering if one can use multiple pysequencers at the same time and if not
> > > if this feature is planned in the future? Our experiment (mu3e) has one frontend
> > > per detector and each sequencer would only access a subset of ODB entries.
> >
> > I believe sequencer design supports this, same as mlogger supports multiple output
> > files and mhttpd supports multiple listener ports.
> >
> > But how to do this with pysequencer, I am not sure. Simplest is to wait a few more
> > weeks for Ben to return from vacation.
> >
> > K.O.
>
> I looked into this, and it has been possible for at least a year. Just start the sequencer with `-c MyUniqueName` and
> then all of the state etc. can be controlled from the ODB location `/PySequencerMyUniqueName/`.
> And obviously use different names for each instance.
that's what I remember, too. but was not sure. K.O. |