Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Timeout #11

Open
Liontooth opened this issue Aug 10, 2014 · 2 comments
Open

Timeout #11

Liontooth opened this issue Aug 10, 2014 · 2 comments

Comments

@Liontooth
Copy link

The stanford-ner server finds some strings unparsable. I have relatively dirty data with stray characters like BOM and NULL, not to mention non-US characters like ç, so pyner hangs. Could we have a timeout, perhaps in socket? I'm using ner.SocketNER and I'm surprised and delighted how fast it is - thank you!

Category wishlist

Cheers,
Dave
@dat
Copy link
Owner

dat commented Sep 1, 2014

Sorry for the delayed response, but I've been busy with other commitments. Do you have a patch for that socket timeout by any chance? I'm happy to take a look and merge if it looks good.

@Liontooth
Copy link
Author

Thanks for the response!. Sorry, I don't know socket well enough.

Incidentally, I've used pyner for Stanford NLP Parts of Speech, changing NER to POS and it works fine.

erickpeirson added a commit to erickpeirson/pyner that referenced this issue May 3, 2015
@erickpeirson
changed the way that SocketNER retrieves data from the socket server;…
42ed5c8 
… may address issue dat#14 and issue dat#11.
@erickpeirson erickpeirson mentioned this issue May 3, 2015
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dat @Liontooth