You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, the Phoenix channel was used for both dynamic experiments and interactive experiments. An experiment would only start when the designated number of participants is reached.
Now, we have a <variant-chain-generation> tuple for dynamic experiments, and an interactive experiment would only start whenever the number of players is reached.
We can simplify the mechanism at first. If there is no need for a dynamic experiment to use socket features, let's use the socket exclusively for interactive experiments.
AC:
Dynamic experiments are no longer facilitated via channels, but rather with simple REST API calls to assign the tuple to the participant.
The text was updated successfully, but these errors were encountered:
x-ji
changed the title
Set up the channels so that both dynamic experiments and interactive experiments are supported
Support dynamic experiments via REST calls
Aug 14, 2021
x-ji
changed the title
Support dynamic experiments via REST calls
Support dynamic experiments via the socket
Aug 23, 2021
x-ji
changed the title
Support dynamic experiments via the socket
Support dynamic experiments via REST calls
Aug 23, 2021
Previously, the Phoenix channel was used for both dynamic experiments and interactive experiments. An experiment would only start when the designated number of participants is reached.
Now, we have a
<variant-chain-generation>
tuple for dynamic experiments, and an interactive experiment would only start whenever the number of players is reached.We can simplify the mechanism at first. If there is no need for a dynamic experiment to use socket features, let's use the socket exclusively for interactive experiments.
AC:
The text was updated successfully, but these errors were encountered: