whizard is hosted by Hepforge, IPPP Durham

Opened 14 years ago

Closed 14 years ago

Last modified 7 years ago

#172 closed enhancement (duplicate)

Phase space tuning

Reported by: kilian Owned by: kilian
Priority: P3 Milestone: v42-backlog
Component: core Version: 2.0.0beta
Severity: normal Keywords:
Cc:

Description

W2 produces more channels than W1, which may be good or bad. Implement a switch and run tests to decide the default behavior.

Look for other places to improve (or repair) phase-space setup.

Change History (15)

comment:1 Changed 14 years ago by kilian

Status: newassigned
Type: defectenhancement

comment:2 Changed 14 years ago by Juergen Reuter

Priority: P2P1
Severity: normalblocker

For e+ e- -> b bbar u ubar s sbar the phase space generation is taking more than 45 min, at least, or does not even stop an a standard laptop.

comment:3 Changed 14 years ago by Juergen Reuter

Milestone: v2.0-rc2v2.0-rc1

This is a no-go, sry.

comment:4 Changed 14 years ago by Juergen Reuter

I have to check whether WHIZARD is doind anything at all...

comment:5 Changed 14 years ago by Juergen Reuter

WHIZARD stays for ages in cascade_set_generate.

comment:6 Changed 14 years ago by kilian

Component: configurecore
Milestone: v2.0-rc1v2.0-rc2
Priority: P1P2
Severity: blockernormal

I agree that the mentioned problem must be solved, but this is #171. Exchanging the two.

comment:7 Changed 14 years ago by kilian

Milestone: v2.0-rc2v2.0final
Priority: P2P3

If everything works, nothing to be done here. Just be aware that unexpected failures for processes require some work here.

comment:8 Changed 14 years ago by Juergen Reuter

Thorsten and his diploma student reported a problem with the phase space, regarding a discrepancy when switching on cuts. The discrepancy between W1 and W2 amounts to per cent errors between 5 and 10. Please, the Wurzburg people, provide us with the details (and if possible with a solution muharhar).

comment:9 Changed 14 years ago by ohl

Milestone: v2.0.0finalgolden-classics

comment:10 Changed 14 years ago by Juergen Reuter

Here, we are still waiting for the people from Wuerzburg to confirm any differences they claimed to have found between W1 and W2.

*

What also belongs here is to include benchmarking between W1 and W2 which CS promised to do.

comment:11 Changed 14 years ago by kilian

Currently, the groves are too large, they do not distinguish flavor in (massive) s-channel resonances. Should separate them, although it might not be that important.

comment:12 Changed 14 years ago by kilian

The previous point is addressed in r2508.

comment:13 Changed 14 years ago by Juergen Reuter

Another point we are still awaiting is the performance comparison with WHIZARD 1 (to be done by CS) as well as a general profiling. If there are no further points, I would suggest to close this ticket and open special issue tickets if there are dedicated problems.

comment:14 Changed 14 years ago by ohl

Resolution: duplicate
Status: assignedclosed

see #329, #358

comment:15 Changed 7 years ago by Juergen Reuter

Milestone: golden-classicsv42-backlog

Milestone renamed

Note: See TracTickets for help on using tickets.