whizard is hosted by Hepforge, IPPP Durham

Opened 14 years ago

Closed 14 years ago

#321 closed defect (fixed)

Cross sections are zero if compiled with nagfor -O2

Reported by: sschmidt Owned by: ALL
Priority: P1 Milestone: v2.0.2
Component: configure Version: 2.0.1
Severity: critical Keywords: nagfor compiler
Cc:

Description

W2 only gives zeros as cross sections if compiled with nagfor and FCLAGS="-O2"

| Integrating process 'eedd':
|=============================================================================|
| It      Calls  Integral[fb]  Error[fb]   Err[%]    Acc  Eff[%]   Chi2 N[It] |
|=============================================================================|
|=============================================================================|
   1          0  0.0000000E+00  0.00E+00    0.00    0.00    0.00
|=============================================================================|
n_events =  1
?rebuild_events = true
$sample = "shower"
| Initializing simulation for processes eedd:
| Simulation mode = unweighted, event_normalization = '1', unpolarized_events
******************************************************************************
*** ERROR: Simulation: sum of process integrals must be positive; skipping
******************************************************************************

I'm using nagfor 5.2(724) on 32bit Linux.

The problem first appeared somewhere between r2465 and r2475, right now trying to spot the guilty one.

This probably is a compiler bug, but should be mentioned somwhere.

Change History (3)

comment:1 Changed 14 years ago by sschmidt

As a small update: r2465 works normally, r2469 gives only zeros, the revisions in between don't compile.

comment:2 Changed 14 years ago by Juergen Reuter

Milestone: v2.0.3v2.0.2
Priority: P3P1
Severity: majorcritical

This is critical. WK, this happened (if SS is correct) through your splitting of command/integration/simulation modules.

comment:3 Changed 14 years ago by kilian

Resolution: fixed
Status: newclosed

was unrelated to optimization: in integrate_init_iterations a flag was not initialized properly, just happened to be .false. in the -O2 case [2531].

Note: See TracTickets for help on using tickets.