Modify ↓
#130 closed defect (fixed)
EGamma setup: x=1 in SF, TChannelWeight bad momenta
Reported by: | Frank Siegert | Owned by: | Stefan Hoeche |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Unknown | Version: | 1.2.3 |
Keywords: | Cc: |
Description
In the default EGamma example setup the integration leads to the following two kinds of errors:
SF::CalculateWeight : x out of bounds 1 at 17038.3, xrange = 1e-06 ... 0.999999 TChannelWeight: bad momenta!!!! -0.991994 - 0.473135 (0.566092) 1: (35.2969,0,0,35.2969) 2: (35.2969,0,0,-35.2969) 3: (7.91879,0.0321595,6.52771,4.48277) 4: (62.675,-0.0321595,-6.52771,-4.48277)
The SF one goes away if I disable the electron PDF by PDF_SET_2=None
, that might explain why it hasn't appeared before (we didn't use to active electron PDFs by default).
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from support@sherpa-mc.de to Stefan Hoeche |
---|
Note: See
TracTickets for help on using
tickets.
It seems like the combination of ISR handler and beam handler in this setup leads to the problems. Looking at
Phase_Space_Handler::Differential(process,mode)
then the momenta still look fine before thep_isrhandler->BoostInLab
happens:After that they also still seem ok:
Then comes the
p_beamhandler->BoostInLab
which makes them:(which is clearly wrong given that both beam energies are at 250 GeV).