-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
undefined method `children' for nil:NilClass (NoMethodError) #65
Comments
I'm seeing the same thing. Did you find a solution to this? |
I can't reproduce with my p392. Will investigate with the newer version... |
It looks like something with the latest StanfordCoreNLP. I'm not sure at this point but I did try to install your other gem (sfanford-core-nlp) and it took a lot of odd manual configuration to get running. I'll post a better report when I get to my computer (versions, os etc) |
I just got this with treat (2.0.7) with the automatic installer. |
has anyone managed to fix this one? |
still not working. 2.1.2 :001 > require 'treat' 2.1.2 :005 > sent.apply(:tag => :stanford) => Sentence (77529910) --- "This is an [...] to me!" --- {:tag_set=>nil, :tag=>"S"} --- [] ls $GEM_HOME/gems/stanford-core-nlp-0.5.1/bin |
Are you using the latest version of StanfordCoreNLP files from the Stanford website, or are you downloading from my website (linked in the Manual)? |
Also, can you please test on 1.9.3.xxx and let me know if the bug reproduces there? |
I get the same thing with ruby 1.9.3:
|
(and 2.1.2, which is what I tried first) |
Getting this same error, did anyone find a solution yet? |
I ended up using https://github.com/louismullie/stanford-core-nlp directly |
@cheerfulstoic I just downloaded that myself |
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:
Specifically, I think the failure occurs a little further up the chain at
Since I'm unclear whether it's a problem with the Any ideas why |
Ok, so this is interesting. If I tokenize first, then parsing appears to be working. For example: FAILS:
WORKS:
Not sure why, but that seems to work. |
@ojak - indeed, as per the manual the parser requires tokenization. However it seems like the OP was appropriately tokenizing the sentences and still running into issues. |
@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, and stanford-core-nlp 0.5.1 with the complete JAR installed under RVM. |
@gabro @acrookston - Does
|
Seeing this issue too. |
same here
|
I had the same problem, and preforming tokenization before parsing did resolved the problem. That makes sense as a pipeline, but as is the documentation doesn't explain it. On the contrary, it propose the example which was pasted here several time which skip the tokenization. The code should seamlessly run |
I'm trying to parse a document, but I get this error. Here's my code attempt
And here's the stacktrace
I used the automatic installer and manually installed Enju, which is in my PATH.
Any idea on why I'm getting such error?
The text was updated successfully, but these errors were encountered: