|
[Flexiblesusy-commits] [FlexibleSUSY/FlexibleSUSY] 430927: generalise particle references in the templatesGitHub noreply at github.comMon Aug 15 16:19:16 BST 2016
Branch: refs/heads/feature-SMtower Home: https://github.com/FlexibleSUSY/FlexibleSUSY Commit: 4309274d247b365faf1d47751f6661d851563498 https://github.com/FlexibleSUSY/FlexibleSUSY/commit/4309274d247b365faf1d47751f6661d851563498 Author: Alexander Voigt <Alexander.Voigt at desy.de> Date: 2016-08-15 (Mon, 15 Aug 2016) Changed paths: M meta/FlexibleSUSY.m Log Message: ----------- generalise particle references in the templates MSSM: HiggsBoson_0 -> hh(0) HiggsBoson_1 -> hh(1) HiggsBoson(1) -> hh(1) SM: HiggsBoson_0 -> hh # has no index HiggsBoson(0) -> hh(0) # always puts index in parenthesis Commit: 7a4984c10011188ad99a7472eb13aaf35b8655d7 https://github.com/FlexibleSUSY/FlexibleSUSY/commit/7a4984c10011188ad99a7472eb13aaf35b8655d7 Author: Alexander Voigt <Alexander.Voigt at desy.de> Date: 2016-08-15 (Mon, 15 Aug 2016) Changed paths: M templates/standard_model_matching.cpp.in M templates/standard_model_matching.hpp.in M templates/standard_model_two_scale_matching.cpp.in M templates/standard_model_two_scale_matching.hpp.in Log Message: ----------- generalisation: allow usage of arbitrary CP-even Higgs mass entry in BSM model. For example in the NMSSM, one can now use the 2nd Higgs to be the SM-like one. However, this makes only sense, if the SM can still be regarded as the correct EFT, i.e. when hh(0) ~ hh(1) ~ M_SUSY In this case one would integrate out all particles at M_SUSY, which is close to the EW scale. Compare: https://github.com/FlexibleSUSY/FlexibleSUSY/compare/2f3549f2fbec...7a4984c10011
More information about the Flexiblesusy-commits mailing list |