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

Test to verify that custom metrics appear in model insight metrics #387

Merged
merged 5 commits into from
Aug 21, 2019

Conversation

tovbinm
Copy link
Collaborator

@tovbinm tovbinm commented Aug 20, 2019

Related issues
No tests exist to verify that custom metrics appear in model insight metrics

Describe the proposed solution
Added tests to verify that custom metrics appear in model insight metrics

Describe alternatives you've considered
N/A

@codecov
Copy link

codecov bot commented Aug 20, 2019

Codecov Report

Merging #387 into master will decrease coverage by 34.9%.
The diff coverage is 71.42%.

Impacted file tree graph

@@             Coverage Diff             @@
##           master     #387       +/-   ##
===========================================
- Coverage   86.85%   51.95%   -34.91%     
===========================================
  Files         336      336               
  Lines       10950    10955        +5     
  Branches      351      569      +218     
===========================================
- Hits         9511     5692     -3819     
- Misses       1439     5263     +3824
Impacted Files Coverage Δ
...m/salesforce/op/evaluators/EvaluationMetrics.scala 81.25% <100%> (-5.42%) ⬇️
...op/stages/impl/selector/ModelSelectorSummary.scala 85.71% <69.23%> (-6.84%) ⬇️
...sforce/op/stages/base/binary/BinaryEstimator.scala 0% <0%> (-100%) ⬇️
...la/com/salesforce/op/aggregators/Geolocation.scala 0% <0%> (-100%) ⬇️
.../scala/com/salesforce/op/test/FeatureAsserts.scala 0% <0%> (-100%) ⬇️
...la/com/salesforce/op/utils/io/avro/AvroInOut.scala 0% <0%> (-100%) ⬇️
.../salesforce/op/aggregators/FeatureAggregator.scala 0% <0%> (-100%) ⬇️
...n/scala/com/salesforce/op/readers/CSVReaders.scala 0% <0%> (-100%) ⬇️
...stages/base/sequence/BinarySequenceEstimator.scala 0% <0%> (-100%) ⬇️
.../scala/com/salesforce/op/readers/CSVDefaults.scala 0% <0%> (-100%) ⬇️
... and 170 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 07a4a73...bd6178a. Read the comment docs.

@tovbinm tovbinm changed the title Test to verify that custom metrics appear model insight metrics Test to verify that custom metrics appear in model insight metrics Aug 20, 2019
@tovbinm tovbinm requested a review from Jauntbox August 20, 2019 21:16
@tovbinm tovbinm merged commit dc64b4f into master Aug 21, 2019
@tovbinm tovbinm deleted the mt/modelInsightMetrics branch August 21, 2019 00:08
@gerashegalov gerashegalov mentioned this pull request Sep 8, 2019
gerashegalov added a commit that referenced this pull request Sep 11, 2019
Bug fixes:
- Ensure correct metrics despite model failures on some CV folds [#404](#404)
- Fix flaky `ModelInsight` tests [#395](#395)
- Avoid creating `SparseVector`s for LOCO [#377](#377)

New features / updates:
- Model combiner [#385](#399)
- Added new sample for HousingPrices [#365](#365)
- Test to verify that custom metrics appear in model insight metrics [#387](#387)
- Add `FeatureDistribution` to `SerializationFormat`s [#383](#383)
- Add metadata to `OpStandadrdScaler` to allow for descaling [#378](#378)
- Improve json serde error in `evalMetFromJson` [#380](#380)
- Track mean & standard deviation as metrics for numeric features and for text length of text features [#354](#354)
- Making model selectors robust to failing models [#372](#372)
- Use compact and compressed model json by default [#375](#375)
- Descale feature contribution for Linear Regression & Logistic Regression [#345](#345)

Dependency updates:   
- Update tika version [#382](#382)
@salesforce-cla
Copy link

Thanks for the contribution! Unfortunately we can't verify the commit author(s): Erica Chiu <e***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants