whizard is hosted by Hepforge, IPPP Durham

Opened 15 years ago

Closed 14 years ago

Last modified 8 years ago

#88 closed task (duplicate)

Validation

Reported by: Juergen Reuter Owned by: ALL
Priority: P1 Milestone: v42-backlog
Component: core Version: 2.0.0alpha
Severity: blocker Keywords: WHIZARD stress testing
Cc:

Description (last modified by ohl)

SM backwards compatibility seems to be problematic. WHIZARD2 right now is not able to give reliable results without cuts, standard cuts are not implemented, and with cuts there seem to be different results between WHIZARD 1 and 2.

It would be useful to have an EXPECT function in the WIZARD language.

Attachments (3)

whizard.sm_proc_01.out (19.7 KB) - added by Juergen Reuter 15 years ago.
WHIZARD 1 run output file for process e1,E1 -> b,B,u,D,U,d
whizard.in (671 bytes) - added by Juergen Reuter 15 years ago.
WHIZARD 1 input file
whizard.2.in (671 bytes) - added by Juergen Reuter 15 years ago.
WHIZARD 1 input file

Download all attachments as: .zip

Change History (20)

Changed 15 years ago by Juergen Reuter

Attachment: whizard.sm_proc_01.out added

WHIZARD 1 run output file for process e1,E1 -> b,B,u,D,U,d

comment:1 Changed 15 years ago by Juergen Reuter

I tried the following process e+ e- -> b bbar u dbar ubar d with the configuration file that can be found in the whizard.in.smext input file in share/test from version r1288 on. I attached the corresponding input file for WHIZARD 1 and the WHIZARD 1 run output which is in perfect agreement with HELAC and SHERPA. Also the whizard.in file for the run is attached. The WHIZARD 2 run follows here as screen output: mW -> 80.418999999999997 wW -> 2.1200000000000001 mZ -> 91.188199999999995 wZ -> 2.4952000000000001 GF -> 1.16639000000000003E-005 me -> 0.0000000000000000 mmu -> 0.10565830000000000 mtau -> 1.7769999999999999 ms -> 0.20000000000000001 mc -> 1.3000000000000000 mb -> 4.7999999999999998 mtop -> 174.30000000000001 wtop -> 1.6000000000000001 mH -> 130.00000000000000 wH -> 4.29000000000000041E-003 alphas -> 9.24999999999999989E-002 sqrts = 360.00000000000000 Beam data (collision):

e- (mass = 0.0000000 GeV) e+ (mass = 0.0000000 GeV) sqrts = 360.0000000000000 GeV

| Integrating process 'sm_proc_01' |=============================================================================| | It Calls Integral[fb] Error[fb] Err[%] Acc Eff[%] Chi2 N[It] | |=============================================================================|

1 100000 1.6720295E+01 6.29E+00 37.63 118.98* 0.10 2 100000 6.6417782E+00 1.99E+00 30.01 94.89* 0.08 3 100000 1.2204299E+01 4.57E+00 37.43 118.37 0.07 4 100000 1.9927258E+01 1.62E+01 81.43 257.49 0.03 5 100000 8.6931468E+00 2.80E+00 32.20 101.84* 0.06 6 100000 1.3546682E+01 4.12E+00 30.45 96.28* 0.05

|=============================================================================|

6 600000 9.0476153E+00 1.39E+00 15.40 119.29 0.05 1.02 6

|=============================================================================| |========================= Results Summary =========================|

sm_proc_01: 9.04761526E+00 +- 1.39E+00 fb

|=============================================================================| | WHIZARD run finished. |=============================================================================|

Changed 15 years ago by Juergen Reuter

Attachment: whizard.in added

WHIZARD 1 input file

Changed 15 years ago by Juergen Reuter

Attachment: whizard.2.in added

WHIZARD 1 input file

comment:2 Changed 15 years ago by ohl

Description: modified (diff)
Summary: Problems with validationValidation

comment:3 Changed 15 years ago by Juergen Reuter

Better formatted output here:

mW -> 80.418999999999997 wW -> 2.1200000000000001 mZ -> 91.188199999999995 wZ -> 2.4952000000000001 GF -> 1.16639000000000003E-005 me -> 0.0000000000000000 mmu -> 0.10565830000000000 mtau -> 1.7769999999999999 ms -> 0.20000000000000001 mc -> 1.3000000000000000 mb -> 4.7999999999999998 mtop -> 174.30000000000001 wtop -> 1.6000000000000001 mH -> 130.00000000000000 wH -> 4.29000000000000041E-003 alphas -> 9.24999999999999989E-002 sqrts = 360.00000000000000 Beam data (collision):

    e- (mass = 0.0000000 GeV) e+ (mass = 0.0000000 GeV) sqrts = 360.0000000000000 GeV

| Integrating process 'sm_proc_01' |=============================================================================| | It Calls Integral[fb] Error[fb] Err[%] Acc Eff[%] Chi2 N[It] | |=============================================================================|

    1 100000 1.6720295E+01 6.29E+00 37.63 118.98* 0.10 2 100000 6.6417782E+00 1.99E+00 30.01 94.89* 0.08 3 100000 1.2204299E+01 4.57E+00 37.43 118.37 0.07 4 100000 1.9927258E+01 1.62E+01 81.43 257.49 0.03 5 100000 8.6931468E+00 2.80E+00 32.20 101.84* 0.06 6 100000 1.3546682E+01 4.12E+00 30.45 96.28* 0.05

|=============================================================================|

    6 600000 9.0476153E+00 1.39E+00 15.40 119.29 0.05 1.02 6

|=============================================================================| |========================= Results Summary =========================|

    sm_proc_01: 9.04761526E+00 +- 1.39E+00 fb

|=============================================================================| | WHIZARD run finished. |=============================================================================| 

comment:4 Changed 15 years ago by Juergen Reuter

No, a second try:

mW -> 80.418999999999997 
wW -> 2.1200000000000001 
mZ -> 91.188199999999995 
wZ -> 2.4952000000000001 
GF -> 1.16639000000000003E-005 
me -> 0.0000000000000000 
mmu -> 0.10565830000000000 
mtau -> 1.7769999999999999 
ms -> 0.20000000000000001 
mc -> 1.3000000000000000 
mb -> 4.7999999999999998 
mtop -> 174.30000000000001 
wtop -> 1.6000000000000001 
mH -> 130.00000000000000 
wH -> 4.29000000000000041E-003 
alphas -> 9.24999999999999989E-002 
sqrts = 360.00000000000000 

Beam data (collision):

e- (mass = 0.0000000 GeV) 
e+ (mass = 0.0000000 GeV) 
sqrts = 360.0000000000000 GeV

| Integrating process 'sm_proc_01' |=============================================================================| 
| It Calls Integral[fb] Error[fb] Err[%] Acc Eff[%] Chi2 N[It] | |=============================================================================|
    1 100000 1.6720295E+01 6.29E+00 37.63 118.98* 0.10 
    2 100000 6.6417782E+00 1.99E+00 30.01  94.89* 0.08 
    3 100000 1.2204299E+01 4.57E+00 37.43 118.37  0.07 
    4 100000 1.9927258E+01 1.62E+01 81.43 257.49  0.03 
    5 100000 8.6931468E+00 2.80E+00 32.20 101.84* 0.06 
    6 100000 1.3546682E+01 4.12E+00 30.45 96.28*  0.05
|=============================================================================|
    6 600000 9.0476153E+00 1.39E+00 15.40 119.29 0.05 1.02 6
|=============================================================================| 
|========================= Results Summary =========================|
    sm_proc_01: 9.04761526E+00 +- 1.39E+00 fb
|=============================================================================| 
| WHIZARD run finished. 
|=============================================================================| 

comment:5 Changed 15 years ago by Juergen Reuter

Milestone: v2.0-betav2.0-final

Since the validation procedure is part of the preparation for the final release, I move this ticket to the final release.

comment:6 Changed 15 years ago by kilian

Type: defecttask

expect is now implemented [1348]. Now the standard tests should use it to detect numerical discrepancies.

comment:7 Changed 15 years ago by Juergen Reuter

As a first observation, there seems to be an factor of 4 in speed between WHIZARD 1 and 2 for a 2 -> 6 process (ILC top signal and background processes). This is not a "truth level" comparison as W2 was compiled with gfortran 4.5.0 with O2 and W1 with ifort 11.1.056 with -O3. My suspicion is that this factor of 4 comes basically from the not yet implemented helicity selection rules which kills probably everything up to roughly a quarter of the combinations.

comment:8 Changed 15 years ago by Juergen Reuter

It looks to be more like an order of magnitude for 2->6 processes :( This is a big, big problem!

comment:9 Changed 15 years ago by Juergen Reuter

TASK 001:

Validate the correctness of the binary STDHEP files written by WHIZARD 2. Maybe Marcus R. could do this!? There are some smaller issues which I do not understand.

comment:10 Changed 15 years ago by ohl

Milestone: v2.0.0finalgolden-classics

comment:11 Changed 15 years ago by Juergen Reuter

Test.

comment:12 Changed 14 years ago by Juergen Reuter

When tickets #229 and #375 are done, all WHIZARD1 features (that have been working in W1) are re-enabled. When they are validated this ticket will be closed.

comment:13 Changed 14 years ago by Juergen Reuter

Well, in principle, the 2->1 processes were also working in W1. So I fear we have to keep this open until that is also implemented and validated.

comment:14 Changed 14 years ago by Juergen Reuter

There are also the s-channel mappings which need to be finished and checked. CS would say there are also the user-defined functions, but they cannot really be validated. And there is the EWA which was incorrect also in WHIZARD1, at least the usage of the EW coupling constants in the structure function. But nevertheless that also is a W1 feature which should be finished for completeness reasons. After all that we can close this ticket, maybe somehow at the end of the year.

comment:15 Changed 14 years ago by Juergen Reuter

Ok, there is one more point, we have to discuss ticket #418 before we can close this ticket.

comment:16 Changed 14 years ago by ohl

Resolution: duplicate
Status: newclosed

only #57 and #375 remain

comment:17 Changed 8 years ago by Juergen Reuter

Milestone: golden-classicsv42-backlog

Milestone renamed

Note: See TracTickets for help on using tickets.