RE: Limit on number of primary particles per event?

Help: Forums, postings and threads

Forums, postings and threads

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.

Layout of the posting thread(s)

The posting threads can be shown with/without the text of the postings ("Inline depth"). In addition the depth of the thread can be controlled ("Outline depth"). For both cases several values are provided, which can be toggled. Note that the displayed values are those, which can be chosen, they do not correspond to the actual display status of the thread(s).

Add message

Add a new posting thread to this Forum

Show subscribers

Click "Show subscribers" to get the List of all subscribers, who receive e-mail from postings to this Forum, if they have not explictly unsubscribed from a posting thread. This includes:

Subscribers to the forum
Explicit subscribers to the posting or any of its ancestors
The author of the posting (if he has not unsubscribed)
The authors of any ancestor posting (if they have not unsubscribed)

Some browsers display old pages from the cache

Some browsers (e.g. Firefox) display a page from the cache even though the page has been updated. As a result, one may not get the latest messages in the forum's outline or the logon ID of the previous session appears on the upper right corner. If one suspects that he or she does not get the latest content of a page, try clearing up the personal data from the browser's cache as the following:

Tools -> Clear Private Data -> Clear Private Data (from browser Firefox)

Tools -> Delete Private Data (from browser Opera)

then reflesh the current page to get the latest content.

Details on "Inline depth" and "Outline depth"

Threads and the follow-up messages are numbered. There is one line per posting, normally starting with the posting number. The URLs of a posting and its responses reflect the depth of the follow-up postings. Watch the URLs to see how this is done. Depending on the chosen display options, the thread-display may be incomplete; the number of messages at the next level is, however, displayed, e.g. "…3 message(s)". You may not see all contributors unless you choose "All".

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.

Argument Default value Alternative Comment

1 0 1 no text / full text of posting

2 1 All text for level 1 only / text for All postings

Argument	Default value	Alternative		Comment
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.

Argument Default value Alternative Comment

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)

Argument	Default value	Alternative	Comment
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)

Hi Makoto,

I ran exampleN01 with GPS primary generation, 1 event with 300000 primaries
through valgrind, which resulted in the output below. During the execution,
the memory used peaks at 16% of the total 1Gb, and that peaks at the start of run
and doesn't change whilst the run is processing.

Cheers,

Ben

Start Run processing.

==3578== Stack overflow in thread 1: can't grow stack to 0xBE6EFFFC
==3578== 
==3578== Process terminating with default action of signal 11 (SIGSEGV)
==3578==  Access not within mapped region at address 0xBE6EFFFC
==3578==    at 0x5884292: G4PrimaryParticle::~G4PrimaryParticle() (in /opt/warwick/epp/2007.0.1/geant4/9.1.p01/i686/gnu/4.1.2/lib/Linux-g++/libG4particles.so)
==3578== Stack overflow in thread 1: can't grow stack to 0xBE6EFFF8
==3578== 
==3578== Process terminating with default action of signal 11 (SIGSEGV)
==3578==  Access not within mapped region at address 0xBE6EFFF8
==3578==    at 0x401E200: _vgnU_freeres (in /usr/lib/valgrind/x86-linux/vgpreload_core.so)
==3578== 
==3578== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 17 from 1)
--3578-- 
--3578-- supp:   17 dl-hack3
==3578== malloc/free: in use at exit: 139,092,191 bytes in 271,762 blocks.
==3578== malloc/free: 4,176,472 allocs, 3,904,710 frees, 296,446,694 bytes allocated.
==3578== 
==3578== searching for pointers to 271,762 not-freed blocks.
==3578== checked 139,544,332 bytes.
==3578== 
==3578== LEAK SUMMARY:
==3578==    definitely lost: 0 bytes in 0 blocks.
==3578==      possibly lost: 115,814 bytes in 2,481 blocks.
==3578==    still reachable: 138,976,377 bytes in 269,281 blocks.
==3578==         suppressed: 0 bytes in 0 blocks.
==3578== Rerun with --leak-check=full to see details of leaked memory.
--3578--  memcheck: sanity checks: 5891 cheap, 236 expensive
--3578--  memcheck: auxmaps: 0 auxmap entries (0k, 0M) in use
--3578--  memcheck: auxmaps: 0 searches, 0 comparisons
--3578--  memcheck: SMs: n_issued      = 2984 (47744k, 46M)
--3578--  memcheck: SMs: n_deissued    = 26 (416k, 0M)
--3578--  memcheck: SMs: max_noaccess  = 65535 (1048560k, 1023M)
--3578--  memcheck: SMs: max_undefined = 33 (528k, 0M)
--3578--  memcheck: SMs: max_defined   = 1112 (17792k, 17M)
--3578--  memcheck: SMs: max_non_DSM   = 2958 (47328k, 46M)
--3578--  memcheck: max sec V bit nodes:    0 (0k, 0M)
--3578--  memcheck: set_sec_vbits8 calls: 0 (new: 0, updates: 0)
--3578--  memcheck: max shadow mem size:   47632k, 46M
--3578-- translate:            fast SP updates identified: 40,940 ( 86.1%)
--3578-- translate:   generic_known SP updates identified: 4,191 (  8.8%)
--3578-- translate: generic_unknown SP updates identified: 2,372 (  4.9%)
--3578--     tt/tc: 4,881,650 tt lookups requiring 20,549,198 probes
--3578--     tt/tc: 4,881,650 fast-cache updates, 3 flushes
--3578--  transtab: new        38,400 (1,084,325 -> 16,549,039; ratio 152:10) [0 scs]
--3578--  transtab: dumped     0 (0 -> ??)
--3578--  transtab: discarded  9 (209 -> ??)
--3578-- scheduler: 589,113,564 jumps (bb entries).
--3578-- scheduler: 5,891/13,231,378 major/minor sched events.
--3578--    sanity: 5892 cheap, 236 expensive checks.
--3578--    exectx: 30,011 lists, 12,372 contexts (avg 0 per list)
--3578--    exectx: 8,081,199 searches, 8,071,406 full compares (998 per 1000)
--3578--    exectx: 0 cmp2, 68 cmp4, 0 cmpAll
Segmentation fault