Opened 11 years ago
Closed 11 years ago
#276 closed defect (fixed)
RootNTuple output and read-in inconsistent
| Reported by: | Steffen Schumann | Owned by: | Stefan Hoeche |
|---|---|---|---|
| Priority: | major | Milestone: | rel-2.1.0 |
| Component: | Unknown | Version: | 0.trunk |
| Keywords: | Cc: |
Description
Dear all,
When reading in NLO events via RootNTuples the generated/calculated cross section does not agree with the original one that generated the NTuple file. I attach a simple run card to see this. When generating the sample first, the xsec is 259pn, when reading it in again it says 304pb. Analysing the events with Rivet it seems as this is not just a flat normalization problem.
Any help with that is appreciated.
Cheers, Steffen
Attachments (1)
Change History (3)
Changed 11 years ago by
| Attachment: | Run_NLO.dat added |
|---|
comment:1 Changed 11 years ago by
| Owner: | changed from support@sherpa-mc.de to Stefan Hoeche |
|---|
This works just fine if you separate the different NLO parts and put them in different runcards (which is what's typically done in BlackHat etc).
comment:2 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is fixed in r22423. You still cannot run BVI and RS at once, but I think this should be a minor issue because they have different phase space anyway.
run card