|Message: Re: Memory use by ROOT histograms||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)|
Hi Alexandr, Andreas,
From the code sample, it is clear that Alexandr uses the Geant4 analysis tools based on g4tools.
In Geant4 examples, we instantiate G4AnalysisManager both on workers and on master (and create histograms per thread) so that we need not to lock filling the histograms what would be required if we use just one shared object. The design however does not prevent you from creating the analysis manager only on master and use from the workers with locking the filling operation. What is required by the design is that the master object must be instantiated if you have instances on workers and use histograms.
From the provided code, it is however not clear how you create your event action class, as usually the event action class is created on workers (in ActionInitialization::Build method), and so moving the analysis code here does not change the situation.
|Inline Depth:||Outline Depth:||Add message:|