Hello Lane,
frankly I don't see this as sooo desireable. You just exchange a magic
character with an even more magic one. Since the proposed character is
not an ASCII character you'll eventually run into encoding problems. And
for most people it'd be very difficult to type this character on
Hi,
train-model.perl with the parameter -phrase-word-alignment adds
word-for-word alignment information to the phrase table. Unfortunately
this information get's lost when converting the textual phrase-table
into a binary format with processPhraseTable. Using
processPhraseTable
Hi,
I saw that KenLM source code is distributed from the Moses svn and can
set in configure. Is anybody here using it and willing to share some
experiences? Is it thread-safe and can used in Moses together with SRI
and IRST ? Any particular advantages? Is there any more information than
Hello Souhir,
are you using a recent revision of moses? My phrase tables look a bit
different from yours.
To see the alignment information I use the switches:
-use-alignment-info -print-alignment-info -T file
and the alignment information is written to the file.
best regards
Christof
||| pp.nlog_pte;
still prints things in the correct order (pt-filter.cpp lines 144 - 145.
best regards
Christof
On 9/24/10 1:37 PM, Christof Pintaske wrote:
Hi,
I just updated my moses installation to trunk. Unfortunately I found
that filter-pt is now crashing instead of pruning. The patch
where did you get your Moses installation from? train-model.perl
should be in moses/bin/scripts-*/training . At least it has always been
there for me. If that's not the case then you may want to check the
source or checkout a new version from the repository.
hope that helps
Christof
Dear
On 5/20/10 8:12 PM, yifeng...@sina.com wrote:
In Factored Tutorial, the first example is:
% train-model.perl \
--corpus factored-corpus/proj-syndicate \
--root-dir unfactored \
--f de --e en \
--lm 0:3:factored-corpus/surface.lm:0
I think the language model is usually used in the decoding
Hi,
you may want to have a closer look at tokenizer.perl which is used for
word-breaking. It seems there is some special logic to handle English,
French, and Italian but nothing much else.
I'm not sure if you can or plan to reveal your findings here on the list
but at any rate I'd be very
Hi,
in parse-de-bitpar.perl the code sequence
while(STDIN)
{
foreach (split)
{
s/\(/\*LRB\*/g;
s/\)/\*RRB\*/g;
print TMP $_.\n;
}
print TMP \n;
}
adds a newline after each single word. Is this required? To me it looks
like bitpar parses sentences
Hi,
I'm playing with bitpar for parsing and annotating English content. I
modified parse-de-bitpar.perl to use the TraceParser grammar files
instead of the German Tiger files. When I tried to annotate my corpus
parse-de-bitpar.perl died on me on two occasions:
1. a grammar like (a (b (c))(d))
Hi,
here's a minor discovery in phrase_extract
phrase_extract does not give any usage information, even though it seems
somebody had the intention to do so:
if (argc 1)
{
cerr syntax: relax-parse in-parse out-parse [
--LeftBinarize | ---RightBinarize |
things?
best regards
Christof
On 01/02/2010 19:13, Christof Pintaske wrote:
Hi,
while running mert-moses-new.pl to tune the chart-decoder I get this output:
[...]
The decoder returns the scores in this order: lm tm tm tm tm tm tm w
[...]
Executing: /export/home/moses/libexec/moses
Hi Christopher,
when I tried to build srilm on a amd64 machine running Linux, I found
that srilm used the common/Makefile.machine.i686 Makefile. This, in
turn, defines compiler flags GCC_FLAGS = -m32 -mtune=pentium3 -W
I removed the -m32 -mtune=pentium from the flags to build regular 64
I'd think that you did not compile or link successfully against SRILM.
As a consequence LanguageModelInternal tries to load the language model
as opposed to being overloaded by the correct SRILM code.
just my 2 cents
Christof
Panagiotis Kanavos wrote:
Hi,
I downloaded moses from svn and
file format so the chart decoder
isn't backwardly compatible. You should use the trunk decoder if the
data was trained using the trunk scripts
On 22/01/2010 00:20, Christof Pintaske wrote:
Hi,
is the moses/moses_chart executable from the mt3_chart branch supposed
to be usable
Hi,
my extract.o.gz respectively extract.o.sorted produce a large number
of error messages: buggy line. For example:
buggy line (o_previous:): [X] , [X] and ||| [X] , [X] et |||
buggy line (o_following:): [X] , [X] and ||| [X] , [X] et |||
in fact extract has generated the respective line(s)
, Jan 20, 2010 at 11:05 PM, Christof Pintaske
christof.pinta...@sun.com wrote:
Hi,
my extract.o.gz respectively extract.o.sorted produce a large number
of error messages: buggy line. For example:
buggy line (o_previous:): [X] , [X] and ||| [X] , [X] et |||
buggy line (o_following:): [X] , [X
?
best regards
Christof
Christof Pintaske wrote:
Hi,
I created a 3-gram LM with the irstlm toolkit (5.0.22). The LM has about
25M entries:
ngram 1= 300209
ngram 2= 4864097
ngram 3= 20336549
I tried to prune it with prune-lm on a Linux machine.
prune-lm --threshold=1e-6,1e-6
18 matches
Mail list logo
