Opened 14 years ago
Closed 14 years ago
#408 closed defect (fixed)
Idiosyncrasies when using variables in cuts
Reported by: | sschmidt | Owned by: | kilian |
---|---|---|---|
Priority: | P4 | Milestone: | v2.0.5 |
Component: | core | Version: | 2.0.4 |
Severity: | minor | Keywords: | |
Cc: |
Description
Two subtickets:
1) When using a variable already defined in whizard.nw and changing this variable, the change is not detected and the results stay unchanged. A show(cuts) shows that only the name of the variable appears in the tree of cut expressions, so when checking for a change in the cuts probably only the name is compared but not the value.
cuts = Pt > kTcut [g] kTcut = 15 GeV seed = 0 integrate(uueeg) { iterations = 2:2000 } kTcut = 25 GeV seed = 0 integrate(uueeg) { iterations = 2:2000 }
2) When using a user-defined variable
mykTcut = 15 GeV cuts = Pt > mykTcut [g]
an error is printed and the value is taken to be zero.
I don't know though if constructions like the ones mentioned above are intended to work in sindarin. Especially the first one might be useful for the matching interface.
Attachments (2)
Change History (5)
Changed 14 years ago by
Attachment: | ticket408-1.sin added |
---|
comment:1 Changed 14 years ago by
1) I see no problem with example 1), are you sure that you are using the latest svn version?
2) In example 2) you forgot to declare mykTcut as real.
comment:3 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
My Fault... I only checked with my mymatching-branch, didn't think anything regarding the cuts changed since I created the branch.
Example for part 1)