we have these field definition volumes that were added in order to force G4 to take a step at the boundary of the constant field. 

The problem that is arising is that these volumes are overlapping with the tracker itself. How do we deal with this? Clearly this is kind of a hack from the start but perhaps there is a smart way of keeping this. Perhaps we donít care if we are going to a 3D field map where the step size is not determined by this. 

For now, Iíll remove it from any new detector.


<detector id="30" name="TrackerFieldDef" type="HPSTracker2" readout="TrackerHitsFieldDef" >
            <comment>Boundary planes for magnetic field, also used as scoring planes</comment>
<!--        <constant name="dipoleMagnetHeight" value="17.78*cm"/>
        <constant name="dipoleMagnetWidth" value="41.6052*cm"/>-->
            <module name="TestRunModuleFieldDef">
                <box x="416.052" y="177.8" />
                <module_component thickness="scoringThickness" material = "Vacuum" sensitive="true"/>
            <module name="TestRunModuleFieldDefFlare2">
                <box x="416.052" y="177.8+(327.66-177.8)*(dipoleMagnetPositionZ+dipoleMagnetLength/2-913.378)/385.572" />
                <module_component thickness="scoringThickness" material = "Vacuum" sensitive="true"/>
            <layer id="1">
                <module_placement name="TestRunModuleFieldDef" id="0" x="dipoleMagnetPositionX" y="0" z="dipoleMagnetPositionZ-dipoleMagnetLength/2" rx="0" ry="0" rz="-PI/2"/>
            <layer id="2">
                <module_placement name="TestRunModuleFieldDefFlare2" id="0" x="dipoleMagnetPositionX" y="0" z="dipoleMagnetPositionZ+dipoleMagnetLength/2" rx="0" ry="0" rz="-PI/2"/>


can someone tell me exactly 
who added 

Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link: