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
Info printed during yadism runs are still partial, to be included
FNS
TMC (if enabled)
To be reorganized:
couplings related: e.g. QCDNUM needs to load the coupling constants, and so it's doing many calls to get_weights, but it's reasonable that some values are constant per-run, like MZ and so on, and instead they are printed over and over
maybe we should make an object that loads some initial configs, and log only when instantiating the object, or changing top-level values (like MZ), while not logging for each and every
Debug level
logging more in distribution_vec?
The text was updated successfully, but these errors were encountered:
I'd rather lower the logging level in this specific piece of code, if needed - otherwise keep in mind that we still want to make logging as explicit as possible and introduce a new output level for user information
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Info level
Info printed during
yadism
runs are still partial, to be includedTo be reorganized:
get_weights
, but it's reasonable that some values are constant per-run, likeMZ
and so on, and instead they are printed over and overMZ
), while not logging for each and everyDebug level
distribution_vec
?The text was updated successfully, but these errors were encountered: