Opened 10 years ago
Closed 10 years ago
#709 closed defect (fixed)
Resolve issues with excess events
Reported by: | Juergen Reuter | Owned by: | kilian |
---|---|---|---|
Priority: | P0 | Milestone: | v2.2.6 |
Component: | core | Version: | 2.2.5 |
Severity: | blocker | Keywords: | |
Cc: |
Description
Report by the Siegen ATLAS group in the process pp -> bblvlvA. Roughly 50% excess events.
Change History (4)
comment:1 Changed 10 years ago by
Status: | new → assigned |
---|
comment:2 Changed 10 years ago by
OK, there is a massive amount of excess events in the simple process e+ e- => b bbar W+ W-
. The integration is perfect, the f_max values nicely converge. Nevertheless, in event generation the weights almost always overshoot.
There must be a problem with rescaling between integration and event generation. Interesting ...
comment:3 Changed 10 years ago by
Priority: | P1 → P0 |
---|---|
Severity: | major → blocker |
Found the culprit (but not yet the exact cause). Channel weights are not initialized properly when starting event generation. The real impact is unclear.
comment:4 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This is now fixed in r6934.
When a VAMP grid is read, the channel weights have to be recalculated or imported into the MCI record. This was not done in the initialization step of event generation. The problem was probably present in all 2.2 versions, since the MCI abstract data type was introduced.
The visible effect was most prominent in processes with a strongly dominant channel, such as tt production and decay. After the revision, excess events are back to a tolerable (tiny) amount.
Next in line.
I'll have to look for manageable processes where this occurs, and debugging is actually possible ...