-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add ml model service #469
base: main
Are you sure you want to change the base?
Add ml model service #469
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.
LGTM (have not manually tested this)
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!
export type { | ||
FlatTensors, | ||
InferResponse, | ||
MetadataResponse, | ||
} from '../../gen/service/mlmodel/v1/mlmodel_pb'; |
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.
From what I know, we don't directly export proto types. There are other instances when we export after using shadow types (i.e. in the navigation service and movement sensor component)
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.
That makes sense, I will update them to shadow types. I also may just reduce it to the FlatTensors
shape, since they other are response shapes but FlatTensors
is used as an argument for one of the APIs, so I could see users wanting to pre-construct that before passing it along.
We have an incoming request to render the response of the
Metadata()
in the test controls for the ML Model Service card. This exposes themetadata
API to be used.