Opened 15 years ago
Closed 15 years ago
#284 closed task (fixed)
Avoid name clashes between coupling constants and wave functions
Reported by: | Juergen Reuter | Owned by: | Juergen Reuter |
---|---|---|---|
Priority: | P3 | Milestone: | v2.3.1 |
Component: | omega | Version: | 2.0.0rc3 |
Severity: | normal | Keywords: | invalid code |
Cc: |
Description
The test file mssm_ext-bb.sin does NOT compile:
libtool: compile: gfortran -c -I/Users/reuter/.whizard/lib/whizard/mod/models -I/Users/reuter/local/lib/whizard/mod/models -I/Users/reuter/local/include/omega -I/Users/reuter/local/lib/whizard/mod/whizard-core -I/Users/reuter/local/lib/whizard/mod/misc -g -O2 prc1.f90 -fno-common -o .libs/prc1.o prc1.f90:121.11: a0_12, h0l_12, h0h_12 1 Error: Symbol 'a0_12' at (1) already has basic type of COMPLEX prc1.f90:309.56: d3_1_d3b__1neu1neu1 = d3_1_d3b__1neu1neu1 + h0h_12*( & 1
Change History (4)
comment:1 Changed 15 years ago by
Owner: | changed from ohl to Juergen Reuter |
---|---|
Status: | new → assigned |
comment:2 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
It was a double declaration of variables in the process files and the generated source code. I renamed the variables in the parameter model files. Should be solved now (I guess there will not be a conflict with vector0_ij, 0 < i,j < 5. Closing.
comment:3 Changed 15 years ago by
Milestone: | v2.0.0final → v2.1 |
---|---|
Priority: | P1 → P3 |
Resolution: | fixed |
Severity: | blocker → normal |
Status: | closed → reopened |
Summary: | Splitting amplitudes lead to invalid code → Avoid name clashes between coupling constants and wave functions |
Type: | defect → task |
Name clashes can be avoided by making sure that coupling constants and wave functions don't share common prefixes. Add such a check to O'Mega's Fusion module.
comment:4 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Was still a problem for me. Fixed in r2288, by adding prefixes to O'Mega variables
- owf_ for wave functions
- oks_ for keystones
these must never be used by coupling constants.
Note: See
TracTickets for help on using
tickets.
This has nothing to do with the splitting *grmpf* I know the dark side of the problem. Will solve it. Darth Plagous