try
{
if (q.T()==0) throw EXCEPTION_WARNING("Energy equal to zero.
Impossible to compute the boost.","",0); setBoostVector(q.X(),q.Y(),q.Z());
}
catch(const std::exception& e)
{ MANAGE_EXCEPTION(e);
MABoost();
but but the division by q.T() is still missing. There is only a check
that q.T() is not 0.
The other bug with (a-b-c).Px() != a.Px()-b.Px()-c.Px(), a,b,c, being
LorentzVectors, is fixed. Thanks a lot!
Regarding my question about event shape observables like aplanarity: Are
they available in madanalysis?
Cheers, Alexander.
Am 19.09.2016 um 18:45 schrieb Benjamin Fuks:
> Hi Alexander,
>
> Thanks for having pointed out this bug. This is now fixed. Can you please check the v1.5beta version of the code,
> https://code.launchpad.net/~ma5dev/madanalysis5/v1.5beta
> and let us know whether everything is now fine. Note that the bug had no impact so far as those methods have never been used before.
>
> Cheers,
>
> Benjamin
>
> ** Changed in: madanalysis5
> Importance: Undecided => Medium
>
> ** Changed in: madanalysis5
> Importance: Medium => High
>
> ** Changed in: madanalysis5
> Status: New => Fix Committed
>
> ** Changed in: madanalysis5
> Milestone: None => v1.5
>
> ** Changed in: madanalysis5
> Assignee: (unassigned) => Eric Conte (eric-conte)
>
Dear Benjamin, dear all,
MABoost includes now
try WARNING( "Energy equal to zero.
setBoostVector( q.X(),q. Y(),q.Z( ));
MANAGE_ EXCEPTION( e);
{
if (q.T()==0) throw EXCEPTION_
Impossible to compute the boost.","",0);
}
catch(const std::exception& e)
{
MABoost();
but but the division by q.T() is still missing. There is only a check b.Px()- c.Px(), a,b,c, being
that q.T() is not 0.
The other bug with (a-b-c).Px() != a.Px()-
LorentzVectors, is fixed. Thanks a lot!
Regarding my question about event shape observables like aplanarity: Are
they available in madanalysis?
Cheers, Alexander.
Am 19.09.2016 um 18:45 schrieb Benjamin Fuks: /code.launchpad .net/~ma5dev/ madanalysis5/ v1.5beta
> Hi Alexander,
>
> Thanks for having pointed out this bug. This is now fixed. Can you please check the v1.5beta version of the code,
> https:/
> and let us know whether everything is now fine. Note that the bug had no impact so far as those methods have never been used before.
>
> Cheers,
>
> Benjamin
>
> ** Changed in: madanalysis5
> Importance: Undecided => Medium
>
> ** Changed in: madanalysis5
> Importance: Medium => High
>
> ** Changed in: madanalysis5
> Status: New => Fix Committed
>
> ** Changed in: madanalysis5
> Milestone: None => v1.5
>
> ** Changed in: madanalysis5
> Assignee: (unassigned) => Eric Conte (eric-conte)
>