If you would like to project the generated events directly into histograms, you should choose the option "histo" in the input file "parameter.indat" and define your histograms in the file "param_histo.indat".
In this file, you can define cuts on the rapidity and transverse momentum of the photon and the jet. Note that you have two possibilities to define the jets: Either already at integration level when making the grid (in this case choose the option for 'jet' in the file "parameter.indat" and also define your cuts on the jet there), or only at the histogrammation level. In the latter case you choose the option for 'inclusive' in "parameter.indat" and choose your jet algorithm and cuts only in the file "param_histo.indat". In this way, the cuts will be applied when the histograms are filled. But note that you may loose many events if you apply severe cuts. SPRING will warn you if the number of misgenerations becomes big. In this case it is recommended to redo the grid with the corrresponding cuts.
In the second part of "param_histo.indat",
you can define the histograms you would like to be produced.
You can define histograms with equidistant or non-equidistant bins.
There is also the possibility to specify several additional cuts
for each histogram.
Further details are given in the file
"param_histo.indat" itself.
There is a certain predefined set of observables which can be histogrammed.
These are
If you want to define new observables, you have to define them in the Fortran file "histo_selection.f" in the directory "src/histo". But note that the script "start.pl" also has to be modified accordingly.
A summary of the cuts and histograms which have been defined will be
written to the file "histoNameHisto.outdat".
The resulting *.dat files for the histograms will be stored in the
directory "pawres".
Note that 'NLO' in the definition of the histograms means 'Born + higher orders', i.e. your histogram represents already the sum of leading order and higher order contributions.