Page History

...

• camViewer <-h>: starts the python viewer. You can pass the relevant camera by supplying via the '-c <camname>' argument. Adding '-m' will start the edm screen for the relevant area detector 
• iocmanager <lfe> (turns out, you need to be on lfe-console to see most of the processes)
• eloggrabber <-h>: by defaults starts the operator eloggrabber of the hutch that is guessed by the hostname or pathname. '-u <username>' will start the eloggrabber as yourself, but you need to start it from a session in which you have a personal kerberos token.
• lfe : 'lucid' home screen for the FEE

...

A few python notebooks will be provided in /reg/d/psdm/xpp/xpp43118/results/smalldata_tools/notebooks. If you want to use those, I will suggest a softlink of this directory from your home as the Jupyterhub will also ways starts from your home area.

Samples

The new elog allows us to define 'samples' or run groups. For e.g. the run tables & elog, you can toggle between the run groups or show all the data.

Beamline Python (xpp3)

Components in the lfe beamline will be provided in xpp3. Their names follow the standard device names w/o caps (e.g. im1l0). We have also defined a few convenience functions which will be deceived below (the complete list can be found by typing x.<tab>:

...

• returns a 'plan' to move motor <motor> in <steps> steps from <start> to <end>, taking <nEvents> at each step. This will take control of the DAQ. To actually RUN the scan, you can either
  • myscan=x.get_ascan(...); RE(myscan); do something ; RE(myscan) or
  • RE(x.get_ascan(...))
• you can scan any motor and most other variables that you have permissions to change as well. If in doubt, test & ask if there are issues.

x.get_ascandscan(motor, start, end, steps, nEvents, record=True):

...