corrected order of valid and train data arguments in DomainDataModule #82
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.
here the order of validation and training where mixed up. This error goes all the way through to the trainer. I.e., training data and validation data get swapped!
Maybe adapt the code with keyword arguments so that the order does not matter?
PS:
If you want to double check the length of valid and train data used in the trainer, add in
class DomainDataModule
:Then add before the unimodal module the following class:
Finally, in def train module, before calling the trainer, add
dataset_length_logger = DatasetLengthLogger()
And in trainer, add
dataset_length_logger
to the callbacks:Result:
Training Data Length 128
Validation Data Length 256