> > > > 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.

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.