-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Question about sequence/map input onnx type from model #1747
Comments
I'll take a look at the second one. It shouldn't be [-1]. |
For you question two: here the -1 means unknown. You can replace it with any non-zero positive value. |
Yes, I did replace the -1 with 1 to all of the four inputs while getting the element out-of-bound exception as shown in the screen shot. |
We'll update the model. |
For 1. I'm not sure what you mean by continuing to get the type of the map. If you have an Ort::Value you can still call GetTypeInfo() on it and then call GetONNXType() the same as before? |
@RyanUnderhill Thanks Ryan. However, for inputs, I will not get it in Ort::Value and the GetTypeInfo() could only get the type of the outer type. |
@qw2208 Ah, I see what you're looking for. Yeah, currently we have no way to query subtype information of a type. I'm marking this as an enhancement as we'd need some extra interface functions like this: OrtStatus* GetType(const OrtTypeInfo type, int index, OrtTypeInfo** out) |
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. If further support is needed, please provide an update and/or more details. |
This issue has been automatically closed due to inactivity. Please reactivate if further support is needed. |
For example, if the model input is of type: std::vector<std::map<int64_t, float>>, I could get the input type of
ONNX_TYPE_SEQUENCE
by runningsession->GetInputTypeInfo(i).GetONNXType();
However, I'm confused how I could continue to get the type of the map while creating Ort::Value using the CXX api?
The text was updated successfully, but these errors were encountered: