Page History

...

• DM needs a framework for describing sensors, their properties and positions, including how to iterate over the sensors 
  • 6 months for delivery of this
  • Plan is python except for a detector class (with coord transforms) and then detector class in C++
  • OPSIM: needed outside of opsim for post-processing of outputs of opsim, may be needed inside of opsim for dithering (a long term goal)
    • probably only need positions at the amplifier level
    • Srini and Steve R will work with Simon to make sure Opsim is represented
  • PHOSIM: 
    • John will represent phosim on the camera geom redevelopment

Following is a part of an email sent to members of the OpSim and Camera teams.  I am very interested to have conversations with anyone having a stake in the design of the camera geometry classes.  Further, please feel free to add requirements to the design page.

I (Simon Krughoff) am leading the DM effort to redesign the camera geometry framework.  From the DM perspective the camera framework is responsible for several things.

1. Providing iterators over all devices in the camera.  This allows logical flows like:

  for every device in my camera:

    do some work

2. Providing coordinate transforms to/from a set of defined coordinates systems (e.g. pixel, camera, sky).

3. Providing a container to hold important electronic information for calibration as well as how to assemble amp segments into a full chip size grid.

The work is currently in the design phase and I would very much like to get input from the camera team and the OpSim team on requirements that are not provided by DM.

The current design document is at:

https://dev.lsstcorp.org/trac/wiki/Winter2014/Design/CameraGeom

The summary is that we intend to take a hierarchical approach  where cameras contain rafts and rafts contain detectors.  The implementation will primarily be in python with the detector class implemented in C++ so that the coordinate transforms contained by the detectors can be written in C++ and accessed by algorithms in C++.  The Detector class will be available in python via SWIG wrappers.  We intend both the hierarchy and coordinate systems to be configurable.

Crosstalk 

• Tony mentioned that modelling cross talk may be significant for opsim
  • magnitude of crosstalk correlates with readout time so simulations of the impact of increasing readout could be beneficial
  • better understanding of the crosstalk on time scale of 2 months

...