whizard is hosted by Hepforge, IPPP Durham

Opened 14 years ago

Closed 14 years ago

#401 closed defect (fixed)

Cuts not applied to factorized processes

Reported by: dwiesler Owned by: jreuter
Priority: P3 Milestone: v2.0.5
Component: interfaces Version: 2.0.4
Severity: normal Keywords: sindarin syntax cuts
Cc:

Description

The attached example demonstrates, that cut statements (on final state particles) are not applied, if the process in question is factorized to production and decay. This is easily circumvented by putting an additional if statement in the analysis environment as in the example, but I'm unsure, if this is intended or not. It may confuse the enduser in that given cuts are not applied (in the special case of factorization) and thus it should at least be mentioned in the manual somehow.

Attachments (2)

fudge.sin (809 bytes) - added by dwiesler 14 years ago.
example sindarin file
fudge.pdf (17.8 KB) - added by dwiesler 14 years ago.
example pdf showing the missing cut on pt

Download all attachments as: .zip

Change History (6)

Changed 14 years ago by dwiesler

Attachment: fudge.sin added

example sindarin file

Changed 14 years ago by dwiesler

Attachment: fudge.pdf added

example pdf showing the missing cut on pt

comment:1 Changed 14 years ago by Juergen Reuter

Milestone: v2.0.5v2.0.6

comment:2 Changed 14 years ago by Juergen Reuter

Milestone: v2.0.6v2.0.5

This should maybe be fixed before release 2.0.5.

comment:3 Changed 14 years ago by Juergen Reuter

What do we do with this one? Just docu, or is there a possibility to find a solution?

comment:4 Changed 14 years ago by kilian

Resolution: fixed
Status: newclosed

The 'cuts' expression should apply to the hard subprocess, its main use is to make the cross section finite. It would be confusing to apply it to the generated events, again.

I added a 'selection' expression. This is applied only to simulated events (so the matrix element has already been evaluated), where cuts have already been applied. It determines whether an event should be analyzed and/or written to external file. Since the analysis expression can contain conditionals, the rationale for the new feature is mainly to control which events are written to external files.

The 'raw' event files are not affected (all events are there), and events that fail selection will nevertheless count for 'n_events'. The advantage is that one can change the selection without redoing event generation. The disadvantage is a potential waste of resources.

Done in r3196.

Note: See TracTickets for help on using tickets.