AgML Release Milestone 2

Simulations run in STARSIM show good agreement using the AgML and AgSTAR geometry descriptions for the latest revision of the Y2005 geometry to the latest revision of Y2009.

Few exceptions to note:

1) SVT hit multiplicity is simply wrong.  Possible explanations include misconfiguration of number of sensitive volumes, tracking thresholds, etc...

2) MUTD, FPD, FPD++ detectors are not imlpemented in g2t tables and cannot be tested

3) BBC does not appear in StMcEvent for some reason?


05/05/2011

I strongly suspect that the SVT issue has to do with the way the HITS operator has been implemented in AgML, and exported to Mortran:

The HITS operator in Mortran/AgSTAR looks like

HITS VOLU meas[=value]:BITS:[option][(min,max)] ...

or

HITS VOLU meas[=value]:BINS:[option][(min,max)] ...

where VOLU is the active volume, and the definition of one or more hits follows.  Where multiple definitions occur, oder matters.  The initial versions of AgML used an 'operator' style for declaring hits:
 
<Hits for="VOLU"  meas1="..." meas2="..." />
 
Such an approach does not preserve the order.  So I have refactored the declaration of hits in AgML to an "instrumentation block" such as...
 
             <Instrument block="SVTD"  >
                <Hit meas="z" opts="S" bins=".001"  />
                <Hit meas="y" bins=".001"  />
                <Hit meas="x" bins=".001"  />
                <Hit meas="ptot" nbits="18" min="0" max="100"  />
                <Hit meas="cx" nbits="10"  />
                <Hit meas="cy" nbits="10"  />
                <Hit meas="cz" nbits="10"  />
                <Hit meas="sleng" nbits="16" min="0" max="500"  />
                <Hit meas="tof" nbits="16"  />
                <Hit meas="step" bins=".01"  />
                <Hit meas="eloss" nbits="22"  />
            </Instrument>
  

now the fun part... I need to go through by hand all of the geometry modules and rewrite the hits blocks...