#123 closed defect (fixed)
DecayOS throws NaNs with Amegic's integrator
Reported by: | Frank Siegert | Owned by: | support@sherpa-mc.de |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Unknown | Version: | 0.trunk |
Keywords: | Cc: |
Description (last modified by )
Using DecayOS with Amegic currently leads to a flood of warnings during integration. This only seems to be the case for proton-proton setups like below, if the initial state is changed to e+e- it works.
(run){ OUTPUT = 2 EVENTS=1 FRAGMENTATION = Off BEAM_1 = 2212 BEAM_ENERGY_1 = 3500 BEAM_2 = 2212 BEAM_ENERGY_2 = 3500 ME_SIGNAL_GENERATOR=Amegic }(run) (processes){ Process : 93 93 -> 24[a] -24[b] DecayOS : 24[a] -> -11 12 DecayOS : -24[b] -> 13 -14 End process }(processes)
Attachments (0)
Change History (5)
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
The problem originates from a wrong spmin in the ISR integrator. In commit r16020 the treatment of cuts has been changed, in consequence Phase_Space_Handler.C the following change was made:
@@ -111,7 +108,6 @@
return 0;
} if (m_nin>1) {
- InitCuts();
m_smin=ATOOLS::Max(sqr(p_process->ISRThreshold()),p_cuts->Smin());
} m_initialized=1;
when including the call of InitCuts() again everything looks nice and consistent. Can the one that modified the cut handling have a look please. I can't judge if this line disappeared by mistake or if some other routine isn't doing its supposed job correctly.
Steffen
comment:4 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thank you for finding the problem, Steffen. It should be solved with trunk r16496.
the commit under question obviously is r16020, the merger with the nlome's branch. i will have a look if I am able to pin down the problem further.