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

Feature/dbarrow257/osc prob dune old core #47

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from

Conversation

camillesironneau
Copy link
Member

Pull request description:

Addition of apps for 2D variations of parameters. Also included example .yaml file to use the app Variations2D

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is your first PR, thank you for contributing to MaCh3 DUNE!

Copy link
Member

@dbarrow257 dbarrow257 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the good work - some minor YAML node reworking just to keep the General node more concise.

#T2K-like best-fit
#OscillationParameters: [0.307, 0.528, 0.0218, 7.53e-5, 2.509e-3, -1.601, 25]

Variations:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you move this to it's own node? I.e. see the Projections node at the bottom of this config?

for (int iPar=0;iPar<nPars;iPar++) {
std::string ParName = CovObj->GetParName(iPar);

for (auto const &param : FitManager->raw()["General"]["Variations"]) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And the associated change here for moving the Variations to it's own node

@@ -0,0 +1,130 @@
#include <iostream>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a few lines about the structure of the Variations YAML node, and expected structure?
Also can you add a TODO about considering merging this with the SigmaVariations app?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants