This repository has been archived by the owner on Nov 22, 2022. It is now read-only.
Unify input for TorchScript Tensorizers and Models #1256
Closed
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.
Summary:
Dataflow from PyText client to TorchScript model in predictor
Before:
We need a wrapper for each combination of (texts, tokens, languages, dense)
After:
a wrapper for with dense, another wrapper for without dense feature
Alternative:
ScriptPyTextModule(inputs: ScriptBatchInput)
after NamedTuple is supported in client example => predictor => ScriptPyTextModule
https://fb.workplace.com/groups/811605488888068/permalink/3266598560055403/
Reviewed By: chenyangyu1988
Differential Revision: D19900062