dPHI

Bug #1235341 reported by Gabriele Ferretti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadAnalysis 5
Invalid
Undecided
Benjamin Fuks

Bug Description

Hi,

I am still not sure about dPHI... (I am using the 2013-09-12 version, revision 68 in Launchpad.)
What I did is to generate a run with one event :) and check by hand.
I attach the LHE file, never mind the other particles, just look at the photons 4 momentum

a2 = 0.60637959083E+02 -0.35342794180E+02 0.64175521742E+02 0.95102958802E+02
a1 = -0.92401079936E+02 -0.12834023879E+03 0.18221352926E+03 0.24126944836E+03

a1 has pt in the lower left corner of the (x,y) axis. If I understand your conventions that means phi = -2.195
a2 has pt in the lower right corner, phi = -0.5277

in ma5 i input
plot dvPHI(a[1] a[2]) 100 -3.14 +3.14
plot PHI(a[1]) 100 -3.14 +3.14
plot PHI(a[2]) 100 -3.14 +3.14

The plots for PHI(a[1]) and PHI(a[2]) are OK BUT the the plot dvPHI(a[1] a[2]) should give in my opinion
|-2.195 -(-0.5277)| = 1.6673 whereas ma5 gives -2.596

Lastly one minor thing: It seems to me that your default range is 0. 3.14 but it should be -3.14 3.14, maybe you could change it?

Have a nice weekend everyone!
Gabriele

Revision history for this message
Gabriele Ferretti (ferretti-o) wrote :
Revision history for this message
Benjamin Fuks (fuks) wrote :

Hi Gabriele,

The observable dvPHI is the vectorial difference among the two phis. This means that you first take the difference of the two four-vectors and then compute the phi angle of the resulting four-vector.

If you want phi1 - phi2, you need to compute the scalar difference, i.e., you first compute the phi angle of the first four-vector, then the one of the second four-vector, and you calculate the difference between the two results.

Please hence try sdPHI instead of dvPHI. It should work.

For the other minor thing. The default range for sdphi will be changed to (-2pi, 2pi) in v1.1.9, and the one for the scalar sum to (-2pi,2pi), since our default range is (-3.14, 3.14) Thanks for pointing this out.

Cheers,

Benjamin

Changed in madanalysis5:
milestone: none → v1.1.9
status: New → Invalid
assignee: nobody → Benjamin Fuks (fuks)
Revision history for this message
Gabriele Ferretti (ferretti-o) wrote : Re: [Bug 1235341] Re: dPHI
  • main.pdf Edit (240.6 KiB, application/pdf; name="main.pdf")

Hi Benjamin,
Thanks! Silly me!

Since we are on the subject...

One other minor problem is that the captions of some plots have a ">"
instead of a "<".

Just look at the main.pdf attached.
The cuts on ETA(a) are in page 2 and you see that they don't match the
titles on page 6,7,8.
I think it's only the titles, there should be no problem with the actual
cuts, but it might be worth checking.

A second thing you may be able to help me with:
I need to set cuts on the sdPHI between a photon and the *total* missing
PT of an event.
Is there a way to do that without going to expert mode?

Thanks again!

Cheers
Gabriele

On 10/9/2013 11:32 PM, Benjamin Fuks wrote:
> Hi Gabriele,
>
> The observable dvPHI is the vectorial difference among the two phis.
> This means that you first take the difference of the two four-vectors
> and then compute the phi angle of the resulting four-vector.
>
> If you want phi1 - phi2, you need to compute the scalar difference,
> i.e., you first compute the phi angle of the first four-vector, then the
> one of the second four-vector, and you calculate the difference between
> the two results.
>
> Please hence try sdPHI instead of dvPHI. It should work.
>
> For the other minor thing. The default range for sdphi will be changed
> to (-2pi, 2pi) in v1.1.9, and the one for the scalar sum to (-2pi,2pi),
> since our default range is (-3.14, 3.14) Thanks for pointing this out.
>
> Cheers,
>
> Benjamin
>
> ** Changed in: madanalysis5
> Status: New => Invalid
>
> ** Changed in: madanalysis5
> Milestone: None => v1.1.9
>
> ** Changed in: madanalysis5
> Assignee: (unassigned) => Benjamin Fuks (fuks)
>

Revision history for this message
Benjamin Fuks (fuks) wrote :

Hi Gabriele,

Unfortunately, we cannot do anything for the titles since there is no general way to collect various condition pieces. While
  select ETA(a) > -2.5 and ETA(a) < 2.5 means -2.5 < ETA(a) < 2.5 (this is easy to write nicely)
there is nothing one can do for
  reject ETA(a) < -2.5 and ETA(a) > 2.5
Therefore, we will let the titles as they are now.

Cheers,

Benjamin

Revision history for this message
Benjamin Fuks (fuks) wrote :

PS: I know the second condition is silly and always false, but I gave t for the sake of the example.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.