It's possible to use relative paths in moses.ini if moses binary is called
in the correct cwd.

2017年6月29日 下午9:09,"liling tan" <alvati...@gmail.com>寫道:

> Awesome, thanks Hieu!!
>
> On 29 Jun 2017 8:20 p.m., "Hieu Hoang" <hieuho...@gmail.com> wrote:
>
>> ./moses -feature-overwrite "TranslationModel0
>> path=/home/someoneelse/anotherpath/phrasemodel/work.src-trg/
>> training/model/phrase-table.gz"  -f moses.ini < input.txt > output.txt
>>
>> Hieu Hoang
>> http://moses-smt.org/
>>
>>
>> On 29 June 2017 at 10:44, liling tan <alvati...@gmail.com> wrote:
>>
>>> Dear Moses community,
>>>
>>> When decoding, it's easy to use the moses.ini if the paths are fixed.
>>> But if the model has to be moved around different machines / users, it's a
>>> little messy to replace the paths to the correct ones.
>>>
>>> Is it possible to set the paths in moses.ini when calling the moses
>>> binary on the CLI?
>>>
>>> More specifically, is ther a way to overwrite the paths parameters in
>>> the [feature]?
>>> E.g. in the moses.ini, there's
>>>
>>> PhraseDictionaryMemory name=TranslationModel0 num-features=4
>>> path=/home/alvas/experiments/phrasemodel/work.src-trg/training/model/phrase-table.gz
>>> input-factor=0 output-factor=0
>>>
>>> Is there an equivalent CLI parameter that can overwrite the path? e.g.
>>>
>>> ./moses --phrase-dictionary-memory-path= /home/someoneelse/anotherpath/
>>> phrasemodel/work.src-trg/training/model/phrase-table.gz  -f moses.ini <
>>> input.txt > output.txt
>>>
>>> Thanks in advance for the answer!
>>>
>>> Regards,
>>> Liling
>>>
>>>
>>>
>>> _______________________________________________
>>> Moses-support mailing list
>>> Moses-support@mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/moses-support
>>>
>>>
>>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support

Reply via email to