A starting point on the requests to be answered by a common geometry API [message #104] |
Sat, 05 June 2004 10:12 |
lima Messages: 47 Registered: May 2004 Location: DeKalb, IL, USA |
|
|
|
This list is the result of a discussion carried out during the
LC simulations workshop at Argonne. Please add to this topic your comments and suggestions to this list. Comments from reconstruction algorithm developers are specially encouraged.
Guilherme, for the
Worldwide LC Simulations working group
---------------------------------------------------
Requests to be answered by a common geometry API
a starting point
* reqs on the geom system:
. full detector
- name/tag
- version
- others?
. given (x,y,z):
- material properties
density, radlen, intlen, others?
- E-field
- B-field
- distance to closest detector element (is this needed)?
- cell/channel
. id
. shape
. dimensions
. distance to closest edge
. volume, area, etc (needed?)
. given volume (cell/channel) id
- center position
- local <--> global coords transformations
- neighborhoods?
- geant4 attributes
. given A(xa,ya,za) and B(xb,yb,zb) (straight line only!)
- distance
- # radlens
- # intlens
- integral E.dl or B.dl
- collection of traversed volumes
. hierarchical view: given a volume
- collection of mutually exclusive, non-overlapping
subvolumes
- parent volume
- list of all parents
- sensitivity
- type (calorimeter or tracker)
. given vecP(px,py,pz)...
- nothing from a geometry system, but
from a client of the geometry system
|
|
|