Beam monitoring step

[vratislav3]

We will need selfstanding step for beam monitoring.

Creation and filling of histograms related to RIB diagnostics will be realized here.

In this step will be no processing of data related to detectors other than MWPC and TOF.

Detectors and stations should be stored as class data members.

[evovch]

See commit 1e0c841

To be checked by vratislav3 and developed further on.

[vratislav3]

It is not possible to check BeamDetMonitoring step in GUI, for following reasons:

1. file electronics2.xml cannot be found - solved by copy to WORKINGDIR/usr, temporary FIXME in UserAnalysis.cxx respected at current developing stage;

2. when enabling AdvMonitoring step (BeamDetMonitoring disabled or enabled at the same time), analysis is stopped.

3. when AdvMonitoring disabled and BeamDetMonitoring enabled, GUI analysis terminal gives "[WARN ] UserProcBeamDetMonitoring::BuildEvent(): no input event!"

additionally: file setup.C was copied to working directory to avoid message about missing setup.C but it seems that there is no effect on GUI window.

[evovch]

Error mentioned in the items 2&3 of the list actually appeared due to my inadvertence. See commit 0c22402 which seems to fix it.

Indeed one has to somehow provide electronics.xml file to the analysis. Currently it is implemented such that it is taken from the ./usr/ directory and go4 probably starts searching from the working directory which is specified in a dedicated textbox when running GUI. Another option, if reimplemented, could be to specify the path to electronics.xml together with the path to the setup.xml. For now I rejected this approach as I don't expect the users to change (or at least produce new versions of) this file and adding another item makes the already annoying arguments list even longer.

The setup.C macro is imported here:
https://github.com/evovch/ACCULINNA_go4_user_library/blob/master/useranalysis/UserAnalysis.cxx#L63
after processing the code in the Construct method of the UserAnalysis class invoked here:
https://github.com/evovch/ACCULINNA_go4_user_library/blob/master/useranalysis/UserAnalysis.cxx#L59
which means that the analysis setting are overwritten by setup.C.
The open question still is how this related to the settings defined in the GUI window.