NEXT
NEXT copied to clipboard
nextml
do_not_ask_list
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.
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 can choose to not pay attention to it
On Thursday, August 4, 2016, Scott Sievert [email protected] wrote:
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).
I'm pro keeping dev around but renaming to legacy.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nextml/NEXT/issues/129#issuecomment-237732532, or mute the thread https://github.com/notifications/unsubscribe-auth/ACHgBx2z-sWfLiwNxmNh3e4OZQXI3bgbks5qcpFpgaJpZM4JdP49 .
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?