Strip control inputs from graph when creating new TF functions from tensors. #5
Conversation
This file contains 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
drubinstein
reviewed
Jul 24, 2023
drubinstein
approved these changes
Jul 24, 2023
psobot
force-pushed
the
psobot/control-inputs
branch
from
0609e25
to
6939f80
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.
When using
create_function_from_tensorsto create a new TensorFlow function from an existing TF model or graph, the presence of control inputs can cause the extraction of a sub-graph to fail. These control inputs are generally only used during training, while this function is usually used for inference.This PR adds a new argument to
create_function_from_tensorsto allow including control inputs, which are now omitted by default. To detect control inputs, we use the same criteria as the main TensorFlow package.