4th BLISS Steering Committee meeting

Beamline Instrumentation Support Software

13/9/2019

4th BLISS Steering Committee meeting

Braving the road, going full-throttle

Situation to avoid... >

Activity since last meeting

 

  • Offset display for `wm`, `wa` standard functions (#853)
  • Race condition with metadata info writing at end of scan (#888)
  • Keithley device controller fix (#883)
  • Lakeshore temperature controllers refactoring (#629)
  • Take `display_unit` into account for Tango counters (#882)
  • Warning displayed for configuration items without plugin (#893)
  • Pseudo (calc) motor limits check before move (#471)
  • user info property handling for all BLISS objects (#923)
  • standard relative scans cleanup fix (#928)
  • prevent multiple shells with identical sessions to run at the same time (#793)
  • default, standard scans to take number of intervals not number of points (#931)

Data from commits history

Bugs fixing 44%

Refactoring

13%

Documentation

13%

New features

16%

C.I.

6%

Devices

4%

Activity since last meeting

Feature highlight: sampling counter modes (#832)

Possibility to select statistics to get from sampling counters

Default mode

+ `SAMPLES` mode: adds a 1D dataset with all acquired values (for diagnostic)

+ `STATS` mode: gives std deviation, min, max, PV, etc.

Activity since last meeting

Improvements to Flint, BLISS data display tool

Meeting organised by Valentin Valls on 2/9/2019 (minutes)

Use cases

Development plan

Follow-up on continuous scan toolbox

  • to rely on existing BLISS scanning engine
  • need to be as generic as possible
    • blocking points have been identified
  • BLISS components are not always written the same way
    • need to be made uniform
  • top-priority item now

Meeting held with BLISS team + E. Papillon, G. Berruyer (#978)

Goal : to provide a "toolbox" (= helper functions) to be able to create optimized acquisition chains for any continuous scan

Follow-up on data saving

Wout de Nolf (DAU) has a working prototype of external data saving (cf. previous Steering Committee meeting) for ID21

Issues

  • Virtual Datasets support
    • need h5py upgrade, see !1450 ; LIMA problem, being solved
  • BLISS devices to "publish" their parameters automatically (#926)
  • Acquisition chain information (#902, #930, #922, #932)
    • What can be the best structure ?
    • Which information is missing ?

See `nxscanwriter` in id21blissutils

BLISS team responsible for data saving: L. Pithan

BLISS releases policy

Meeting held with A. Gotz on 6/9/2019

  • One release every month
    • latest release: 0.2.0, see changelog 
    • next release: 30/09/2019 (#985)
    • bug fixes to be backported to previous release, if possible
  • Change log to tell about differences, new features, bug fixes, deprecated functions, ...
  • Announcement on BLISS mailing list
  • Conda package

BLISS team responsible for releases: P. Pancino

Short term planning (from task list)

  • Data policy / electronic logbook support (M. Guijarro)
  • Missing features for Lima cameras (S. Petitdemange, L. Claustre*)
    • background, masks, flatfield etc.
  • Continuation on diffractometers support (L. Pithan, E. Papillon*)
    • documentation
    • tests on ID03's 6-circle diffractometer => code finalization
  • Wago Tango server using BLISS Wago controller (P. Pancino)
    • 100% compatible with the existing Tango server
    • support of new interlocks, new Wago TCP module
  • Still on-going: regulation framework (P. Guillou)

September

Replaced by scan toolbox tasks

Linus works on external data saving instead

Short term planning (from task list)

  • Finish MCA support (C. Guilloud, D. Naudet)
    • documentation
    • ROI counters
    • data saving -for fast scans-
    • Falcon X and other devices

October / November

  • Enhanced GUI support (S. Petitdemange, M. Guijarro)
    • monitoring framework, compatible with data acquisition
    • state passing between peers
    • use of distributed locking (leases)

Discussion

Training sessions

  •  For external users during Users Meeting : do we confirm ?
    • if yes: something simple, basic usage (similar to spec training before)
    • beyond BLISS: shouldn't we include information about data policy, electronic logbook etc ?
  • Training for BL scientists and beamline staff
    • When ? How ?

Newcomer to French CRGs: Benoît Fromet: next week !

  • will join forces within the BLISS team
Made with Slides.com