Page History

This page is here to capture our thoughts, task lists, and priorities in streamlining the cspad analysis experience.

Meetings

What: Weekly meetings to discuss streamlining of cspad analysis.
When: Mondays, 2 PM
Where: Erie Conference Room (Building 40, Room 209, see map)

This meeting will occur weekly until we have a good useable interface and infrastructure for taking, viewing, and analyzing cspad data.

2013-

...

10-02 LCLS User's Meeting

• CSPAD Analysis Overview (Mikhail)

2013-07-17 Meeting

• Experimenting with GUIs for Calibration management tool developement notes

2013-06-20 Meeting

Decision Meeting

Discussion

Agenda:

• Review/agree on requirements for a streamlined cspad analysis
• Discuss versioning of calibration directory and agree on a design for tracking versions

2013-05-29 Meeting (Minutes):

Agenda:

• 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):

  Agenda:

  • CSPAD Calibration etc. - Mikhail

  ...

  • 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?

  2013-05-13 Meeting (Minutes):

  Agenda:

  • Overview
  • Get feedback from Sven and Philip on what they'd like to see for users (and for themselves)
  • Formulate task list and priorities