#12 closed defect (invalid)
warnings and error messages during event generation
Reported by: | niegel@cern.ch | Owned by: | support@sherpa-mc.de |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | Unknown | Version: | 1.0.11 |
Keywords: | Cc: |
Description
Hi Sherpa Team,
I have three questions concerning event generation with Sherpa. I'm responsible for the SherpaInterface to the CMS Software framework.
Why takes the loading of libraries before event generation in case of processes containing a lot of feynman diagrams e.g. W+4jets 4 hours and more, Also if Process and Result directory are present? What kind of calculation are done during this "loading"
Maybe I missed it in the manual, but is Sherpa able to produce/read LHE-files (Les Houches Event) ?
What is the meaning of this error messages? Is it crucial? Does it mean, that that the generated event is corrupt?:
ISR_Handler::MakeISR(..): y out of bounds.
y_{min}, y_{max} vs. y: -1.70588, 1.70588 vs. -2.47115
%MSG-i FwkReport: main_input:source 03-Mar-2008 20:57:59 CET Run: 1 Event: 98 Begin processing the 99th record. Run 1, Event 99 %MSG Multi_Channel::GeneratePoint(..): (0xb155870) No channel selected.
disc = 0.538919, sum = nan
Multi_Channel::GeneratePoint(..): (0xb155870) No channel selected.
disc = 0.375269, sum = nan
Multi_Channel::GeneratePoint(..): (0xb155870) No channel selected.
disc = 0.996714, sum = nan
Multi_Channel::GeneratePoint(..): (0xb155870) No channel selected.
disc = 0.901054, sum = nan
Multi_Channel::GeneratePoint(..): (0xb155870) No channel selected.
disc = 0.670741, sum = nan
Thank you very much in advance,
Martin Niegel
Attachments (0)
Change History (5)
comment:1 Changed 17 years ago by
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 Changed 16 years ago by
before event generation in case of processes containing a lot of feynman diagrams e.g. W+4jets 4 hours and more, Also if Process and Result
comment:4 Changed 13 years ago by
Milestone: | → rel-old |
---|
Answered in email conversation (the errors seem to appear only in the CMS interface; debugging there).