WIP - Add sub- thresold pdf#59
Open
petitcactusorange wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am working on adding a sub-threhold PDF for Lambda (1405)--> pK. I started from the
RooBreitWignerand created aRooSubThreshold. The formula I used to modify the effective mass is based on Equation 38 from the Laura++ document arXiv:1711.09854. I realised looking at the parameter ofRooBreitWignerare only for mesons, I will update this for baryons in a second stage.However to be able to test it I am running into some difficulties. In RapidSim there are a couple of sanity kinematics checks which are performed in
RapidDecay.ccwhich don't allow me to test this configuration.Could you please tell me what's the best and safest way to work around that ?
Furthermore, the
RooSubThreholdrequires not only information from the two children particles, but also the parent and the third child. I see inRapidParticleData.ccthat there is some shuffling of the IDs I was wondering if this is something I should pay attention too when accessing the mass of the third particle ?