Logbook: command output
Currently user commands are send to the e-logbook:
loopscan(1, 0.1, lima_bv4.counters,lima_bv4, mg1)
I see my ID21 colleagues add this manually
loopscan(1, 0.1, lima_bv4.counters,lima_bv4, mg1)
Scan(number=143, name=loopscan, path=/data/id21/inhouse/20Mar/blc11998/id21/condition1/condition1_0002/condition1_0002.h5)
And for a ct
ct(0.1, lima_bv4.counters, mg1)
they add this
ct(0.1, lima_bv4.counters, mg1)
xtal1_111_rx = 3306.573872190382 ( 33065.73872190382/s)
xtal1_111_ry = 42066.31325495296 ( 420663.1325495296/s)
xtal1_111_z = -50265.41570420471 (-502654.15704204707/s)
xtal1_311_rx = 188538.66651645824 ( 1885386.6651645822/s)
xtal1_311_ry = 77925.46098652661 ( 779254.609865266/s)
xtal1_311_z = -54886.276820420826 (-548862.7682042082/s)
xtal_111_drx_filter = -229248.12180244114 (-2292481.2180244112/s)
xtal_111_dry_filter = 531120.960650949 ( 5311209.60650949/s)
xtal_111_dz_filter = 11344560.445432859 ( 113445604.45432858/s)
acq_time = 0.13295602798461914 ( 1.3295602798461914/s)
fwhm_x = 86.01273888049354 ( 860.1273888049354/s)
fwhm_y = 93.47569043604665 ( 934.7569043604665/s)
intensity = 1730.0 ( 17300.0/s)
x = 662.6433882115568 ( 6626.433882115568/s)
y = 402.77495794674564 ( 4027.7495794674564/s)
Scan(number=134, name=ct, path=)
So from observing this:
-
should we have something like spec's pon/poff which sends the output of a command to the logbook as well?
-
maybe for scans we can always add "Scan(number=143, name=loopscan, path=/data/..." to the command?
Not sure, just suggestions.
Edited by Wout De Nolf