-
Notifications
You must be signed in to change notification settings - Fork 9
Feat/add prediction artifact and upload method #292
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
Conversation
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.
Left some comments about the model structure. We can chat about it some more if you'd like. 😄
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.
Nice work, @j279li !
fe10e34
to
db77f00
Compare
@jstlaurent I've encountered circular import issues with BenchmarkV2Specification, since the benchmark package already imports from the evaluate package. To work around this, I moved the Predictions class into its own package for now. Would that be alright, or do you have other ideas? |
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.
Nice job!
@j279li Ping me once this is ready for another review! Happy to take a look! |
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.
Thanks again, @j279li 💪 I've left a few comments we should probably take a look at. It's coming along nicely!
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.
Hi @j279li, sorry for not spotting any of this on my first review. I've been out of the loop on recent changes to Polaris, so I may also be missing some context here.
We're making good progress, but I think we should take another look at how we've done things for competitions. Specifically, I would like us to revisit the user-facing API as well as the validation of the Predictions
class.
Happy to find some chat to about this tomorrow!
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.
Thanks @j279li , we've made a lot of progress but there are still a couple of thinks I would like us to take a look at. Let me know if you have any questions!
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.
Thanks for all the changes, @j279li! I just have a few more suggestions and comments.
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.
Sorry for the quick feedback, @j279li , but I saw the new commit and figured I would leave the feedback sooner rather than later.
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.
I'm left with some minor comments, but this looks good to me! Thanks @j279li, great work ! 🚀
Summary of Changes
This PR introduces a new Prediction artifact, and an associated upload method
New Features
Prediction Artifact (
Predictions
)Predictions
model to represent prediction artifacts as Zarr archives.columns
,dtypes
,n_rows
, etc.) for quick data exploration.Upload API (
upload_prediction
)upload_prediction
method inPolarisHubClient
for uploading prediction artifacts.