-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
IDataView Type system needs to be extensible to properly support image, date, and other types #3274
Comments
Perhaps we ought to change this to, the reflection based mechanism by which things like prediction engine specifically are not extensible to new types -- a problem that would not exist but for the fact that the DataView type system is extensible, which makes the title a bit misleading? What you think? I also I have a possibly workable solution to that specific problem in #3263, let me know your reactions. |
Agree. I think this is "a must" feature (pre-requisite) in ML.NET (support for in-memory images) in order to be able to release the TensorFlow and ONNX packages as v1.0 (Currently 0.12). Note that this implementation would be centralized (not specific within the TensorFlow or ONNX packages), though, so it'll need a new version for ML.NET itself, too? Minor version? |
To support loading
Image
fromIDataView
(as shown in #3263), user must modify ML.NET code, which means our type system is not extensive. Do we want to invest on the extensibility of ML.NET type system?The text was updated successfully, but these errors were encountered: