PWGHF: beauty production with natural decay at forward rapidity#2353
PWGHF: beauty production with natural decay at forward rapidity#2353NicoleBastid wants to merge 3 commits into
Conversation
add a new .cfg for natural decay with PYTHIA8 Mode 2
new .ini file for beauty with natural decay at forward rapidity
.C file for beauty with natural decay at forward rapidity
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
+async-label async-2024-pp-apass1 |
github-actions
Bot
added
the
async-2024-pp-apass1
|
Dear @NicoleBastid , thanks a lot for the work! It looks fine for me. I just have a minor question, as mentioned in the review. I am not sure if you want to further constrain the generator triggered on the desired hadron. But if not, I think we can just merge it. And the |
| return 1; | ||
| } | ||
| std::cout << "#muons: " << nMuons << "\n"; | ||
| std::cout << "#muons in acceptance: " << nMuonsInAcceptance << "\n"; |
There was a problem hiding this comment.
Hi @NicoleBastid , do you have any expected numbers of these muons and those in acceptance?
| ### The external generator derives from GeneratorPythia8. | ||
| [GeneratorExternal] | ||
| fileName=${O2DPG_MC_CONFIG_ROOT}/MC/config/PWGHF/external/generator/generator_pythia8_gaptriggered_hf.C | ||
| funcName=GeneratorPythia8GapTriggeredBeauty(4, -4.3, -2.2) |
There was a problem hiding this comment.
I see you have the debug output about the nMuonsInAcceptance in the test macro. As you may know, it is also possible to constrain the desired hadron within the given rapidity range in the GeneratorPythia8GapTriggeredBeauty. If that's what you want, one could also trigger based on the hadronPdgList. But I am not sure if this has been used before.
2 participants
new .ini, .cfg and .C files for beauty production at forward rapidity with natural decay