|Message: Re: How to create ASCII output?||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)|
These issues are more to do with C++ and object oriented programming than with Geant4.
Creating an analysis manager is a way of being object oriented. In any function you can (using A01 as an example)
A01AnalysisManager* am = A01AnalysisManager::GetInstance(); am-><any-public-method-or-data-member-of-A01AnalysisManager>
So it's then up to you to write methods (functions) of the analysis manager or give access to data of the analysis manager that you want.
If you want to avoid the overheads of all this, C and C++ allows you to define a global object, say, myfile:
#include <fstream> using namespace std; ofstream myfile("myfilename");
at the top before any functions, methods, etc., and use it
myfile << whatever << endl;
anywhere. If you want to write to the same file with code that is in more than one C++ source file, put the above in one file, where the first output will come from, and
#include <fstream> using namespace std; extern ofstream myfile;
in every other source file. This is allowed in C and C++, but it's generally thought to be bad practice to have global objects (you might get a confusion of names).
Another point is: one usually wants to postpone the decision about writing until the end of the event. I typically put stuff, e.g., energy deposited in each step, in containers in the analysis manager, then in EndOfEventAction write it all out if the event passes some selection criterion. If you really want to do this the proper way you should create hits (see examples/novice/N03 and following) and dump them to file in EndOfEventAction if you want, or even more professionaly, use Geant4 persistency classes. Hits have the advantage they can be viewed if you write a Draw method.
|Inline Depth:||Outline Depth:||Add message:|