ENH: XES Analysis Wishlist for smalldata

[fredericpoitevin]

Margaret Doyle is super happy with the new smalldata feature in the eLog to look at XE spectrometer alignment and is interested in integrating her whole analysis workflow. I put her wishlist below - one idea could be to create sub-issues from each item when starting to work on it, and close with the corresponding PR.

• [ ] Ability to average multiple runs together before displaying images in the XES - epix_1 tab. Users can group these runs together however they see fit, I could see us grouping batches of sample together or alternatively grouping sample conditions (flash states for PS II collected across different batches) together.
• [ ] Ability to compute the FWHM and peak position of spatial projection - so we can quickly quantitatively compare focus every time we do alignment
• [ ] Ability to throw a flag or warning to user if COM of spatial projection drifts or changes significantly relative to average
• [ ] Also throw a flag if additional strong peaks in spatial projection begin showing up
• [x] Can the dynamically updated x-axis for energy projection not be coupled with the spatial projection x-axis? Do not want them to share x-axis. #181
• [ ] Ability to include energy calibrated axis so we display spectrum on energy axis instead of pixel. I can provide function we use for this
• [ ] Ability to plot the energy dispersive spectrum from two 'batches' (averaged over N runs) on top of each other in the same plot
  • [ ] Ability to display the difference spectrum computed between these two spectra
• [ ] Ability to do a background subtraction from the energy dispersive spectrum
• [x] Automatic triggering of summary plots
• [ ] Ability to compute First Moment/ COM of spectra
• [ ] Ability to construct a scatter plot of the First Moment / COM computed from different 'batches' or 'groupings' on a plot (I can send an example)
• [ ] Ability to toggle between different detector images / projections for the same run but with different event codes (event codes are not used widely by our group tbh but I could see it being useful in certain scenarios)
• [x] Ability to rotate the image before summing to get crispier spectra

[tim-vandriel]

Adding XSS/XAS/XES wishlist for the liquid standard config I realize that these are not simple requests and may require some discussion about implementation.

Key requirement is robustness, so the automatic smalldata analysis becomes reliable and integrated into the workflow.

What is the best way to set parameters for automatic analysis? any barrier of entry will make it the first thing to suffer in a time-crunch. Automatic/robust parameters that can be overwritten or updated could be a way to go.

• [ ] It would be useful to extract a "slice" of one or more figures across all runs to see if things changed during the experiment

%%% parmeter visualizer

• [ ]General parameter monitoring, plots, histograms to see how the tracked PV's have changed (advanced archiver )

• [ ] Lasertiming: drift monitoring, lxt, txt, lxt_fast , TTfltpos fwhm, TT calib. Timetraces, running averages, 2D plots, histograms with FWHM estimates, "unique" with run grouping of lxt or lxt_fast range

• [ ] Laser power: Timetraces, running averages, 2D plots, histograms with FWHM estimates, "unique" with run grouping of LXE, LXE_OPA or diodU.ch0

%%% Overlap scans

• [ ] Robust XSS overlap scans when lens_h and lens_v and lxt are ascan/dscan'ed

• [ ] multiple runs on one page as we often repeat and try to find reproducibility

• [ ] Extend to overlap scans XES/XAS

• [ ] Extend to weaker and TT sorted lxt_fast timing overlap scans

• [ ] TT calib fit, confidence and output Powertit scans to find onset of nonlinear heating and linear regime.

• [ ] XSS onset of nonlinear heating

• [ ] linear regimes of XES,XAS,XSS diff signals

%%% Actual analysis for ongoing monitoring of the experiment

• [ ] XSS Analysis
• [ ] XES Analysis
• [ ] XAS Analysis