-
Notifications
You must be signed in to change notification settings - Fork 73
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
feat(weave): Support creating a dataset from ops #3385
base: andrew/ds-frame
Are you sure you want to change the base?
Conversation
Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=c04f5d15f4fda6a3f50ba436761ae25e822e7449 |
0103498
to
eb73723
Compare
a65ca93
to
bb3b9a6
Compare
eb73723
to
dbe4992
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do this? Is this in response to a customer/user? Seems like unnecessary sugar - makes a 1 liner from a 2 liner.
It's just sugar for expressing the user intent "How do I make a dataset of my function's calls" (as per: https://www.notion.so/Eval-and-Dataset-Workflow-API-Improvements-15fe2f5c7ef380c3a89ce031c36cb767?pvs=4#160e2f5c7ef380e7adf5d02da9390c7f) I'm not against skipping this one |
I think it is going to be very rare that you just want to create a dataset from a single op. you almost always are going to filter by something / look for a tag / look for an annotation / filter by a time window / etc... i might opt to skip this for now |
bb3b9a6
to
8e7ac86
Compare
Resolves: https://wandb.atlassian.net/browse/WB-22706