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

mooclet frontend: reward metric section in stepper #2203

Open
danoswaltCL opened this issue Feb 7, 2025 · 1 comment · May be fixed by #2210
Open

mooclet frontend: reward metric section in stepper #2203

danoswaltCL opened this issue Feb 7, 2025 · 1 comment · May be fixed by #2210
Assignees
Labels

Comments

@danoswaltCL
Copy link
Collaborator

danoswaltCL commented Feb 7, 2025

A mooclet (adaptive) experiment will always need to have a reward metric. For MVP we will always be creating this metric for the user, and attaching a query for success percentage automatically. See #1934 and #2191 for how the backend will wire this up.

The convention for this metric key will be the [UPPERCASE name of the experiment] + _REWARD. A mooclet experiment will be guaranteed to be uniquely named (#2199), so this will suffice as a unique key.

Requirements:

  • For mooclet experiments only, a read-only "Reward Metric" section will appear below the usual Metrics in the metric tab.

  • The reward metric key will be sent on the experiment as rewardMetricKey

  • The link is TBD, we will need a story to create documentation link in gitbook.

Image

Image
@danoswaltCL danoswaltCL changed the title mooclet frontend: mooclet frontend: reward metric section in stepper Feb 7, 2025
@zackcl zackcl self-assigned this Feb 7, 2025
@zackcl zackcl moved this to In Progress in UpGrade Project Feb 7, 2025
@kawcl
Copy link
Contributor

kawcl commented Feb 11, 2025

Updated requirements to include key on experiment dto.

@danoswaltCL danoswaltCL moved this from In Progress to Code Review in UpGrade Project Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Code Review
Development

Successfully merging a pull request may close this issue.

3 participants