Opened 8 years ago
Closed 7 years ago
#370 closed defect (fixed)
Crash with "Invalid amlitude" in V+gamma
Reported by: | Johannes Krause | Owned by: | Stefan Hoeche |
---|---|---|---|
Priority: | minor | Milestone: | rel-2.3.0 |
Component: | ME Generator | Version: | 2.2.4 |
Keywords: | Cc: |
Description
I observe some rare crashes in Sherpa for Z+gamma / W+gamma production at MEPS@NLO. The error message is
Sherpa: CS_Gamma::TrialWeight() throws fatal error: Invalid amplitude for ...
This seems to be related to a "zero matrix element" in MCATNLO/Main/CS_Gamma::SingleWeight(). The first issue is that in line 168 zero is returned but in line 121 minus one is expected. However, fixing this does not help since in both cases the weight map "ws" is not filled. This finally causes the "invalid amplitude" crash.
As a workaround one can comment out the "return 0" statement in line 168, when doing so the weight becomes infinity and a new event is requested. It is not clear to me why the matrix element can be zero and if this is a real problem.
The used run card and the complete event output are attached.
Attachments (2)
Change History (6)
Changed 8 years ago by
Attachment: | invalid_amplitude.log added |
---|
comment:1 Changed 8 years ago by
I've just got the same crash with rel-2-2-3 for MC@NLO single-top production after a few thousand events:
Sherpa: CS_Gamma::TrialWeight throws fatal error: Invalid amplitude for 2_3__G__u__t__d__bb
However, with rel-2-2-2 it worked fine. Although the versions are fortunately not very different, I have not spotted anything obvious with a diff between the two branches.
UPDATE: The crash appeared also with rel-2-2-2, only much later (after 200k events).
comment:2 Changed 7 years ago by
Version: | 2.2.1 → 2.2.4 |
---|
I also observe this rare crash in diphoton production and have put two log files showing this behaviour in Sherpa 2.2.0 and 2.2.4 into:
comment:3 Changed 7 years ago by
We should discuss two options:
- If it is Ok that the matrix element from Amegic is zero, then CS_Gamma has to be able to cope with that.
- Or we accept that a NaN appears and the event is being retried.
In both cases we need to remove the fatal_error if me=0.
comment:4 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is fixed in r31342 on rel-2-2-4 (was already fixed on trunk) and will become available in Sherpa >=2.2.5.
log file