Fix dataset preparation save folder in fluent-speech-commands recipe - #2860
Closed
tomaz-suller wants to merge 1 commit into
Closed
tomaz-suller wants to merge 1 commit into
tomaz-suller wants to merge 1 commit into
Conversation
Variable `save_folder` was mapped to `hparams["output_folder"]` which resulted in a file not found error. By we fix that by passing the correct parameter to `prepare_FSC`.
Author
|
I'll run the recipe tests when I have some time to spare if really needed |
Author
|
I've realised there are other issues with this recipe, so for now I'll close this PR and open a new one fixing all of them instead |
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
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.
What does this PR do?
Variable
save_folderwas mapped tohparams["output_folder"]which resulted in a file not found error. By we fix that by passing the correct parameter toprepare_FSC.Did not bother opening issue since fix is trivial.
Before submitting
Did you make sure to update the documentation with your changes? (if necessary)PR review
Reviewer checklist