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

cases: Experiments #2270

Closed
dberenbaum opened this issue Mar 5, 2021 · 8 comments
Closed

cases: Experiments #2270

dberenbaum opened this issue Mar 5, 2021 · 8 comments
Labels
A: docs Area: user documentation (gatsby-theme-iterative) C: cases Content of /doc/use-cases ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement p1-important Active priorities to deal within next sprints type: discussion Requires active participation to reach a conclusion.

Comments

@dberenbaum
Copy link
Contributor

dberenbaum commented Mar 5, 2021

Child issue of #2266

Proposed requirements

  • Identify potential opportunities to use experiments
  • Show value added by experiments

Questions

  • Is this needed as a separate section?
  • Are example projects needed for this?
  • Who is the target user to read this over other exp docs?
@jorgeorpinel

This comment has been minimized.

@jorgeorpinel jorgeorpinel added A: docs Area: user documentation (gatsby-theme-iterative) p1-important Active priorities to deal within next sprints labels Mar 9, 2021
@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Mar 9, 2021

Ideas for slightly more specific use cases:

  • Hyperspace exploration [Tuning/Optimization] (examples + params & metrics) — too narrow
  • Experiment Bookkeeping? (with Git) Rapid iterations
  • Visualizing Data Science (experiments + metrics/plots)

@dmpetrov and @shcheklein probably have better suggestions.

@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented Apr 7, 2021

This one was probably useful too! Esp. #2270 (comment) (for me at least)

@dberenbaum
Copy link
Contributor Author

I was thinking we could open new issues when we have specific use cases in mind ready to develop, but no problem if having this open as a placeholder with some ideas is helpful for you.

@jorgeorpinel jorgeorpinel changed the title Exp Use Case case: Experiments Apr 28, 2021
@jorgeorpinel jorgeorpinel changed the title case: Experiments cases: Experiments May 6, 2021
@jorgeorpinel jorgeorpinel changed the title cases: Experiments cases: Experiments direction May 19, 2021
@jorgeorpinel jorgeorpinel added ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately. p1-important Active priorities to deal within next sprints and removed p1-important Active priorities to deal within next sprints p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately. labels May 19, 2021
@jorgeorpinel
Copy link
Contributor

jorgeorpinel commented May 19, 2021

From #2490 (comment):

Idea: Experiments tracking/management - here we should sell W&B, MlFlow, etc - rapid iterations, live metrics + other metrics + navigation

I'm still unclear whether an experiment-related use case would be a higher priority than a ML model-related one (#2490), But the ML model direction has been waiting for a use case for a longer time.

Cc @shcheklein

@shcheklein

This comment has been minimized.

@jorgeorpinel

This comment has been minimized.

@jorgeorpinel jorgeorpinel added p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately. p1-important Active priorities to deal within next sprints and removed p1-important Active priorities to deal within next sprints p2-nice-to-have Less of a priority at the moment. We don't usually deal with this immediately. labels May 26, 2021
@jorgeorpinel jorgeorpinel changed the title cases: Experiments direction cases: Experiments Jun 3, 2021
@jorgeorpinel jorgeorpinel added the type: discussion Requires active participation to reach a conclusion. label Jun 3, 2021
@jorgeorpinel jorgeorpinel mentioned this issue Jun 8, 2021
5 tasks
@jorgeorpinel
Copy link
Contributor

Closing in favor of #2544 epic.

@iesahin iesahin added the C: cases Content of /doc/use-cases label Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: docs Area: user documentation (gatsby-theme-iterative) C: cases Content of /doc/use-cases ✨ epic Placeholder ticket for multi-sprint direction, use story, improvement p1-important Active priorities to deal within next sprints type: discussion Requires active participation to reach a conclusion.
Projects
None yet
Development

No branches or pull requests

4 participants