Linear Collider Forum

Home » Simulation » Mokka » feature or bug in TRKSiSD00?
Re: feature or bug in TRKSiSD00? [message #1716 is a reply to message #1686] Tue, 07 April 2009 07:45 Go to previous message
Messages: 57
Registered: February 2004
Dear Rita,

All sensitive detectors in the tracking region write
(to the hit that is being saved) the PID stored in


This is updated to the current TrackID in :

In TrackingAction::PreUserTrackingAction there is the following
piece of code:

if( TruePrimary || ( InsideTrackerRegion &&

aTrack->GetKineticEnergy()>Control::TPCCut) )

// reset the PID for Cal hits

If the initial kinetic energy of the track is greater than
Control::TPCCut (default is 10 MeV) then all sub-detectors
located in the tracking region will store in the hits the
PID of the current track.

The TPCCut can be changed by the command line option

Mokka -t <double>

specifies the TPC primary energy cut in MeV.
(enables the user to control the TPC output file length)
(default is 10 MeV)

or with the steering command:


The most direct way to go is to set the TPCCut to zero for
example, but in that case, all tracking devices will behave
like the VXD.

And, if I understood correctly from Paulo, all parent particles
are saved, up to the primary, thus giving large lcio files.

The other possibility is to

- replace 'currentPID' by 'currentSecondaryPID'

in TRKSiSD00::DumpHit

Thus correcting the specific problem of the VXD, and leaving the
other tracking detectors unaffected.

What do you think it would be best to do?

Best regards,
Read Message question.gif
Read Message
Previous Topic:vxd03 in ILD_00
Next Topic:Probs to start Mokka
Goto Forum:

Current Time: Fri Oct 18 00:05:31 Pacific Daylight Time 2019
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.1.
Copyright ©2001-2010 FUDforum Bulletin Board Software