rstudio / rstudio/vetiver-python
thinking about a/b testing in vetiver
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 71
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
what does a/b testing look like using vetiver now? you can create VetiverAPIs, need some sort of mechanism to route to the correct endpoint.
does it make sense to add any helper functions for this? if yes, what? if no, what documentation will help users who are looking to get started with this task?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how VetiverAPIs are currently created and exposed, then investigate how users could route requests between endpoints for A/B testing. The issue is done when the project has a decided approach—either helper functions or documentation—with clear guidance for getting started.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100