Controller composition

I try to push composition in the BLISS ebs-tomo project.

To me it's a very important feature to be able to reuse complex part of a beamline configuration into another one. Because the main configuration will be isolated into a kind of business modelization.

It's true for ebs-tomo procedure but also for GUI configuration. And i don't want to setup twice the stuffs.

Working prototype

bliss

1. The tomo beamline will provide a TomoSampleStage controller, configured as sstomo2.
2. This controller be composed a bunch of motors by role (sx, sy, sz, somega)
   • Most of the time this devices are fixed (motor use case, sx is always the same)
   • Some controllers can be updated during a session (the actual detector can switch from det1 to det2 for example)
3. This main controller is synchronized between sessions (with channels)

daiquiri

4. A mapping have to be provided for this sample stage controller
5. We could type sub device properties (it is not down for now, i have only used a translator for now)
6. The subdevices are exposed as attributes from role to value: somega="hardware:srot"

daiquiri-ui

7. In hardware we can define bliss://sstomo2 (our sample stage object)
8. In layouts we can use sstomo2.somega
9. HardwareObject have to retrieve the right object from the name sstomo2.somega