Skip to content

Conversation

albertoandreottiATgmail
Copy link
Contributor

@albertoandreottiATgmail albertoandreottiATgmail commented Jan 26, 2018

Description

With this PR we introduce the Assertion Status Annotator.

Motivation and Context

New feature.

How Has This Been Tested?

Tested on real data both at mode and pipeline levels.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Code improvements with no or little impact
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING page.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@saif-ellafi
Copy link
Contributor

Please fix python notebook example and we are good to go,

although there are a few things I would like to change sometime:

  1. see if we can better use tokenizer and document assembler in the model
  2. change parquet labelMap into Feature[Map[String, Double]] It will be faster to use binary format than parquet
  3. use spark.read.parquet instead of sqlContext
  4. help me understand windowing trait some day :) It confuses me quite. Also, any chance for any other type of tokenization process might be involved?

saif-ellafi and others added 6 commits January 27, 2018 12:37
- Updated LogReg to use read and write standard traits
…ents' into assertion_status

src/main/scala/com/johnsnowlabs/nlp/annotators/assertion/logreg/AssertionLogRegModel.scala
@saif-ellafi saif-ellafi merged commit 2507dc6 into master Jan 27, 2018
@maziyarpanahi maziyarpanahi deleted the assertion_status branch March 29, 2021 15:16
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.

2 participants