Oliver Jakubiec

Same issue. I can get Stanford Core NLP running on my machine, but unfortunately I can't get Treat to parse on either 1.9.3 or 2.1.4. Here's what I'm seeing: ```...

Ok, so this is interesting. If I tokenize first, then parsing appears to be working. For example: **FAILS:** Calling `parse` directly on the string. ``` 2.1.4 :001 > 'This is...

@louismullie - I see, so the OP's problem is different from the others (and mine). FYI, I was also unable to reproduce the OP's error on ruby 2.1.4, treat 2.1.0,...

@gabro @acrookston - Does `stanford-core-nlp` work for you outside of treat? From IRB, can you run the following without receiving an error (to ensure that the JAR's are working for...

OK, thanks. I'll look into that approach and let you know how it goes.

@nshmyrev I see, thanks for pointing that out. However, I'm unclear what the initial value would be, since it's a moving target based on the input device. My understanding is...

Well, this is what I saw for the **"hello"** example above: ``` ruby > decoder.configuration.details('cmninit')[:value] => "8.0" > decoder.decode('hello.wav'); puts decoder.hypothesis oh => nil > decoder.configuration.details('cmninit')[:value] => "40,3,-1" > decoder.decode('hello.wav');...

@watsonbox Another possibility is to enable a brute-force approach by default. Something like: 1. If the input is an **audio file**, the default is a two-pass decode (that can optionally...

@nshmyrev I'm having trouble locating any documentation regarding how `cmninit` works and what the comma-delimited values are. Could you point me toward any detailed docs or code? Thx.

@nshmyrev @watsonbox Actually, it looks as though there's a bunch of parameters that are not being set during the initialization of `Configuration` that are somehow being set magically after the...