id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 830,"General support for running masses, couplings and K factors that change event by event",Juergen Reuter,kilian,"Taken over from gitlab issue #51: The SM_tt_threshold-parameter {{{M1S}}} is used by whizard to compute the top mass at sqrts, which is used for example to perform the on-shell projection. However, the model is linked to whizard via C-Interfaces, so that the value of M1S set there is not saved inside Whizard. A workaround has been implemented in {{{ed9beb0d}}} and {{{59e1878d}}}. A more generic solution would approach the problem also from the point of view of running masses and widths. So far, they are constant in Whizard, but the threshold approach (Issue #43 (closed) ) and multiple other applications make up a requirement for this feature. It could work in a similar way as alpha_s and the qcd_t object. However, this would require the switch from some masses and widths from model parameters to Whizard options. BACN suggested to combine this with a more general container for runtime-dependent variables for different models in general. ",task,closed,P4,v2.8.3,core,2.5.0,minor,duplicate,"Refactoring, backlog",