Skip to content

Lima: Display Lima processing in __info__

Valentin Valls requested to merge valentin.valls/bliss:lima-processing into master

This MR is a proposal to display the Lima processing as a workflow in the device info.


                  level   🌞  Source: Simulator
                          │
                          ∎  Internal: reconstruction, flip, binning, ROI
                          │
                         [∎] Internal: accumulation
                          |
                      0  [∎] diffsimulation             
                          |
                      0  [ ] flatfield                  Warning: A task is already available at this level
                          |
                      0  [ ] mask                       Warning: A task is already available at this level
                          |
                      0   ├─[ ] peakfinder              
                          |
                      2  [ ] backgroundsubstraction     
                          |
                     10   ├─[ ] roicounter              
                          |
                     10   ├─[ ] roi2spectrum            
                          │
                          🗑  Result

This allow to understand a bit better the way Lima process the data.

  • Fixed internal operation
  • The order of bin/flip/roi
  • Location of the plugins in the workflow
  • Sink or link plugins (peakfinder is a sink, while backgroundsubstraction is a link)
  • Enabled or not
  • Plus warnings in case of inconsistency (here we can see that diffsimulation and mask could be in conflict)

This displays the actual state of the work flow as exposed by Tango devices (and not the one enforced by BLISS at the prepare).

BLISS is using it's own way to setup the runlevel of some devices during the prepare (processing.runlevel_background). Anybody knows why? I don't understand why BLISS don't use Lima with it's current state.

Edited by Valentin Valls

Merge request reports