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

Refactor no answer handling in Question Answering #258

Merged
merged 10 commits into from
Feb 24, 2020
Merged

Conversation

Timoeller
Copy link
Contributor

@Timoeller Timoeller commented Feb 20, 2020

This PR will need adjustments from downstream applications consuming QA inference, since we now return None for no answer (instead of empty string)

  1. Change naming to no answer boost.
  2. Change how no answer score is computed.
  3. Predictions contain a no answer along positive answers, the no answer score is relative to positive answers.

Copy link
Member

@tholor tholor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Minor comments

examples/question_answering.py Outdated Show resolved Hide resolved
farm/modeling/prediction_head.py Outdated Show resolved Hide resolved
@Timoeller Timoeller requested review from tholor and removed request for tholor February 24, 2020 09:24
@Timoeller Timoeller self-assigned this Feb 24, 2020
@Timoeller Timoeller merged commit 875f8c6 into master Feb 24, 2020
@Timoeller Timoeller deleted the no_ans_boost branch February 24, 2020 09:45
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

Successfully merging this pull request may close these issues.

None yet

2 participants