process_run DAG

[fredericpoitevin]

We list the tasks that define each DAG. We consider a task completed when successfully ran manually on the FFB nodes, and a DAG completed when successfully ran through the eLog.

• run_analysis

$ . elog_submit.sh -c ../tutorial/mfxlv4920.yaml -t run_analysis -n 8

run_analysis:
  max_events: -1

Figures visualizing the powder pattern and run statistics will be saved to ${config.root_dir}/powder/fig/*_r{run:04}.png.

• opt_distance

$ . elog_submit.sh -c ../tutorial/mfxlv4920.yaml -t opt_distance -n 1

opt_distance:
  center: 960 960

If the run is a silver behenate run, this will estimate the distance to the detector and generate a new CrystFEL-style geometry file with the coffset parameter updated accordingly. A figure of the fit can be found at: ${config.root_dir}/geom/figs/r${run:04}.png

• find_peaks: Peakfinder #46

$ . elog_submit.sh -c ../tutorial/mfxlv4920.yaml -t find_peaks -n 8

find_peaks:
  tag: ''
  psana_mask: False
  min_peaks: 10
  max_peaks: 2048
  npix_min: 2
  npix_max: 30
  amax_thr: 300.
  atot_thr: 600.
  son_min: 10.0
  peak_rank: 3
  r0: 3.0
  dr: 2.0
  nsigm: 10.0

• index

$ . elog_submit.sh -c ../tutorial/mfxlv4920.yaml -t index -n 8

index:
  tag: 'test'
  int_radius: '4,5,6'
  methods: 'mosflm'
  cell: '/cds/data/psdm/mfx/mfxlv4920/scratch/apeck/cco.cell'
  tolerance: '5,5,5,1.5'
  no_revalidate: True
  multi: True
  profile: True

• display

[fredericpoitevin]

The corresponding DAG would be something like this:

ag_behenate >> opt_distance
run_analysis >> opt_distance
no_ag_behenate >> find_peaks >> index

But we don't have the Y/N logic for detecting AgBehenate at the moment.