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.

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

use prodigy with mixedin data and pretrained spacy ner model get error. #13

Open
YanLiang1102 opened this issue Jun 30, 2018 · 7 comments

Comments

@YanLiang1102
Copy link
Collaborator

I created an issue in Spacy for this.

@YanLiang1102
Copy link
Collaborator Author

explosion/spaCy#2496

@YanLiang1102
Copy link
Collaborator Author

well I hard coded and put the model path inside of spacy source code in here
File "/usr/local/lib/python3.5/dist-packages/spacy-2.0.12.dev0-py3.5-linux-x86_64.egg/spacy/util.py", line 119, in load_model
but after training for like 30 mins got and segmentation fault error.....:(

@YanLiang1102
Copy link
Collaborator Author

YanLiang1102 commented Jul 12, 2018

well that is becasue it uses up all the memory since the big pretrained vectors,
so use the our own vector and finally get it trained,
I made virtual environment and rebuild all the dependecy
and finally get it to run.
here is the perfomance with only the ldcdaat+prodigy data not perfect, since it is using ontoNotes orginal format, it dose not take advantage of the tag clustering stuff, we have and the anercorp data is not merged in too.
image
@ahalterman

@YanLiang1102
Copy link
Collaborator Author

@andy what is that BEFORE accuracy mean Andy? the 0.029 the mixed in ratio I am using is 5
so prodigy has 801 records, we will mix in the first 4005 records of onto_notes to the augmented data set.

@YanLiang1102
Copy link
Collaborator Author

also I need to manually copy the ar model into the dist-package forder for the virtual environment in order to fix the problem

@ahalterman
Copy link
Collaborator

The BEFORE is built in to Prodigy, I think. It just applies the existing model to the entities and reports the accuracy. So that must be the accuracy on model9.

@YanLiang1102
Copy link
Collaborator Author

I mean that accuracy is definitely not right on model9 it should be around 55% I guess that is with "the new format data" on model9?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants