Modify ↓
#98 closed defect (fixed)
ME+PS scale setting broken for unweighted events
Reported by: | Frank Siegert | Owned by: | Stefan Hoeche |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Unknown | Version: | 1.2.2 |
Keywords: | Cc: |
Description (last modified by )
Event generation takes significantly longer if previously stored integration results are read-in instead of integrated anew. I am attaching a run card and two corresponding log files, one for event generation directly after integration (4829 s / 5000 events) and one for event generation after reading in the results (14024 s / 5000 events).
The setup is:
- Z+0,1,2,3,4 jets, I can't see a similarly drastic difference for Z+0,1,2,3 jets and if I remember correctly also not for exclusive Z+4 jets (but that one I am trying to reproduce currently).
- Unweighted events (I'm currently running a test whether the same happens for weighted events)
- Enhance factors for the higher multis (that's why the events take so long in first place)
- Comix with multi-threading (in both runs)
It might be interesting to note the development of the time estimate in the read-in log, as there seems to be some kind of optimisation happening in the beginning, which doesn't seem to be present in the run with integration?
Attachments (3)
Change History (7)
Changed 14 years ago by
Changed 14 years ago by
Attachment: | integrate.log added |
---|
Changed 14 years ago by
Attachment: | readin.log added |
---|
comment:1 Changed 14 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 14 years ago by
Priority: | major → critical |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Summary: | Event generation after reading integration results very inefficient → ME+PS scale setting broken for unweighted events |
comment:3 Changed 14 years ago by
Milestone: | → rel-1.2.3 |
---|
Note: See
TracTickets for help on using
tickets.
This problem was due to a bug in the METS scale setter, leading to wrong renormalization scales in setups using ME+PS merging. It is solved by r15955 and a patch is provided on the rel-1.2.2 downloads page.