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

Fix a bug in the old scoring API when introducing the new API in TPOT 0.9.1 #626

Merged
merged 11 commits into from
Nov 28, 2017

Conversation

weixuanfu
Copy link
Contributor

  1. Fix a bug in the new scoring API in TPOT 0.9.1, which cause TPOT cannot recognize the scoring function in the old scoring API (which will be removed in version 0.11).

  2. Add two unit tests for the related issue RuntimeError in the TPOT optimization #625

Questions:

  • Do the docs need to be updated? No
  • Does this PR add new (Python) dependencies? No

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.06%) to 96.781% when pulling ade169e on weixuanfu:scoring_api_bug into 01dfc11 on rhiever:development.

@weixuanfu weixuanfu changed the title Scoring api bug Fix a bug in the old scoring API when introducing the new API in TPOT 0.9.1 Nov 17, 2017
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 96.643% when pulling f32aaa3 on weixuanfu:scoring_api_bug into 01dfc11 on rhiever:development.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 96.643% when pulling f32aaa3 on weixuanfu:scoring_api_bug into 01dfc11 on rhiever:development.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 96.643% when pulling eea8749 on weixuanfu:scoring_api_bug into 01dfc11 on rhiever:development.

@weixuanfu weixuanfu merged commit eea8749 into EpistasisLab:development Nov 28, 2017
This was referenced Jan 2, 2018
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