MON96 is the 1996 version of the Baikal Online Monitor Program. The latest release of this F77-program, MON96e, is described in this paper. The Baikal Online Monitor Program runs on the "Monitor PC" (an 486/386 IBM-PC), that is part of the DAQ in the shore station of the Lake Baikal Neutrino Experiment. This program is an intelligent user interface to access the information stored and processed on the shore station transputer modules ("LIM"-modules).
The program runs in two different modes:
The program has been developed in close collaboration with
H.Heukenkamp (LIM software), S.Klimushin (Host-PC software)
and D.Petukhov (Host-PC and LIM software).
In case of bugs, questions, remarks or suggestions, please
contact per e-mail:
wischnew@ifh.de (Ralf Wischnewski) .
First you have to install Salford F77, DBOS and the F77-Cernlibs appropriately to your harddisk (this has been done on all PCs in use in the Baikal Collaboration). If you only want to run the program (no compile-and-link), it is sufficient to install DBOS.
To install the latest Monitor-release, copy the arj-archive file
to your disk and unpack it, including the subdirectories
(we assume for the following the release is MON96e and
your working directory is C:\monitor):
C:\monitor > copy a:\mon96e.arj * C:\monitor > arj x -y mon96e.arj
Apart from the files copied to C:\monitor (*.for, *.cmn, *.obj, *.exe, *.bat, *.hlp),
four subdirectories will be created.
C:\monitor\LIM_BACK for the normal LIM_backup-files.
C:\monitor\user_ana -
containing all files related to user-analysis (see Chapter "User-Analysis" below).
Subdirectory C:\monitor\user_ana\LIM_BACK - where all backup files
created while running the user-version of the monitor program will be stored.
C:\monitor\pl2 for pl2_m.exe, an updated version of the
hbook-viewing program pl2.exe by I.Belolaptikov
(see Chapter "New Menu Items").
The directory structure is as follows:
c:\monitor -- standard monitor program c:\monitor\LIM_backup -- ... the backup files c:\monitor\user_ana -- user-analysis program development c:\monitor\user_ana\LIM_backup -- ... the backup files c:\monitor\pl2 -- plot-program to view hbook-files
The only file you possibly have to adjust when working at your machine
is c:\monitor\lib_z.lin.
This file contains the absolute paths of the CERNBLib files
(located in different directories on different machines).
You need this file if you want to recompile-and-link the executable file
mon96e.exe, and if you want to compile-and-link to create
your own "User-Analysis" (see Chapter "User Analysis").
You simply would edit this file accordingly, that is (assuming the CERNLibs are
on d:\cernlibs\ on your machine):
lo c:\ftn77wor\newlib\hplot5n.lbb ---> lo d:\cernlibs\hplot5n.lbb lo c:\ftn77wor\newlib\higzl.lbb ---> lo d:\cernlibs\higzl.lbb lo c:\ftn77wor\newlib\hbook.lbb ..... ...
A new compile-and-link run for the standard monitor program is then
done by the file do_lim.bat:
C:\monitor > do_lim mon96e
This will produce a new executable file mon96e.exe.
Note, that it is possible to produce a test-version of the program,
that is actually omitting any communication with the LIM and simulating
the LIM response in a very simple way.
The corresponding file mon96e.exe (attention: same name as the
normal executable !!!) is obtained by
C:\monitor > do_sim mon96e
This test-exefile could be useful e.g. to getting started with and debug your user-analysis subroutines(see Chapter "User Analysis"), since MC-events are generated imitating the real raw data received from the LIM.
To run the standard Monitor program, just type
C:\monitor > dbos C:\monitor > run77 mon96e.exe
For consequtive runs, you will omit the DBOS loading command. On some machines, a bat-file has been installed, so that e.g. in the shore station you simply have to say
C:\monitor > m or C:\ > m
To run your "private" user-analysis Monitor program
(assumed to be mon96e_u.exe; see Chapter "User-Analysis"
for how to edit and compile-and-link the program),
just type accordingly
C:\monitor\user_ana > dbos C:\monitor\user_ana > run77 mon96e_u.exe
or use the bat-file located in c:\monitor\user_ana
C:\monitor\user_ana > m_u.bat .
An extended menu system will guide you through all histograms-displays and other program features. Just select the menu item, and you will get the corresponding histogram(s). For some items you get an ascii-table (Number of events triggered so far, their trigger rates, and general run information). For "User-Event-analysis" and "Display Chan/Events" the LIM is sending primary event information, instead of precollected histograms.
Most of the histograms and functions are self-explaining by their names. This chapter is very brief, an extended version is in preparation. The most recent changes are explained in detail in chapter "What's new in the 1996 Release".
All histograms can be zoomed, multiple histogram screens allow for picking of individual histograms, storing the graphic information on an oputput file is supported (to obtain a printer hardcopy).
You have access to the histogram submenus, the ascii-run tables, the event- or channel-display, the user-analysis, the LIM_backup procedure, to the AutoPilot mode and to the LIM_backup files (offline-mode). You can acces ascii-help information screens (identical to this description), set various histogram-display options, switch between Online-LIM- and Offline-DISK-Modes and exit the program.
Here you can access the telescope information on Muons, Monopoles, Supernovas and ControlPoints (PMT noise rates). "Strings" in the menu are actually half-strings (i.e. the 4-long-string NT-96 consists out of 8 strings).
Information related to Muons: Number of hits per channel, Number of fired channels per string and for the full array, Amplitude- and Time-distribution per channel (uncalibrated), Time-difference distributions between selected channel-pairs (calibrated), Muon-Trigger rates versus runtime per channels, per string and for the full array.
Information related to Magnetic Monopoles search: e.g. trigger per string and trigger rate versus time.
Quasi-supernova information (summed total counting rate of all channels contributing to the Array Trigger).
Control Points are the various dark counting rates measured for each individual PMT and for each channel ("local rates"). The rates are displayed as function of time, errors observed by the Host-PC while receiving these slow control data are indicated by y-values reaching the maximium of the y-scale (see also chapter "What's new in the 1996 Release").
The Monitor program has been updated for the 1996 Baikal NT-96 configuration (8 half, i.e. 4 long strings: 1/2;3/4;5/6;7/8). Some additional features, described below, have been introduced. The 1996 release is fully backward compatible. In particular this implies for the offline-mode, that all LIM_backup files written since 1993 are correctly read. For the online-mode this means, that operation with all old LIM-board configurations are possible (e.g. with the 1994-LIM-program running on a single LIM-board, as opposed to the 1996-LIM-software running on 2 LIM-boards). In total we are currently handling for NT-96 setup about 660 online-histograms on the LIM and on the Monitor.
Changes introduced since the 1995 Release (Version MON95.C.01) are:
PL2_m.exe,as distributed
with this release in c:\monitor\pl2).
For details on how to generate your own user-analysis
Monitor program,
please see the description in Chapter "User-Analysis".
A simple example with 5 histograms is installed as default user-analysis
with the standard file mon96e.exe.
pmi.exe (needing also printgl.exe), which
may be invoked from the "Plot to File" submenu or
from DOS. Both programs are on the release,
to invoke them from mon96e, they
have to be located in c:\monitor.
See also the detailed help-file available on request
for printgl.exe, as well as the online-help-screens
displayed by mon96e.exe.
N.B.: The "Plot to File" option has been called
"Graphic Print" in releases before 1996.
DBOS (if not yet done)
and run mon96e.exe in debug
mode:
C:\monitor > dbos C:\monitor > run77 mon96e /breakThen you start program execution from within the debugger by
<F6>,
and leave the debugger by
SHFT<F1> (see <F1> for online help).
The standard way to look at muon-event information is to display the histograms, that are filled on the LIM. This set of histograms is filled permanentely during the run, it's guaranteed that the statistics they contain is complete for the entire run.
An additional way of looking at the muon data is to receive the primary events from the LIM and analyze them directly within the Monitor-program. This allows complete flexibility to fill your own histograms (now sitting directly on the Monitor-PC), to debug some events or to check for the occurence of rare strange events etc. This way of event analysis will, of course, leave you with a subset of the whole run-statistics only.
Please note, that running the user-analysis program has no influence
on the performance of the LIM with respect to the standard histograms
collected - whatever analysis program you would run.
In particular, doing a lim_backup even from within the user-analysis
will yield exactly the same standard backup as from mon96e.exe.
The release mon96e.exe contains a simple user analysis example,
which is briefly described in Chapter "Running User Analysis"
below (the corresponding example user-subroutines are in file
c:\monitor\user_ana\us_ana.for).
To get first experience before generating your own analysis, you
might refer to this (in particular, in it's non-LIM test mode, as explained in
chapters "Your Analysis Code" and "Installation Procedure").
To perform your own user-analysis, you will have to generate your private exe-file.
Please start DBOS and move to subdirectory \user_ana:
C:\monitor > dbos C:\monitor > cd user_ana
All initial tests of your analysis programs should be done here
(finally, you might move your "production" exe-file e.g. to C:\monitor).
You have to edit your private analysis-routines,
assumed to be in file my_ana.for (see section
"Your Analysis Code"). To compile-and-link you simply would do
C:\monitor\user_ana > c_u my_ana
This will result in the executable file mon96e_u.exe.
This exe-file can be started by
C:\monitor\user_ana > m_u
or, of course, by
C:\monitor\user_ana > run77 mon96e_u
If you have tested your program, you might want to rename it to save it for further use.
Please note, that as long as your are starting your user-monitor program
from the subdirectory C:\monitor\user_ana, all LIM_Backup-files will
be written to C:\monitor\user_ana\LIM_BACK, and not
to C:\monitor\LIM_BACK (as for the standard Monitor program running from
c:\monitor). So, you might have to move those LIM_Backup-files
that you want to save to the Exabyte tape to the corresponding correct
location.
The user has to supply his private Fortran-file with
two F77-subroutines: user_book and
user_analysis.
An example file containing these two subroutines is us_ana.for.
This demonstrates how to book and fill five histograms, and to printout
relevant event information.
Extensive comments in this example file should make it very easy to
produce your own code.
This example is available as "default" user-analysis in the standard program
mon96e.exe.
If you want to test this without having
access to a full experimental setup (LIM-module, Host-PC and running PMTs),
you can do this using MC-generated events in the test-option of mon96e.exe
(see chapter "Installation Procedure" for this mon96e.exe version,
which will omitt any LIM-communication).
subroutine user_book:
Subroutine user_book is called once at program start to initialize
all your private histograms
(optionally, you can also define your own title-string
for the user-analysis item in the Top-Menu, as demonstrated in us_ana.for).
subroutine user_analysis:
Subroutine user_analysis is called once for each event received from the
LIM.
All information relevant for the array (number of channels, strings,
calibration constants) and relevant for the given event (event number,
number of hitted channles, their times and amplitudes) is available from
common /user_ana/.
Please, create your private Fortran file (e.g. named my_ana.for)
by copying the example file
C:\monitor\user_ana > copy us_ana.for my_ana.for
After editing the file, proceed as explained in the above section
"Getting started User-Analysis" to obtain your exe-file mon96e_u.exe.
Let's assume your private analysis code has been edited and
compiled-and-linked according to the above two sections,
or you just want to play around with the default example for a
user-event-analysis, that is available with the standard
exe-file mon96e.exe.
You enter the Analysis-Menu from the Top-Menu.
If not changed by the user (see above),
this menu entry is called "User Event Analysis" (e.g. in the
example file us_ana.for it is "Userana: example").
The structure of the submenu is as follows:
----- User Event Analysis
|----- Start/Continue User Analysis
|----- Display User Histograms
|----- Save User Histograms
|----- Reset User Histograms
This menu is supporting data-taking (i.e. filling of your histograms), and histogram-handling (displaying, saving to an output file and resetting of histograms). All the user-histograms are not affected by leaving the "User-Analysis"-Menus, e.g. to display some standard muon histograms: returning to display the user-histograms, to save them to a file or to continue taking data, they will essentially be of the same content.
user_analysis is called once. There, you are probably filling your histograms
or making some debugging output.
Before event-reading starts, a help-screen gives you information about the
total event statistics accumulated in your histograms so far. Note, that
your statistics will be cumulative if invoking
this menu item several times
(unless you do reset the histograms, see below).
To stop event-reading from the LIM, you have to press <ESC> and
<RET>. This leaves the event loop and displays the full screen of all your
booked histograms (for details, see next item).
Before the histograms are displayed, a help-screen informs
you about the event statisctics collected in this
run and in total.
usr_mon.out. Previously written files are overwritten, so
please take care about proper renaming of the output file.
The file usr_mon.out can directly be read in in a PAW-session,
or alternativley viewed e.g. by the program pl2_m.exe, being
a modified version of pl2.exe with additional printout of the number
of underflow/overflow entries for each histogram.
user_book at
program start).
Have fun with doing your own analysis.