Page History

...

• Review of actions
  • Python module for posting message into ELog
  • procOpticalAlignment.py - script for CSPAD optical measurement quality check
  • procCSPad2x2OpticalAlignment.py- script for CSPAD2x2...
• Overview of cspad analysis in ami
• Discussion of commonalities between ami and psana style analyses
  • What can we do easily in both realms that will allow users to get the same answer regardless of where they do the analysis?

Actions:

• Gabriella/Sven/Philip: Provide some data (non-proprietary) that anyone can use to run a basic cspad analysis/tutorial against. Send Jana an experiment name/number and run numbers (include data from MEC as well, if possible).
• Igor et al. will identify where to copy it where everyone has permission to read it. (Proposed:  /reg/d/ana11/cxi/data/)
• Jana: Come up with a proposal for group discussion at the next meeting that describes the plan for streamlining and improving cspad analysis.

2013-05-20 Meeting (Minutes):

...

• Write a script that can go through and discover all of the cspads configured in the data and run calibration for all of them in one pass (external to psana)
• Create scripting interface/mechanism for looking at dark runs, creating pedestals, and putting in common calibration directory
• Automate the integrity check of Chris' geometry corrections so he can tell right away if he's made an obvious typo.
• Philip/Sven to provide some data that is not proprietary that anyone can run a basic cspad analysis against, to be used for confluence examples. Philip and Sven identify the data; Igor et al. can identify where to put it so everyone has permission to read it.
• All: think about version control for the calibration directory. When is it regenerated? How is that communicated/version
  controlled? By what mechanism can a user figure out what inputs were used to generate a set of calibrations?

...