Skip to content

Test that all rows of a competition test set will have at least a value#116

Merged
kirahowe merged 1 commit into
feat/competitionsfrom
km/competition-additions
Jun 27, 2024
Merged

Test that all rows of a competition test set will have at least a value#116
kirahowe merged 1 commit into
feat/competitionsfrom
km/competition-additions

Conversation

@kirahowe

Copy link
Copy Markdown
Contributor

Changelogs

  • adds some validation on competition creation to check that all test rows will have at least one value in a target column

Checklist:

  • Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
  • Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).
  • [-] Update the API documentation if a new function is added, or an existing one is deleted.
  • Write concise and explanatory changelogs above.
  • If possible, assign one of the following labels to the PR: feature, fix or test (or ask a maintainer to do it for you).

This is a small improvement discussed with Andrew before his vacation. We want to make sure that you can't create a competition where there is missing test data.

@kirahowe kirahowe added the feature Annotates any PR that adds new features; Used in the release process label Jun 26, 2024
@kirahowe kirahowe requested a review from cwognum as a code owner June 26, 2024 11:17
@kirahowe kirahowe changed the title test that all rows of a competition test set will have at least a value Test that all rows of a competition test set will have at least a value Jun 26, 2024
@kirahowe kirahowe merged commit 66c1913 into feat/competitions Jun 27, 2024
@kirahowe kirahowe deleted the km/competition-additions branch June 27, 2024 18:34
Andrewq11 added a commit that referenced this pull request Aug 19, 2024
* competition wip

* wip

* wip

* adding methods for interfacing w/ competitions

* Continuing to integrate polaris client with the Hub for comps

* comp wip

* updating date serializer

* Competition evaluation (#103)

* call hub evaluate endpoint from client evaluate_competitions method

* add super basic test for evaluating competitions

* be more specific in evaluate_benchmark signature

* Update polaris/hub/client.py

Co-authored-by: Andrew Quirke <75542075+Andrewq11@users.noreply.github.com>

* start refactoring object dependencies out of evaluation logic

* refactor test subset object out of evaluation logic

* clean up as much as possible for now

* updating date serializer

* call hub evaluate endpoint from client evaluate_competitions method

* Update polaris/competition/_competition.py

Co-authored-by: Andrew Quirke <75542075+Andrewq11@users.noreply.github.com>

* updating date serializer

* call hub evaluate endpoint from client evaluate_competitions method

* add super basic test for evaluating competitions

* comp wip

* updating date serializer

* call hub evaluate endpoint from client evaluate_competitions method

* fix bad merge resolution

* only send competition artifact ID to hub

---------

Co-authored-by: Andrew Quirke <75542075+Andrewq11@users.noreply.github.com>
Co-authored-by: Andrew Quirke <andrewquirke99@gmail.com>

* Use evaluation logic directly in hub, no need for wrapper (#109)

* use evaluation logic directly in hub, no need for wrapper

* include evaluate_benchmark in package

* remove unnecessary imports

* read incoming scores sent as json

* light formatting updates

* updating fallback version for dev build

* integrating results for comps (#111)

* integrating results for comps

* Update polaris/hub/client.py

Co-authored-by: Cas Wognum <caswognum@outlook.com>

* addressing comments & adding CompetitionResults class

* test competition evalution works for multi-column dataframes

* add single column test to competition evaluation

* fix multitask-single-test-set cases

* fix bug with multi-test-set benchmarks

* adding functions to serialize & deserialize pred objs for external eval

* updating return for evaluate_competition method in client

* updating evaluate_competition method to pass additional result info to hub

---------

Co-authored-by: Cas Wognum <caswognum@outlook.com>
Co-authored-by: Kira McLean <email@kiramclean.com>

* updates to enable fetching & interacting with comps

* updating requirement for eval name

* Feat/competition/eval (#114)

* integrating results for comps

* Update polaris/hub/client.py

Co-authored-by: Cas Wognum <caswognum@outlook.com>

* addressing comments & adding CompetitionResults class

* test competition evalution works for multi-column dataframes

* add single column test to competition evaluation

* fix multitask-single-test-set cases

* fix bug with multi-test-set benchmarks

* adding functions to serialize & deserialize pred objs for external eval

* updating return for evaluate_competition method in client

* updating evaluate_competition method to pass additional result info to hub

* refuse early to upload a competition with a zarr-based dataset

* removing merge conflicts

---------

Co-authored-by: Andrew Quirke <andrewquirke99@gmail.com>
Co-authored-by: Andrew Quirke <75542075+Andrewq11@users.noreply.github.com>
Co-authored-by: Cas Wognum <caswognum@outlook.com>

* test that all rows of a competition test set will have at least a value (#116)

* update competition evaluation to support y_prob

* run ruff on all files and fix issues

* fix wrong url printout after upload

* Clarifying typing for nested types

* removing if_exists arg from comps

* raising error for trying to make zarr comp

* updating name of ArtifactType to ArtifactSubtype

* updating comments & removing redundant class attributes

* moving split validator logic from comp spec to benchmark spec

* removing redundant checks from CompetitionDataset class

* creating pydantic model for comp predictions

* split validator logic, redundant pydantic checks, comp pred pydantic model

* changes for comps wrap up

* Adding CompetitionsPredictionsType

* adding conversion validator for comp prediction type

* setting predictions validator as class method

* Using self instead of cls for field validators

* removing model validation on fetch from hub

* Creating HubOwner object in comp result eval method

* Documentation & tutorials for competitions

* Removing create comp method, fixing failing tests, updating benchmark label struct

* Updating docs for create comp & benchmark pred structure

* tiny wording change in competition tutorial

* Addressing PR feedback

* fixing tests & removing dataset redefinition from CompetitionDataset class

* Commenting out line in tutorial to fix test

* fixing formatting

* small fixes & depending on tableContent for dataset storage info

---------

Co-authored-by: Andrew Quirke <andrewquirke99@gmail.com>
Co-authored-by: Andrew Quirke <75542075+Andrewq11@users.noreply.github.com>
Co-authored-by: Cas Wognum <caswognum@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Annotates any PR that adds new features; Used in the release process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant