#267 closed defect (fixed)
Properly document the semantics of event weights
Reported by: | Juergen Reuter | Owned by: | Juergen Reuter |
---|---|---|---|
Priority: | P2 | Milestone: | |
Component: | documentation | Version: | 2.0.0rc3 |
Severity: | major | Keywords: | event weights |
Cc: |
Description
Weighted events do not give the expected behaviour -- namely, being between 0 and 1 for the events files. This has been destroyed in r2187. Why???
Change History (12)
comment:1 Changed 15 years ago by
Component: | core → documentation |
---|---|
Priority: | P1 → P2 |
Severity: | blocker → major |
comment:2 Changed 15 years ago by
Summary: | Weighted events broken → Properly document the semantics of event weights |
---|
comment:3 Changed 15 years ago by
I would also prefer the choice 4. over 2. And agree on a proper documentation. This is probably our biggest task for the next two weeks.
comment:4 Changed 15 years ago by
Owner: | changed from ALL to kilian |
---|---|
Status: | new → assigned |
Weighted events are actually broken in W2: channel selection doesn't work. I'll fix this first.
comment:6 Changed 15 years ago by
r2192 implements all options that Thorsten has listed, so it's now the user's choice.
The default is $event_normalization = "auto" which normalizes unweighted events to unity, and weighted events to the cross section, i.e., choices 1 and 2.
IMHO, 1 and 2 are preferable over 3 and 4, because (1) they are required in the LHEF standard, and (2) the normalization is independent of the number of events, so event samples can be cut or expanded without normalization change.
In fact, when choosing 3 or 4, appending to an event file should be an error, but I haven't implemented this.
Comments?
comment:7 Changed 15 years ago by
Milestone: | v2.0-rc4 → v2.0.0final |
---|
comment:8 Changed 15 years ago by
Owner: | changed from kilian to Juergen Reuter |
---|---|
Status: | assigned → new |
I will try and write up some Easter bunny up today such that WK can concentrate on his technical stuff.
comment:9 Changed 15 years ago by
Status: | new → assigned |
---|
comment:10 Changed 15 years ago by
Most things done in r2262. There are just a few things in the SINDARIN chapter missing, and a few remarks about the options of simulate in the event generation chapter. Will do that today. Details about the different event formats should be in the manual, too, but for me are part of the general manual ticket.
comment:11 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Documentation done in r2265.Closing.
As I see it, there are four choices (<...> denotes average)
neither of which guarantees that 0 <= w <= 1 (which is one of the motivations for weighted events, btw.). WK has implemented a choice between 1. and 2. using the variable normalize_weight. I would prefer 4. over 2., but this is trivial and only needs to be documented properly.