-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
45 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
.. xnmt documentation master file, created by | ||
eXtensible Neural Machine Translation (xnmt) | ||
============================================ | ||
|
||
This is a repository for the extensible neural machine translation toolkit ``xnmt``. | ||
It is coded in Python based on `DyNet <http://github.com/clab/dynet>`. | ||
|
||
Usage Directions | ||
---------------- | ||
|
||
If you want to try to run an experiment, you can do so using sample configurations in the ``examples`` | ||
directory. For example, if you wnat to try the default configuration file, | ||
which trains an attentional encoder-decoder model, you can do so by running | ||
|
||
python xnmt/xnmt_run_experiments.py examples/standard.yaml | ||
|
||
There are other examples here: | ||
|
||
* ``examples/standard.yaml``: An attentional encoder-decoder model | ||
* ``examples/debug.yaml``: A simple debugging configuration that should run super-fast | ||
* ``examples/speech.yaml``: An example of speech-to-text translation | ||
|
||
See ``experiments.md`` for more details about writing experiment configuration files. | ||
|
||
Programming Style | ||
----------------- | ||
|
||
The over-arching goal of ``xnmt`` is that it be easy to use for research. When implementing a new | ||
method, it should require only minimal changes (e.g. ideally the changes will be limited to a | ||
single file, over-riding an existing class). Obviously this ideal will not be realizable all the | ||
time, but when designing new functionality, try to think of this goal. | ||
|
||
There are also a minimal of coding style conventions: | ||
* Follow Python conventions, and be Python2/3 compatible. | ||
* Functions should be snake case. | ||
* Indentation should be two whitespace characters. | ||
|
||
We will aim to write unit tests to make sure things don't break, but these are not implemented yet. | ||
|
||
In variable names, common words should be abbreviated as: | ||
* source -> src | ||
* target -> trg | ||
* sentence -> sent | ||
* hypothesis -> hyp |