INACTIVE - This is now the official location of the Kaldi project.
Перейти к файлу
Ilya Platonov 7264220cbb Adding nnet3/chain support to steps/cleanup/find_bad_utts_nnet.sh, now script supports both nnet2 and nnet3. Probably nnet1. 2016-05-09 17:37:32 +00:00
egs Adding nnet3/chain support to steps/cleanup/find_bad_utts_nnet.sh, now script supports both nnet2 and nnet3. Probably nnet1. 2016-05-09 17:37:32 +00:00
misc master: merging most code changes from chain branch (but not the actual chain code)-- want to keep shared parts of the code the same. 2016-01-07 22:45:39 -08:00
src some cosmetic changes: add comments to RNNLM rescoring utilities to refer to each other; improve messages printed out by 'configure' 2016-05-09 00:54:44 -04:00
tools Fix undefined variable issue in install_irstlm.sh. 2016-05-05 02:17:35 +02:00
windows adding clarification about recipes not working under windows 2016-04-14 14:50:15 -04:00
.gitattributes Don't mangle patch file line endings in all directories 2016-01-11 11:29:00 +00:00
.gitignore typo, ignore generated VS solution 2016-03-12 20:32:20 +07:00
.travis.yml Travis CI: Do not run make test if nothing changed in src/ 2015-08-27 12:06:26 -07:00
COPYING trunk: small fix to get_lda_block.sh (thanks: mozno@users.sf.net) plus a few other unrelated small changes 2015-07-14 18:53:03 +00:00
INSTALL Merge branch 'master' into sandbox-oplatek 2013-06-18 10:56:26 +00:00
README.md my-awesome-feature: markdownify ./README 2015-08-20 09:33:53 -07:00

README.md

[Build Status] (https://travis-ci.org/kaldi-asr/kaldi)

Kaldi Speech Recognition Toolkit

To build the toolkit: see ./INSTALL. These instructions are valid for UNIX systems including various flavors of Linux; Darwin; and Cygwin (has not been tested on more "exotic" varieties of UNIX). For Windows installation instructions (excluding Cygwin), see windows/INSTALL.

To run the example system builds, see egs/README.txt

If you encounter problems (and you probably will), please do not hesitate to contact the developers (see below). In addition to specific questions, please let us know if there are specific aspects of the project that you feel could be improved, that you find confusing, etc., and which missing features you most wish it had.

Kaldi information channels

For HOT news about Kaldi see the project site.

Documentation of Kaldi:

  • Info about the project, description of techniques, tutorial for C++ coding.
  • Doxygen reference of the C++ code.

Kaldi forums and mailing lists:

  • User list kaldi-help: Web interface/archive || [Subscribe] (mailto:kaldi-help+subscribe@googlegroups.com) || [Post] (mailto:kaldi-help@googlegroups.com)
  • Developer list kaldi-developers: Web interface/archive || [Subscribe] (mailto:kaldi-developers+subscribe@googlegroups.com) || [Post] (mailto:kaldi-developers@googlegroups.com)
  • Also try luck and search in SourceForge archives.

Development pattern for contributors

  1. Create a personal fork of the [main Kaldi repository] (https://github.com/kaldi-asr/kaldi) in GitHub.
  2. Make your changes in a named branch different from master, e.g. you create a branch my-awesome-feature.
  3. Generate a pull request through the Web interface of GitHub.
  4. As a general rule, please follow [Google C++ Style Guide] (https://google-styleguide.googlecode.com/svn/trunk/cppguide.html). There are a few exceptions in Kaldi. You can use the [Google's cpplint.py] (https://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py) to verify that your code is free of basic mistakes.