[Rivet] MC_HJETS and MC_HINC using ZFinder

[Hunt, Julia]

Dear Rivet experts,

I stumbled upon two lines concerning the use of the ZFinder in the two analyses MC_HJETS and MC_HINC. In these analyses, ZFinder is abused to get a Higgs boson.

ZFinder.hh gives the following constructor:

Rivet-2.2.0:
00036     ZFinder(const FinalState& inputfs,
00037             const Cut & cuts,
00038             PdgId pid,
00039             double minmass, double maxmass,
00040             double dRmax=0.1,
00041             ClusterPhotons clusterPhotons=CLUSTERNODECAY,
00042             PhotonTracking trackPhotons=NOTRACK,
00043             double masstarget=91.2*GeV);

Rivet-1.9.0:
00037    ZFinder(const FinalState& inputfs,
00038            double etaMin, double etaMax,
00039            double pTmin,
00040            PdgId pid,
00041            double minmass, double maxmass,
00042            double dRmax, bool clusterPhotons, bool trackPhotons,
00043            double masstarget=91.2*GeV, bool useDecayPhotons=false);


And the analyses don't seem to change the default masstarget:
Rivet-2.2.0:
MC_HINC.cc:
00025       ZFinder hfinder(FinalState(), cut, PID::TAU, 115*GeV, 125*GeV, 0.0, ZFinder::NOCLUSTER);
MC_HJETS.cc:
00028       ZFinder hfinder(FinalState(), cut, PID::TAU, 115*GeV, 125*GeV, 0.0, ZFinder::NOCLUSTER);

Rivet-1.9.0:
MC_HINC.cc:
00026      ZFinder hfinder(fs, -3.5, 3.5, 25.0*GeV, TAU, 115.0*GeV, 125.0*GeV, 0.0, false, false);
MC_HJETS.cc:
00027      ZFinder hfinder(fs, -3.5, 3.5, 25.0*GeV, TAU, 115.0*GeV, 125.0*GeV, 0.0, false, false);

So it seems like the two analyses use the Z mass as a target when looking for a Higgs boson.
Could there be any arguments against changing this masstarget parameter in the MC_HJETS and MC_HINC analyses?

Best regards,
Julia Hunt