Message: Re: G4 killed itself. Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

More Re: G4 killed itself. 

Keywords: Memory
Forum: Run Management
Re: Question G4 killed itself. (Sehwook Lee)
Re: None Re: G4 killed itself. (Jane Tinslay)
Re: Idea Re: G4 killed itself. (Gumplinger Peter)
Date: 19 Nov, 2006
From: Gumplinger Peter <Gumplinger Peter>

Doesn't work ...... the user must not delete:

G4VTrajectory* trajectory = fpTrackingManager->GimmeTrajectory();

in UserTrackingAction - or else core dumps!

However, I found a solution to draw tracks in PostUserTrackingAction without the G4TrajectoryContainer overflowing with G4Trajectories.

The solution is to set in PreUserTrackingAction:

fpTrackingManager->SetStoreTrajectory(true);

then in PostUserTrackingAction:

#include "G4VVisManager.hh"

if (G4VVisManager::GetConcreteInstance()) trajectory->DrawTrajectory(50);

fpTrackingManager->SetStoreTrajectory(false);

If I now look in EndOfEventAction there isn't even a

G4TrajectoryContainer* trajectoryContainer=anEvent->GetTrajectoryContainer();

This was tested with /examples/extended/optical/LXe

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: G4 killed itself.   (Sehwook - 19 Nov, 2006)
 Add Message Add Message
to: "Re: G4 killed itself."

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]