Update prediction pipeline example #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
simleo
force-pushed
the
update_prediction_pipeline
branch
from
a70f084 to
f171089
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the ML prediction pipeline example according to the latest discussion on the profile:
encodingFormatexampleOfWorkadditionalTypeentry fromPropertyValueentitites (that info can now be retrieved by followingexampleOfWorkto the correspondingFormalParameter)File parameters now list their expected format via
encodingFormat, whileadditionalTypehas been changed toImageObject. Note that I haven't added anencodingFormatentry to non-file parameters (e.g., integers): would it make sense to do so? E.g.,text/plain?