Jose,

 I just caught another part of your message "I assume that is possible 
 to transfer the scripts that I have trained on Ubuntu to Windows."

 If you're talking about transferring the training scripts to MS Windows 
 and training on Windows, this assumption is incorrect. Training a 
 translation model uses a variety of Perl & shell scripts to train the 
 language model and t-tables. Those scripts call out to various C++ apps 
 and in some cases Python scripts. Many of these scripts and C++ 
 application simply do not run on Windows. It might be possible to update 
 the Perl and Python scripts, but the shell scripts would have to be 
 re-written in another language and the C++ apps would need major work 
 because many call-out to native Posix/Linux resources (e.g. "sort").

 If you're talking about transferring the trained/tuned translation 
 models to MS Windows, the previous messages apply. The blog you refer to 
 was written in Jan 2010 and used a 2009 version of Moses with the 
 SRILM-compatible 3-gram limited language model. If this compile option 
 is still valid, you would have to train/tune translation models on 
 Linux/Posix with 3-gram SRILM-compatible language model, then 
 transfer/run them on MS Windows. KenLM language models would not be an 
 option. I don't remember if binarized phrase/reordering tables were 
 supported on Windows. Therefore, your MS Windows system would require 
 plenty of RAM resources.

 I have no idea if the newer moses code for hierarchical models would 
 compile/run as a native MS Windows app.

 Tom


 On Tue, 3 Jul 2012 17:09:15 +0100, Barry Haddow 
 <[email protected]> wrote:
> Hi Jose
>
> Moses is a command line application, so the usual way to use it on 
> windows
> would be through cygwin.
>
> If you want to use Moses in a GUI application, then probably the best 
> way is
> to run Moses server and have the GUI communicate with the server. 
> This has
> been discussed on this list before.
>
> cheers  - Barry
>
>
>
>
> On Tuesday 03 July 2012 13:03:14 Jose Casimiro Pereira wrote:
>> Hi everyone.
>>
>> First of all, I apologize for my English.
>>
>> I'm a PhD student, from Portugal, and I'm starting to study and use 
>> MOSES
>>  tool. I installed MOSES on Ubuntu and everything works fine.
>> The corpora that I have, was properly trained and worked fine with 
>> MOSES.
>>
>> For several constraints of the project I work, we need to put MOSES
>> working on Microsoft Windows.
>> I downloaded MOSES' source and compiled it, and I think it was well
>> compiled (I was inspired by Wang Pidong instructions
>> 
>> (http://wangpidong.blogspot.pt/2010/01/how-to-compile-moses-under-visual.ht
>> ml)).
>>
>> The problem that I have, and for that I ask for help, is this:
>> - how to make MOSES work on Windows? How to use MOSES to translate 
>> corpora?
>>
>> I read that is possible to transfer the training scripts from one
>> location to another. So, I assume that is possible to transfer the
>> scripts that I have trained on Ubuntu to Windows. But, again, how to 
>> use
>>  them? I haven't seen any example of it.
>>
>> There are several examples explaining how to use MOSES on Cygwin, 
>> but
>> we pretend to use it outside Cygwin.
>> I  have seen examples, too, using MOSES on Linux and accessing it
>> from Windows, using PuTTY. But, that isn't what we desired to use.
>>
>> I'll appreciate any help you could do.
>>
>> Many thanks.
>> j.casimiro
>>
>> _______________________________________________
>> Moses-support mailing list
>> [email protected]
>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>
>
> --
> Barry Haddow
> University of Edinburgh
> +44 (0) 131 651 3173
>
> --
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
> _______________________________________________
> Moses-support mailing list
> [email protected]
> http://mailman.mit.edu/mailman/listinfo/moses-support

_______________________________________________
Moses-support mailing list
[email protected]
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to