Recursive pipeline #90
Merged
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.
Description
An alternative pipeline that provides annotators with knowledge about their last-state pipeline. This allows some annotator machine learning models re-utilize current pipelines among different datasets, avoiding to have to create inner-pipelines to just run a few NLP tasks within an annotator.
Recursive Pipelines are backwards compatible and are an optional alternative which should boost training performance in some scenarios. As of this writing, Recursive pipelines only help to the CRF NER approach training stage.
Motivation and Context
Avoid unnecessary waste of time in re-creating inner pipelines just to perform nlp tasks within an annotator. Facilitates the annotator with a tool to re-utilize already trained pipeline instead.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: