use child codes as parent in classifier#688
Merged
Merged
Conversation
9eb8aab to
0991fd2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the option (during first step of span classifier wizard) to merge child codes into parents.
This changes both the dataset statistics (shown before training) as well as the actual training data.
Given a code hierarchy like
and selecting a & b as codes, this will treat a1,a2,a11 as a, and b1,b2 as b. Thus, more fine-grained codes can be used for their coarse-grained parent codes recursively.
As child codes spans might overlap, only distinct spans (after in-place conversion to parent code) are counted for the dataset statistic. This fits the IO/BIO tagging scheme of the classifier, that can only output a single code per token.
If 'merge child codes into parents' is not used, behavior is as before.