Skip to content

Commit f4432de

Browse files
A-RindoneA-Rindone
authored
Experiment status "Completed" -> "Concluded"
1 parent 815e3b8 commit f4432de

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

‎docs/experiment-analysis/reading-results/experiment-status.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ You can navigate to the **Analysis** page by clicking on the icon from the left-
66
2. Running - The active state where the experiment is assigning subjects and/or updating the metric event data
77
3. Ready for Review - The state where a decision can be made, either because the primary metric is statistically significant for a sequential/Bayesian test, the precision target has been hit, or the end date has been reached. The experiment may still be assigning subjects and/or updating the metric event data if the end date has not yet been reached.
88
4. Wrap Up - The state where the end date of the experiment has been reached and Eppo is no longer automatically updating results, but requirements to make a decision have not been met
9-
5. Completed - The state where a decision regarding the experiment has been made
9+
5. Concluded - The state where a decision regarding the experiment has been made
1010

1111
![Experiment Statuses](/img/measuring-experiments/experiment-status-1.png)
1212

@@ -19,7 +19,7 @@ If you hover on the progress bar for an experiment you can view more details abo
1919
| Status | Non-Eppo Randomized Experiment | Eppo Randomized Experiment |
2020
| :----------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
2121
| `DRAFT` | Go to `RUNNING` if… <li> Experiment key added </li> <li> Active variation added </li> <li> Experiment started <em>(the assignment start date passed)</em> </li> | Go to `RUNNING` if… <br/> <li> Experiment key added </li> <li> Active variation added </li> <li> Experiment started <em>("Start Experiment" button pressed)</em> </li> |
22-
| `RUNNING` | Go to `READY TO REVIEW` if… <li> Primary metric is statistically significant for a sequential/Bayesian test </li> <li> OR Precision target has been reached for a sequential/Bayesian test </li> <li> OR Experiment ended <em>(Later of the end dates entered by the user has passed)</em> </li> <li> AND there is no traffic imbalance </li> <li> [Optional] AND Minimum requirements have been met </li> <br/> Go to `WRAP UP` if… <li> A traffic imbalance exists </li><li>[Optional] OR minimum requirements have not been met</li><li>AND Experiment ended <em>(Later of the end dates entered by the user has passed)</em></li><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will update the end date if going from `RUNNING` to `COMPLETED` </li> | Go to `READY TO REVIEW` if… <li> Primary metric is statistically significant for a sequential/Bayesian test </li> <li> OR Precision target has been reached </li> <li> OR Experiment ended <em>(User stops assignments & event analysis date has passed)</em> </li> <li> AND there is no traffic imbalance </li> <li> [Optional] AND Minimum requirements have been met </li> <br/> Go to `WRAP UP` if… <li> A traffic imbalance exists </li><li>[Optional] OR minimum requirements have not been met</li><li>AND Experiment ended <em>(Later of the end dates entered by the user has passed)</em></li><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will stop assignments if still on and update the end date if going from `RUNNING` to `COMPLETED` </li> <br/>Uncommon situation: If the event analysis end date is set to run longer than when assignments are stopped, clicking “Stop Assignment” will not change the experiment status from `RUNNING`. The experiment will remain in the `RUNNING` status until the larger of the two end dates have passed. Once that date has passed, the experiment will move into the `READY FOR REVIEW` status.|
23-
| `READY FOR REVIEW` |Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will update the end date if going from `READY TO REVIEW` to `COMPLETED` </li> | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will stop assignments if still on and update the end date if going from `READY TO REVIEW` to `COMPLETED` </li> |
24-
| `WRAP UP` | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - the dates are not affected </li> | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `COMPLETED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - the dates are not affected </li> |
25-
| `COMPLETED` | Go to `READY TO REVIEW` if… <li> User reopens the experiment - this allows them to edit the date ranges and the decision made </li> | Go to `READY TO REVIEW` if… <li> User reopens the experiment - this allows them to edit the event analysis date ranges and the decision made </li> |
22+
| `RUNNING` | Go to `READY TO REVIEW` if… <li> Primary metric is statistically significant for a sequential/Bayesian test </li> <li> OR Precision target has been reached for a sequential/Bayesian test </li> <li> OR Experiment ended <em>(Later of the end dates entered by the user has passed)</em> </li> <li> AND there is no traffic imbalance </li> <li> [Optional] AND Minimum requirements have been met </li> <br/> Go to `WRAP UP` if… <li> A traffic imbalance exists </li><li>[Optional] OR minimum requirements have not been met</li><li>AND Experiment ended <em>(Later of the end dates entered by the user has passed)</em></li><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will update the end date if going from `RUNNING` to `CONCLUDED` </li> | Go to `READY TO REVIEW` if… <li> Primary metric is statistically significant for a sequential/Bayesian test </li> <li> OR Precision target has been reached </li> <li> OR Experiment ended <em>(User stops assignments & event analysis date has passed)</em> </li> <li> AND there is no traffic imbalance </li> <li> [Optional] AND Minimum requirements have been met </li> <br/> Go to `WRAP UP` if… <li> A traffic imbalance exists </li><li>[Optional] OR minimum requirements have not been met</li><li>AND Experiment ended <em>(Later of the end dates entered by the user has passed)</em></li><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will stop assignments if still on and update the end date if going from `RUNNING` to `CONCLUDED` </li> <br/>Uncommon situation: If the event analysis end date is set to run longer than when assignments are stopped, clicking “Stop Assignment” will not change the experiment status from `RUNNING`. The experiment will remain in the `RUNNING` status until the larger of the two end dates have passed. Once that date has passed, the experiment will move into the `READY FOR REVIEW` status.|
23+
| `READY FOR REVIEW` |Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will update the end date if going from `READY TO REVIEW` to `CONCLUDED` </li> | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - This will stop assignments if still on and update the end date if going from `READY TO REVIEW` to `CONCLUDED` </li> |
24+
| `WRAP UP` | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - the dates are not affected </li> | Note: This step is skipped if user clicks “Make Decision” from the `RUNNING` state <br/><br/> Go to `CONCLUDED` if… <li> Decision made <em>(user clicks the “Make Decision” button and fills out the outcome and decision)</em> - the dates are not affected </li> |
25+
| `CONCLUDED` | Go to `READY TO REVIEW` if… <li> User reopens the experiment - this allows them to edit the date ranges and the decision made </li> | Go to `READY TO REVIEW` if… <li> User reopens the experiment - this allows them to edit the event analysis date ranges and the decision made </li> |

0 commit comments

Comments
 (0)