Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"FancyName" is used instead of "ParamName" #302

Open
ewanwm opened this issue Jan 24, 2025 · 1 comment
Open

"FancyName" is used instead of "ParamName" #302

ewanwm opened this issue Jan 24, 2025 · 1 comment
Labels
Bug Fix Something isn't working

Comments

@ewanwm
Copy link
Contributor

ewanwm commented Jan 24, 2025

Is it really right to use the FancyName inside the covariance objects?

_fFancyNames[i] = Get<std::string>(param["Systematic"]["Names"]["FancyName"], __FILE__ , __LINE__);

CorrNamesMap[param["Systematic"]["Names"]["FancyName"].as<std::string>()]=i;

To me the regular parameter name should be used internally and "FancyName" should only be used for e.g. plotting, printing etc.
I can't actually find anywhere that "ParameterName" is used at the moment.

Didn't want to just change this as it would probably break all existing config files :)

@ewanwm ewanwm added the Bug Fix Something isn't working label Jan 24, 2025
@KSkwarczynski
Copy link
Member

I agree this is confusing. I think there was initally idea as you outline, but so many processing relies on names being xsec_XX

Right now normal name is xsec_XX (autogenerated), while fancy name Eb_XX

- Systematic:
    Names:
      FancyName: EB_dial_C_nu

    Correlations:
    - EB_dial_C_nubar: '0.778'

I think expansion of this issue should be how we store parameter names in MCMC tree and how processing works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Fix Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants