Page History

h3. List of things from Philip that he does in his analysis code:

1 = trivial, but maybe check
2 = they should do if they don't
3 = surely they do

1: subselect quad to analyze
2: filter on event 162 etc
2: run on every nth event
2: dump every mth event to file; dump event passing criteria
2: dump event time
3: turn on/off frame noise
2?: recognizes pedestal run and just does basics
2\!: run on either cspad or cspad2x2 with the same analysis code
2\!: run on all cspads in event, produce files labelled by detector
3: get other detector info (e.g. ipimb) for use in cspad frame analysis;
   for example I look at the previous event's ipimb and eBeam
2: check header vs element fiducials
1: keep careful track of # of analyzed events
1: I could trivially analyze multiple cspads together per frame
2: dump selected events to xtc file
2: dump pointer to interesting events
2: run on just a particular calibration step
1: print out a few pedestal values each run
2: run over multiple files using run list
3: use root; should be able to use lighter faster histos too
2: do simple clustering, find isolated hits; singles, doubles, triples
2: know where pixel i,j is using metrology, or dump out array for later
   analysis
2: (my job presumably): Apply various fitting approaches to single-photon
                        gain calibration
2: run easily in batch (not a myana thing, I do e.g.
\#\!/bin/tcsh
set run = ($1)
setenv runFile `printf "/reg/d/psdm/MOB/mob20113/import//e0-r%04d-s00-c00.xtc" $run`
set s = (0)
set step = (0)
while ( $s < $2 )
&nbsp;&nbsp;&nbsp;&nbsp;bsub \-q psfehq \-o out_${run}
\_${s}.out \~/cxi/myana/ssrl_B22_Jan13/runJob.csh ${step}${run}${s}${runFile}
&nbsp;&nbsp;&nbsp;&nbsp;@ step\+
\\
+
&nbsp;&nbsp;&nbsp;&nbsp;@ step\+
\\
+
&nbsp;&nbsp;&nbsp;&nbsp;@ s\+
\\
+
end
which would take a new user a while to come up with.

2: all the stuff one can do easily in the online, plus maybe easily
transfer setups from offline_ami to psana. &nbsp;For example it would be nice
to be able to select an area in offline_ami and look at some histos, then
run the same selection in psana to get higher stats (rates).

2: fill some standard default histos - spectrum per modules, full range/
close to single-photon range, common-mode distribution, 2d plot of hits
over threshold, etc.