-
Notifications
You must be signed in to change notification settings - Fork 9
Updated model to include trained_slice_id #421
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
Talked with Ryan on Slack, I think we'll sync up with @levinwil tomorrow to scope out exactly what he needs for his work. We can always backfill trained_slice_id in the PSQL database at a later date, so I don't think it's really necessary to push through ASAP |
feel free to loop me in, happy to learn more about the context here |
@scaleapi/nucleus-eng @edwardpark97 PR is now ready for review with accompanying scaleapi PR. |
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.
apart from comments LGTM, thanks!
@scaleapi/nucleus-eng If the PR looks good to y'all, would someone be able to merge it please. |
90a6a9c
to
61e632f
Compare
|
This update is to add
trained_slice_id
to the model object. So that when we create a model (withNUCLEUS_CLIENT.create_model
) we are able to associate atrained_slice_id
with it.I did not change the repr response, since it causes issues with the test comparison. Let me know if we want to simplify the repr and modify the test or leave as is.
Associated scaleapi PR: https://github.com/scaleapi/scaleapi/pull/74083
Previous PR: #419