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-prediction-inverse-mapping #9

Merged
merged 1 commit into from
May 26, 2024

Conversation

sumanthprabhu
Copy link
Owner

  • predicted_label returned by CrossValCurate.fit_transform contains integer values irrespective of the data type in the input label column. Fix this by mapping the predictions to the corresponding value in the input label list.
  • Add sanity checks to handle cases where input labels can be blank strings
  • Add the corresponding tests

- `predicted_label` returned by `CrossValCurate.fit_transform` contains integer values irrespective of the data type in the input label column. Fix this by mapping the predictions to the corresponding value in the input label list.
- Add sanity checks to handle cases where input labels can be blank strings
- Add the corresponding tests
@sumanthprabhu sumanthprabhu merged commit 5481bac into main May 26, 2024
2 checks passed
@sumanthprabhu sumanthprabhu deleted the Fix-prediction-inverse-mapping branch May 26, 2024 14:31
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.

Datatype mismatch between input labels and predicted_label returned by CrossValCurate.fit_transform
1 participant