#/**
#*       Example macro for simulating forced firing of the channel discriminators,
#*       such as due to pedestal or TUBii pulser signals.
#*
#*       addforcedhits.mac
#*       Date:           06/02/2022
#*       contact:        T. Kroupova, UPenn
#*/

/run/initialize

# BEGIN EVENT LOOP

# Running the processor with no parameters produces hits at 110 ns
# at all online PMTs
/rat/proc addforcedhits

# Can add multiple instances of the processor to an event
# ech with different parameters
/rat/proc addforcedhits
# To specify time (in ns) of the hits since MC event time = 0
/rat/procset time 200.0


# Specify a full crate where to generate hits - all online channels
# in the crate fire
/rat/proc addforcedhits
/rat/procset time 300.0
/rat/procset crate 1


# Specify a card where to generate hits - all online channels in the card fire.
# Should specify which crate, otherwise it defaults to crate 0
/rat/proc addforcedhits
/rat/procset time 400.0
/rat/procset crate 2
/rat/procset card 3

# Specify a single channel to generate hits
# Should specify which crate and card, otherwise both default to 0
/rat/proc addforcedhits
/rat/procset time 500.0
/rat/procset crate 4
/rat/procset card 5
/rat/procset channel 6


/rat/proc frontend
/rat/proc trigger
/rat/proc eventbuilder
/rat/proc count
/rat/procset update 10

/rat/proc calibratePMT
/rat/proclast outroot
/rat/procset file "addforcedhits.root"

# END EVENTLOOP

# Makes the most sense with the null generator, but any should work
/generator/add null
/generator/rate/set 1

/rat/run/start 10
exit