p19.L3.06 (post shutdown Oct 2007)
The L3TMuon tool acquired a new parameter: vertexrefset
Muon L3TMuon(
tooltype="physics",
vertexrefset=NONE, <----- add this line to keep your
level3.sim file equivalent to p19.L3.05a
muontrackrefset=MUO_LOCAL,
centralmatchrefset=NONE,
muocalmatchrefset=NONE)|
You will probably have more than one instance of L3TMuon in your level3.sim
file. Make sure you update *all* of them. The order in which the parameters
appear matters !
Unfortunately the muon filter (L3FMuon) also aquired a new parameter:
zcut, which is |z_pvtx - z_muon| (i.e. force the muon to come from the
vincinity of the primary vertex).
To edit this search for all instances of
CentralMatchReq=TRUE
and replace this with the string
CentralMatchReq=TRUE zcut=-1.0
then search for
CentralMatchReq=FALSE
and replace it with
CentralMatchReq=FALSE zcut=-1.0
(a negative value for zcut indicates the trigger to ignore this cut)
If you want to use this new option (e.g. to be able to replace/relax an
isolation requirement) you can add a vertex tool (e.g. vertexrefset=PrVTX3
for high lumi tools, PrVTX_Z_TRK for lower lumi) and then cut in the filter
(e.g. zcut=5.0). You need to make sure that whatever vertex tool you are
using, it must be defined in your level3.sim file *before* you attempt to
include it in the muon tool. Do not use a vertex tool with a local (i.e.
centralmatchrefset=NONE) muon tool. You'll waste copious amount of CPU and the
results will probably be meaningless. If you try to cut |z_pvtx - z_muon| in
the filter and the vertex tool hasn't run, TrigSim will core dump (and
rightly so). Unfortunately so far I have not been able to get it to print
out a sensible error message before doing so, but if you see mysterious
crashes, please check your level3.sim file for typos.