|
Right! OK!
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.
| 
Re: How to create ASCII output? 
Feedback
]
icon
and there is no indentation. 
