Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numerical instabilities in "isobarAmplitude::gjTransform" #91

Open
suhlatwork opened this issue May 18, 2015 · 3 comments
Open

Numerical instabilities in "isobarAmplitude::gjTransform" #91

suhlatwork opened this issue May 18, 2015 · 3 comments
Labels

Comments

@suhlatwork
Copy link
Contributor

"isobarAmplitude::gjTransform" never checks whether the beam and X Lorentz-vectors actually span a production plane or are collinear.

A proper solution probably has to handle two cases:

  • beam and X are collinear and the three-vector component is not equal to zero
  • beam and X are collinear with a zero three-vector component

Case one can probably not be handled without spoiling theta_GJ and phi_TY, the second case can probably be handled by simply not performing any transformation (as X already appears to be in its centre-of-mass system) and relying on the user to have taken care that those two angles still are correct. However, the check for equal to zero needs to include some numerical margin, as typically X is calculated from its daughters.

This is actually a real problem, as the "phaseSpaceIntegral" class uses a non-interaction vertex which can only provide equal beam and X Lorentz-vectors to calculate the amplitudes.

@suhlatwork suhlatwork added the bug label May 18, 2015
@bgrube
Copy link
Contributor

bgrube commented May 18, 2015

Oops, but how does phaseSpaceIntegral handle the t' dependence?

@suhlatwork
Copy link
Contributor Author

For the pure phaseSpaceIntegrals (without taking acceptance into account) there should be no t' dependence?

@bgrube
Copy link
Contributor

bgrube commented May 18, 2015

Yes, I was confusing it with the phase-space integral we use for the likelihood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants