-
Notifications
You must be signed in to change notification settings - Fork 0
Dependent development
This page aims to list the areas outside drunc where code development is needed to make drunc better and simpler.
Nobody likes to specify ports everywhere. We could make controllers and DAQ applications advertise their dynamically allocated control ports to the connectivity server and remove all the shenanigans of port offsetting.
drunc now uses its own broadcast messages and Kafka hook to broadcast what is happening to it. It would be better to use the ERS's Python binding to do that, although I am increasingly starting to think that the way it is now is an acceptable solution too.
The DUNE-DAQ applications do not know anything about their state. This makes the run control essentially "blind" to the state of the applications. We know that if commands are successful or not, and that is about it.
It would be nice if the DUNE-DAQ applications used the same command hooks as controllers. This would simplify greatly the controller code.