|Message: Re: RE: BeamOn won't allow generating more than 3 billion events||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I suggest you don't mess with the G4int typedef and especially don't assume that nowhere in the code this takes on negative integers. If it is too combersome for you to merge the results of separate runs to get the statistics you need, and you are free to modify the Geant4 source, then by all means redefine the code of G4RunManager:BeamOn:
so that n_event take the new meaning of n * billions of events. You then modify G4RunManager::DoEventLoop adding an outside for-loop accordingly.
I checked, i_event, G4RunManager::numberOfEventToBeProcessed and G4Run:numberOfEventToBeProcessed are used for printing purposes only except for some visualization logic at:
which looks harmless especially for a large batch job.
Running multiple primary particles for each event is only a solution if you are interested in quantities that are accumulative for the entire run. For signals that are derived event by event this will produce the wrong result because you'll get the system's responds to multiple primary particles/per event not just each one independently.
|Inline Depth:||Outline Depth:||Add message:|