Hi all,
Just a heads up that vak
version 0.5.0 is released:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## Unreleased
### Added
- Add unit tests for `csv.has_unlabled`
[#541](https://github.com/NickleDave/vak/pull/541).
Fixes [#102](https://github.com/NickleDave/vak/issues/102).
- Add unit tests for `__main__`
[#542](https://github.com/NickleDave/vak/pull/542).
Fixes [#337](https://github.com/NickleDave/vak/issues/337).
- Add validation of `labels` argument to `vak.split.algorithms.brute_force`,
to prevent conditions where algorithm can fail to converge
because of bad input
[#562](https://github.com/NickleDave/vak/pull/562).
Fixes [#288](https://github.com/NickleDave/vak/issues/288).
- Add a "Frequently Asked Questions" page to the documentation,
This file has been truncated. show original
You should be able to pip install
or get it through the conda-forge
channel now.
Big addition here is the ability to continue training models, contributed by @kaiyaprovost and based on work in their pre-print . Thank you Kaiya!
This is also the first time I’ve worked with someone as a maintainer on a sizable code contribution to a project
Gory detail in the pull request here if you want to read:
vocalpy:main
← kaiyaprovost:adding-training-checkpoint-feature
opened 06:33PM - 20 Apr 22 UTC
ENH: Add "train_checkpoint module" based off of "train" module and "predict" mod… ule. Copied main code of "train" module while updating core, cli, config. Added code from "predict" to import an existing checkpoint from a previous run of a model, rather than initializing a new model without any training.
There are also some doc fixes – thanks to @YMK123 for helping catch issues with how we explained the expected naming conventions for annotation files:
Based on other issues I think this still might be a point of confusion, see e.g. DOC: Better document naming convention · Issue #524 · vocalpy/vak · GitHub
The long term plan is to make it easier to build datasets by letting people specify whatever convention they want
ENH: add `pair` function with `key` argument · Issue #2 · vocalpy/vocles · GitHub
(I know the wording in this issue is only clear to me at the moment so you just have to take my word that’s the plan )
Thanks all for contributing and please feel free to give feedback when you test it out!
1 Like