| Step | What | config | I/II | beam? | fixed/autoranged | AMI/offline? | metrics | analysis | notes | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 5 pedestals | both | no - be sure not | both | both | Compare offline to expectations. Compare makepeds bad pixels to expectations. Check switch point | documentation makepeds existing script or inspect | Jira to make n_bad_pixels visible | ||||
| plain dark | fixed (both???) | check noise w/w/o common mode correction | existing script, documention | ||||||||
| forced low dark | auto | compare pedestal level to expectation | documentation | Interface take r0, specify 5 ped run. Script could be smart enough to see if r0 is a five-pedestal. Make a histogram of difference. Also image. Addresses tiger teeth or whatever. | |||||||
| charge injection | both | no | both | offline | check switchpoint | existing script | pre-beamtime presumably | ||||
| Blunt autoranging test | both | intensity scan | auto | both | Look for negative pixels in AMI (calib) Look offline for negative pixels | existing script | |||||
| Persistence check | both | yes | both | offline | Look at dropped shots | existing script | watch out for heating Ideally with features like rings | ||||
| Intensity scans | yes | both | offline AMI-II | linearity in fixed modes hockey stick procedure (look for negative-going region etc.) | understand wave8 | ||||||
| Masked xtalk check | yes | both? | Look at both illuminated and unilluminated regions | Pinhole or lead tape or disk with hole Need to steal masking procedure? | |||||||
| timing scan | yes | both | offline AMI-II | Xavier has something | Need DAQ script to change timing | ||||||
| Bias plateau | yes - steady | fixed | offline | take ten runs from 20-200 V | |||||||
| T sensitivity | reduce cooling | not a common test | |||||||||
| Different DAQ rate | II | could repeat all the above... rare activity | |||||||||
| Intensity monitor crosschecks | existing root script Kaz's scripts look at automated plots, write python algorithm; check for saturation, noise | Make a script that allows us to call the expert-derived algorithm(run). | |||||||||
| Single-photon spectrum | both | low flux | fixed (mostly?) | reconstructed energy, width | existing messy offline suite | Need automated way to estimate n photons Scripts use a lot of root Some issues about cuts (one pixel? cluster energy?) | |||||
| Geometry (AgBehe) | rare activity | ||||||||||
Overview
Content Tools
2 Comments
Philip Hart
(Offline) scripts should have a common interface for expt, run (range), camera type, ... Perhaps some minimal logging so we know what we've run - that could be part o f the standard structure by importing a logging class. Also indicates success. Check with Fred on this. Flux should come from an imported class too.
Philip Hart
We might use the argparse stuff in e.g. /cds/home/p/philiph/psana/detdaq20/epix100/keVify.py to make a class that established the interface. See also a job history file like /reg/d/psdm/mfx/mfxx1005021/results/scripts/scan/jobHistory.txt.