



\section{
\label{advanced-features.tex}
User Documentation}


The basic features of the decoder are explained in the Tutorial (Section \ref{tutorial.tex}) and Training sections. But to get good results from Moses you probably need to use some of the features described in this page.






\begin{description}\item[Advanced Models (Section \ref{advanced-models.tex})] A basic SMT system contains a language model and a translation model, however there are several ways to extend this (and potentially improve translation) by adding extra models. These may improve the modelling of reordering, for example, or capture similarities between related words.
\item[Efficient Phrase and Rule Storage (Section \ref{advanced-ruletables.tex})] To build a state-of-the-art translation system, Moses often requires huge phrase-pair or rule tables. The efficient storage and access of these tables requires specialised data structures and this page describes several different implementations.
\item[Search (Section \ref{advanced-search.tex})] Given an MT model and a source sentence, the problem of finding the best translation is an intractable search problem. Moses implements several methods for taming this intractability.
\item[Unknown Words (Section \ref{advanced-oovs.tex})] No matter how big your training data is, there will always be OOVs (out-of-vocabulary words) in the text you wish to translate. One approach may be to transliterate - if your source and target languages have different character sets.
\item[Hybrid Translation (Section \ref{advanced-hybrid.tex})] Sometimes you need rules! If you want to add explicit knowledge to Moses models, for example for translating terminology or numbers, dates etc., Moses has a few ways of making this possible.
\item[Moses as a Service (Section \ref{advanced-moses.tex})] Moses includes a basic server which can deliver translations over xml-rpc.
\item[Incremental Training (Section \ref{advanced-incremental.tex})] The traditional Moses pipeline is a sequence of batch processes, but what if you want to add extra training data to a running system? Storing the phrase table in a suffix array makes this possible.
\item[Domain Adaptation (Section \ref{advanced-domain.tex})] When the training data differs in a systematic way from the test data you have a domain problem. Several techniques have been proposed in the literature have been proposed and Moses includes implementations of many of them.
\item[Constrained Decoding (Section \ref{advanced-constrained.tex})] In some applications, you know that translation but you need to know how the model derived it.
\item[Cache-based Models (Section \ref{advanced-cachebased.tex})] These can be a useful way for the document context to influence the translation.
\item[Sparse features (Section \ref{sparse-features.tex})] Feature functions that produce many features, for instance lexicalized features
\item[Support Tools (Section \ref{support-tools.tex})] Various tools to manipulate models and configuration files.
\item[External Tools (Section \ref{external-tools.tex})] Linguistic tools, word aligners, evaluation metrics and frameworks, other open source machine translation systems.
\item[Web Translation (Section \ref{web-translation.tex})] Web service software to translate web pages and text on demand.
\item[Pipeline Creation Language (Section \ref{advanced-pcl.tex})] A generic mechanism for managing pipelines of software components, such as Moses training.
\item[Obsolete Features (Section \ref{advanced-obsolete.tex})] Things that have been removed, but documentation is preserved for posterity.
\end{description}









\begin{center}\textit{\small Subsection last  modified on December 23, 2015, at 05:43 PM}\end{center}
