Logbook

Electronic logbook

One of the ESRF data policy services is the electronic logbook. BLISS uses it to log user commands, the start of datasets, etc. Users can also use it to send custom messages:

DEMO [1]: elog_print("user message in electronic logbook ")

You can configure the e-logbook (persisted in Redis) of each Bliss session to send all e-logbook messages to the beamline+proposal logbook OR beamline logbook only:

DEMO [1]: elogbook.beamline_only = True  # No elogbook messages will be
                                         # send to the proposal logbook.
DEMO [2]: elog_print("hide from user")
DEMO [3]: elogbook.beamline_only = False  # The default: messages appear in
                                          # beamline AND proposal logbook.
DEMO [4]: elog_print("visible by user")

In addition you can overwrite the default setting for each message separately:

DEMO [1]: elogbook.beamline_only = False  # Messages appear in beamline
                                          # AND proposal logbook.
DEMO [2]: elog_print("hide from user", beamline_only=True)

DEMO [1]: elogbook.beamline_only = True  # No elogbook messages will be send
                                         # to the proposal logbook.
DEMO [2]: elog_print("visible by user", beamline_only=False)

Scan comments

When not using the ESRF data policy, comments can be added to the scan:

DEMO [1]: s = loopscan(10,0.1,run=False)
DEMO [2]: s.add_comment("This is a comment")
DEMO [3]: s.add_comment("This is another comment")
DEMO [4]: s.add_comment("And another one")
DEMO [4]: s.run()

These comments are saved in the HDF5 file created by the Nexus writer.