whizard is hosted by Hepforge, IPPP Durham

Opened 10 years ago

Closed 9 years ago

#658 closed defect (fixed)

Rescan command fails with weighted events

Reported by: Juergen Reuter Owned by: kilian
Priority: P1 Milestone: v2.2.4
Component: core Version: 2.2.2
Severity: normal Keywords:
Cc:

Description

Reported by FB.

Attachments (2)

foo.sin (486 bytes) - added by fbach 10 years ago.
ticket658.sin (567 bytes) - added by kilian 9 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 10 years ago by fbach

Given a weighted event sample and a corresponding analysis with histograms (cf. foo.sin), if you rescan the sample and rerun the analysis, the original event weights are simply used again, thus producing identical histograms after rescanning.

Changed 10 years ago by fbach

Attachment: foo.sin added

comment:2 Changed 10 years ago by Juergen Reuter

Milestone: v2.2.3v2.2.4

comment:3 Changed 9 years ago by kilian

Milestone: v2.2.5v2.2.4
Priority: P3P1
Status: newassigned

I'll look into this. The alt values in the LHE output appear to reflect the change of PDF, so how should this be handled regarding analysis ...

comment:4 Changed 9 years ago by kilian

OK, the sample Sindarin file uses alt_setup, and the behavior is correct. In the absence of array constructs within Sindarin expressions, it is not possible to plot the alternate weight. It is written to the event file as required, so no problem there.

However, I don't get a recalculation when the primary environment is changed. This is probably incorrect.

Changed 9 years ago by kilian

Attachment: ticket658.sin added

comment:5 Changed 9 years ago by kilian

Resolution: fixed
Status: assignedclosed

First of all, the sample input file contains several errors (or misconceptions) about the way the rescan command works. The alt_setup clause works correctly, but the calculated alternative weights appear only in the LHEF output, they can't be used for the internal analysis.

What does work is a straightforward rescan without alt_setup. At least, after clearing up the code and fixing various things, r6454. One has to set update_sqme and update_weight, and one has to make sure that the analysis definitions are valid during the rescan. I attach an updated example file.

Note: See TracTickets for help on using tickets.