Load time signal data #133
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
added 4 commits
July 16, 2019 17:21
* loading the raw time signal directly from wav-copy ark output * handling different sized chunking of input and output sequence * chunking information is currently handed over through config option max_seq_length_*
* added option to use max_sequence_length as carrier for the asynchron chunking information. * Implemention is backwards compatible with standard use
* this is needed if the feature and label sequences are of different length and the respective sub sampling is done by the network
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.
This pull request enables to load the wav data directly from kaldi ark files.
It also handles the issue of different dimensions in the input sequence length and label sequence length.
The changes are supposed to be completely backwards compatible to previous versions. But has only been tested on a small number of cases. Thus the whole implementation is kept in run_nn_refac01. But after more rigorous testing could potentially replace run_nn.
For the implementation to work the cfg_proto and cfg_proto_chunk need to be adjusted. For now the respective files have been added as separate files *_refac01.proto