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

None Re: Skipping an event where the code gets stuck 

Forum: Event and Track Management
Re: Question Skipping an event where the code gets stuck
Date: 01 Sep, 2005
From: Makoto Asai <Makoto Asai>

You can use G4UserLimits to limit the maximum number of steps for
a track, for example. 

By the way, it will be quite beneficial to us if you can identify
how your program stuck. Please try the following and report it to
this HyperNews.

1) Store randum number status (seeds) for every event
2) Kill the execution of your program when it stuck, then the
stored random number status is the one for the problematic event.
3) restart your program with the stored random number status, with
necessary verbose lebel.


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

1 Question: Re: Skipping an event where the code gets stuck   (Ioannis Sechopoulos - 24 Jul, 2006)
 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 ]