-
Notifications
You must be signed in to change notification settings - Fork 54
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
do_not_ask_list #129
Comments
This should be an alg level decision -- what if the alg developer wants to ask the same question twice (e.g., like I did in validation sampling for triplets). I'm pro keeping dev around but renaming to legacy. |
The do not ask list is handed to the alg without taking any action, the alg On Thursday, August 4, 2016, Scott Sievert [email protected] wrote:
|
Was the do_not_ask_list put back in? This is important to have in place before any psych experiment happen. |
I think CardinalBandits has it, but we're definitely missing an example of this in the docs. Also, we should probably do a name change. Maybe previois_questions instead of do_not_ask? |
This used to be implemented in the App.py list (pre redux). I now see no reference to it in PoolBasedTripletMDS or DuelingBandits. We should make sure to reimplement it...this is also a good argument to not delete the dev branch (perhaps rename it to legacy) just to confirm that everything made it.
The text was updated successfully, but these errors were encountered: