Open
Conversation
…[0,1] range. I _believe_ this is the expected range for the VGG16 model. A better solution could be to perform a specific normalization step depending on the initial type and depth of the source image. This change is sufficient for me for now, as it allows the testing of regular JPG files whose ranges were in the [0, 255] range.
This was an usual occurrence while testing early epoch models. If the punctuation sign was not among the generated words, the `test` function only showed the first word ('a', usually).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Some small changes to the notebook:
testfunction defaults to using a valid image path.More details in the corresponding revision logs.