You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's actually make an issue to summarize the QED development (i.e. the actual implementation of QED evolution in EKO), while the old #23 will keep serving the purpose of collecting ideas and related items.
specify orders in the runcards, proposal PTO: n -> order: {qcd: ns, qed: n} such that we have an unambiguous PineAPPL compatible name (instead of a weird acronym...)
even if we have no QED matching conditions (to be verified at level of logs of mass over matching scale ratios) we still have to implement the existing ones in the unified basis
the easiest is to just apply the rotation after defining them in QCD evolution basis
Let's actually make an issue to summarize the QED development (i.e. the actual implementation of QED evolution in EKO), while the old #23 will keep serving the purpose of collecting ideas and related items.
PTO: n->order: {qcd: ns, qed: n}such that we have an unambiguous PineAPPL compatible name (instead of a weird acronym...)