Problem 1568 - integer limit for number of events per run
Summary: integer limit for number of events per run
Status: RESOLVED WONTFIX
Alias: None
Product: Geant4
Classification: Unclassified
Component: run (show other problems)
Version: 10.0
Hardware: All All
: P5 trivial
Assignee: asai
URL:
Depends on:
Blocks:
 
Reported: 2014-02-12 11:25 CET by martin.stieben
Modified: 2014-02-21 22:13 CET (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description martin.stieben 2014-02-12 11:25:27 CET 
Since all handling of the number of events per run (started by G4RunManager::BeamOn()) is done with standard 32-Bit integer type variables there is a hard limit of 2.15*10^9 events. 
However, some applications can't merge events from several runs due to data acquiring issues but need a number of events per run above the standard integer limit.
A desirable solution would be to replace the current 32-Bit number of events data type by a 64-Bit long integer in all event handling classes.
I don't see any reason why this would be a problem to implement. But it has just to be done by someone of the geant4 team for the next release.
Comment 1 asai 2014-02-21 22:13:56 CET 
I don't know how many primary particles you have in your individual event, but please consider having more primary particles (and more primary vertices if you like) so that you can live with 32-bit integer. There is no hard limit for number of primary particles per event.
Makoto