Message: RE: RE: managing memory Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None RE: RE: managing memory 

Forum: Run Management
Re: None managing memory (Neil Fazel)
Re: None RE: managing memory (Makoto Asai)
Re: Question Re: RE: managing memory (Neil Fazel)
Date: 13 Jul, 2010
From: Makoto Asai <Makoto Asai>

G4Event and related objects including trajectories are
automatically deleted when processing an event is done,
unless you specifically do something special. Do NOT
delete G4Event in your EndOfEventAction.

Do you use parameterized volume? If so, check your code
which is invoked for every step and see if you instantiate
anything.

Makoto

> -----Original Message-----
> From: Neil Fazel [mailto:fazel@physics.utexas.edu]
> Sent: Tuesday, July 13, 2010 9:41 AM
> To: runmanage-g4hn
> Subject: Re: RE: managing memory
> 
> 
> *** Discussion title: Run Management
> 
> On Tue, 13 Jul 2010 05:10:57 GMT, Asai, Makoto wrote:
> 
> > Hi,
> >
> > Given the incident energy of a few GeV, 100 is quite a small number.
> > First of all, if you are visualizing all the events, that is the
> > first thing to drop. Secondarily, if you keep trajectories or
> > events themselves for more than one events, that should be given
> > up. If your problem still persists, check all the user objects you
> > instantiate during the event, e.g. hits, are properly deleted at
> > the end of each event.
> 
> Thank you. I have disabled all visualization and run either from the
> Idle> prompt or in batch mode. I checked to make sure that I'm not
> invoking G4Run->StoreEvent() to explicitly store events. How does the
> user ensure trajectories or events are deleted after they are no longer
> needed? My guess is that something needs to be done in
> G4Event::EndOfEventAction() or G4Run::EndOfRunAction(). Do I need to
> delete the G4Event object in G4Event::EndOfEventAction()?
> 
> Thanks, Neil
> 
> -------------------------------------------------------------
> Visit this GEANT4 at hypernews.slac.stanford.edu message (to reply or
> unsubscribe) at:
> http://hypernews.slac.stanford.edu/HyperNews/geant4/get/runmanage/275/1
> /1.html

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

1 Feedback: managing memory   (Neil Fazel - 13 Jul, 2010)
 Add Message Add Message
to: "RE: RE: managing memory"

 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 ]