Message: Re: Skipping an event where the code gets stuck Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Re: Skipping an event where the code gets stuck 

Keywords: random status
Forum: Event and Track Management
Re: Question Skipping an event where the code gets stuck
Re: None Re: Skipping an event where the code gets stuck (Makoto Asai)
Date: 24 Jul, 2006
From: Ioannis Sechopoulos <Ioannis Sechopoulos>

Makoto, I am having problems with my code in which I get a "Segmentation Fault" error at some point of the simulation with no real other error message. To be able to look at the error with more detail, I tried your suggestion of saving the random number status at each event by using /random/setSavingFlag. After I get the segmentation fault, I restart the program and use /random/resetEngineFrom currentEvent.rndm and use /run/beamOn again. To my surprise the simulation runs with no problem! Is there something I am doing wrong to be able to replicate the point just before the error, so that I can perform further analysis?

Thanks!

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

 Add Message Add Message
to: "Re: Skipping an event where the code gets stuck"

 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 ]