-
Notifications
You must be signed in to change notification settings - Fork 48
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
parser doesn't produce amr-unknown #14
Comments
parsing the same sentence with amrlib parser, for example, gives me this result with amr-unknown:
|
It should produce amr-unknown, we use this often for question parsing. What did you trained it with? I just checked on a v0.4.2 deploy and it parses correctly. Also, do you tokenize? |
hi @ramon-astudillo, well, I was trying to follow your setup instructions from here for setup and training (the default action-pointer network config
|
would mind sharing your trained checkpoint to see if it makes any difference? |
I am certain it should. We are looking into sharing pre-trained models but I can not say anything at this point. Also FYI we will update to From experience in parsing questions, I can say silver-data fine-tuning works well. You can parse some text corpus with questions, filter it with a couple of rules*, and the use it as additional training data. The training scheme silver+gold pre-training with gold fine-tuning seems to work best, see e.g. https://aclanthology.org/2020.findings-emnlp.288/ (*) For example ignore all parses having |
I was able to train the parser as per your instructions. But when testing the trained model I found that it didn't produce amr-unknown node. For example:
The text was updated successfully, but these errors were encountered: