Add EvtEtaLLPiPi model for eta' -> l l pi pi decays (l = e or mu), for https://phab.hepforge.org/T109.
Details
- Reviewers
kreps tlatham - Maniphest Tasks
- T109: New EvtGen model for eta' -> mu mu pi pi or e e pi pi decays
- Commits
- rEVTGENb4c49c7a30a2: Add EvtEtaLLPiPi model.
Model has been tested using testDecayModel (in the jsonTest branch).
Diff Detail
- Repository
- rEVTGEN evtgen
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Hi @jback, sorry it's taken me so long to review this.
You can find here some technical points.
I'll try to compare the physics against the referenced paper next week, although I guess this was checked during the LHCb review?
You mention also testing it using testDecayModel but I can't find the json file(s) for this model. Could you include them in the next revision?
EvtGenModels/EvtEtaLLPiPi.hh | ||
---|---|---|
31 | Can you please run clang-format (preferably version 10.0.0) on these few files when submitting the next version? | |
History.txt | ||
19 | Thanks for remembering to update this file! I shall also mention this in the CONTRIBUTING docs. | |
src/EvtGenModels/EvtEtaLLPiPi.cpp | ||
56 | Would be better to give these values in the header. |
I'll try to compare the physics against the referenced paper next week, although I guess this was checked during the LHCb review?
Yes, Aleksei checked that the code changes produced distributions that matched the plots shown at the Gauss simulation meeting:
https://indico.cern.ch/event/876000
Relevant comment in code review:
https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/626#note_3723807
The plots looked OK for my tests as well.
You mention also testing it using testDecayModel but I can't find the json file(s) for this model. Could you include them in the next revision?
I've added the json files to the jsonTest branch: test/jsonFiles/EtaEEPiPi.json and EtaMuMuPiPi.json. This revision does not include the json testing code.
History.txt | ||
---|---|---|
19 | Have added maniphest and differential links for code review in the history file, since version 2.0.0. |