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

Better blinding #100

Merged
merged 4 commits into from
Jun 9, 2017
Merged

Better blinding #100

merged 4 commits into from
Jun 9, 2017

Conversation

coderdj
Copy link
Contributor

@coderdj coderdj commented May 10, 2017

Adds parameter 'blind_from_run'. Setting this to a run number automatically blinds all background_stable runs after this point unless they are specifically tagged 'unblinded' or '_unblinded'.

This should make it so shifters don't have to put the blinded tag on each run and should remove the possibility of accidentally unblinding because a shifter forgets or misspells this tag.

@JelleAalbers
Copy link
Contributor

JelleAalbers commented May 18, 2017

Thanks Dan, this looks fine. I took the liberty of adding a few comments, fixing a typo ('number' -> number), and removing an unneeded except (KeyError should happen when using get_run_info asking for a single field). If you agree feel free to merge (unless @feigaodm sees a problem?)

Congratulations on the #100 by the way ;-)

@coderdj
Copy link
Contributor Author

coderdj commented May 18, 2017

I have no problem with merging but I'd leave the #blinded tag in until at least a couple people try this out on a few (unblinded) runs. I'll wait for advice from Fei though.

@feigaodm
Copy link
Member

Sorry that I responded to @coderdj only, definitely it's a better way for blinding. Maybe we can test it with new runs without 'blinded' tag, but it's not a stopper to to merge it

@feigaodm feigaodm merged commit 3788c64 into master Jun 9, 2017
@feigaodm feigaodm deleted the better_blinding branch June 9, 2017 20:32
@feigaodm feigaodm added this to the v1.4.5 milestone Jun 19, 2017
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.

3 participants