Our first reading comes from the Book of Resolution, Chapter 1, Verse 1:

      "Blessed are those that simulate without GEANT."

Some quick recommendations for getting started with VIKAR 4.4 (2020-08-08)

I recommend the following:

Make a vikar directory, and extract the tar into it. It should give you two
directories - ./source and ./detectors

In ./source try making vikar (you may need to edit the makefile to point to
your fortran compiler (it's in f77; and thus, the sins of the father are
visited upon the sons). It should be compilable with gfortran and g77. If you
make correctly, copy the executable to /usr/bin, or to whatever directory you
happen to find exhilarating at the time.

The first time you run vikar, it will ask you a huge stack of questions; get
them right, and it will run a simulation. It will ask you if you want an
input file to be generated; say yes, unless you like typing all these answers
into a terminal each time you run. It will also need directing to some
detector setup files; I keep these in the ./detectors directory, as they get
used for different simulations, and it keeps them from the clutter of the
output files. It will generate tens of output files, each labelled out_XXXXX.dat
(typically out_eject_XXXXXX.dat for ejectiles, or out_recoil_XXXXXX.dat for recoils).

Plot them for scatter plots of the data, and histograms of the Q value spectra.

Once you have a VIKAR input file created (eg in.Sn132dp), you can make alterations to this file
and run the code again by piping the input file into vikar, e.g.

$  vikar < in.Sn132dp


Go in peace to love and serve the tea.

------
Evil Dr Pain (2020-01-22)
