#28 closed defect (fixed)
not able to use MSSM_CKM model
Reported by: | Juergen Reuter | Owned by: | kilian |
---|---|---|---|
Priority: | P3 | Milestone: | |
Component: | core | Version: | 2.0.0alpha |
Severity: | normal | Keywords: | wrong model setup |
Cc: |
Description
WHIZARD 2 is not able to use the MSSM_CKM model. When trying to use this WHIZARD always believes the MSSM model is invoked. So e.g. setting the CKM matrix elements is not accepted. Also the default values are not used, and WHIZARD gives back the MSSM cross sections etc. This could be connected to the SLHA interface but I am not sure. Probably the same is true for the MSSM_Grav mode.
Change History (6)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
When disabling the SLHA file, WHIZARD takes the correct model file to build up the phase space, if one raises the CM energy high enough to match the default masses. So it's the SLHA interface which screws this up!
comment:3 Changed 15 years ago by
These two lines in commands.f90 are the reason for the problem: call var_list_link (global%var_list, model_get_var_list_ptr (mdl)) global%model => mdl I don't know actually why the reading of the SLHA file should switch the model, but I will include a check vetoing usage of inconsistent models.
comment:4 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
I removed the resetting of the model by the SLHA_interface. This now allows to use MSSM_CKM, MSSM_Grav, NMSSM_CKM and so on with SLHA input file. A safety check to prevent abuse by the user has been added. Done in r1213.
comment:5 Changed 15 years ago by
Milestone: | v2-compiles-gfortran → v2.0-beta |
---|
What I checked recently is the following: when using the SLHA input file WHIZARD seems to be using the MSSM input file as standard, and e.g. CKM parameters are not known. WHen not using the SLHA input file, WHIZARD seems to be correctly using MSSM_CKM for the parameters, but not for the phase space setup. So there are at least two problems in that ticket.