Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Rob's editorial comments in italics.

Rob showed his proposal for organizing hit information. His slides have been added to: http://docdb.fnal.gov/ILC-public/DocDB/ShowDocument?docid=419Image RemovedSee the two attached files.

There were a number of errors in the slides that have been fixed in the versions put at the above location.

...

Tim suggested that at the hit level a pixel detector should return a cellID that is a single int, not a pair. This is converted to (u,v) in local coordinates by a method of the geometry system. One good case to illustrate why this is a good idea is the case of a hexagonal close packed pixel detector, in which the transformation from a cellID, whether 1D or 2D, into (u,v) is complicated and should be hidden from the user. Another case is a strip detector with strips that are not simple rectangles, such as curved strips or phi strips that have
a width that is a function of radius. So Rob will modify his proposed classes to be consistent with this idea.

...

  • long getCellId();
  • IDDecoder get IDDecoder();
  • SubDetector getSubDetector(); and

And replace with:

  • (some smarter cell ID) getCellID();
  • DetectorElement getDetectorElement();
    where the smarter cell Id is to be defined. It is capable of identifying a single channel on the sensor defined by DetectorElement. There was disagreement about whether it should just be the channel ID on the given detector or whether it should be the full ID of the channel, including the components that identify the sensor. I believe that it should be the former since we already have the information about the sensor available via the getSubDetector() method.