Support for storing models from N last epochs and decoding with those models. #61
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.
User can define number of models to store from
n_mdls_store
last epochs, controlled withn_mdls_store
option in a config file. After training, user can decide to decode with the model stored prior to the final iteration, similarly to theiter
option in Kaldi decoding scripts. This can be done withep_to_decode
option. Epoch indexing starts from 0, so to match e.g. the res.res file, here indexing also starts from 0. This means that if the training is for 5 epochs, and we'll setep_to_decode
to 4, the final model will be used. If theep_to_decode
option is left empty, the final model will be used. A separate decoding directory will be created for eachep_to_decode
.Maybe changing epoch indexing to start from 1 throughout the code would be less confusing?