Docker torch1.13 PL 1.9 - Transform p=1.0 #321
Merged
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
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.
General description of your pull request with the list of new features and/or bugs.
Docker : New docker image with pytorch 1.13 support & pytorch lightning 1.9
Changed back transfrom to p=1.0 : transformation used to be apply automaticly on all frames. Last month we introduced a new parameter to randomly apply the transformation. The parameter was set to p=0.5 which might affect all the training pipeline. As of now we come back to p=1.0 as a default value (transformartion is always apply)
This pull request includes