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

Closure with same level1 #2007

Draft
wants to merge 30 commits into
base: master
Choose a base branch
from
Draft

Closure with same level1 #2007

wants to merge 30 commits into from

Conversation

andreab1997
Copy link
Contributor

This is just a draft in which I collected some hack I need to do for the alpha_s closure test study. @RoyStegeman

@andreab1997 andreab1997 marked this pull request as draft March 15, 2024 14:25
@RoyStegeman RoyStegeman changed the base branch from master to alphas_determination March 15, 2024 14:50
@RoyStegeman RoyStegeman changed the base branch from alphas_determination to master March 15, 2024 14:51
Copy link
Member

@RoyStegeman RoyStegeman left a comment

Choose a reason for hiding this comment

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

Thanks, this seems correct to me. Along with the notebook. Perhaps you'll want to rebase though since switching between this branch master has some delay due to the massive amount of data files moved (and there have been some improvements in particular regarding python and tensorflow versions)

validphys2/src/validphys/config.py Outdated Show resolved Hide resolved
"covariance matrix has not been implemented yet."
)
return validphys.filters.filter_closure_data_by_experiment
if theorycovmatconfig is not None:
Copy link
Member

Choose a reason for hiding this comment

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

I guess the theorycovmatconfig.get("use_thcovmat_in_sampling") should still be checked.

@RoyStegeman
Copy link
Member

Maybe it's better to get the changed cut back into master ASAP, to limit the number of affected fits. Could you open a separate PR for it?

@andreab1997
Copy link
Contributor Author

Maybe it's better to get the changed cut back into master ASAP, to limit the number of affected fits. Could you open a separate PR for it?

Yes sorry, I did it here for the moment just to test

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

Successfully merging this pull request may close these issues.

None yet

3 participants