TF 2.4 raises a val err: Keras symbolic inputs/outputs do not impleme… #58
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
|
Is this merged ? |
|
Edit: Looks like TF > 2.x.x is not working at all. |
christian-steinmeyer
added a commit
to christian-steinmeyer/keras-surgeon
that referenced
this pull request
Jul 6, 2023
christian-steinmeyer
added a commit
to christian-steinmeyer/keras-surgeon
that referenced
this pull request
Jul 6, 2023
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 running inside of tensorflow 2.4, I am getting the following error:
TypeError: Keras symbolic inputs/outputs do not implement __len__. You may be trying to pass Keras symbolic inputs/outputs to a TF API that does not register dispatching, preventing Keras from automatically converting the API call to a lambda layer in the Functional Model. This error will also get raised if you try asserting a symbolic input/output directly.This is due to the fact that
utils.pychecks for the length of the input tensors... the fix is to check if we have a single tensor instance, a tuple, or a list. Here we assume that we have a single tensor anyways and as far as I know there is no support for multiple outputs.