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

Segmentation by difference between models' performance #114

Open
Firenze11 opened this issue Feb 23, 2020 · 0 comments
Open

Segmentation by difference between models' performance #114

Firenze11 opened this issue Feb 23, 2020 · 0 comments
Labels
enhancement New feature or request rfc Request for comments

Comments

@Firenze11
Copy link
Contributor

Summary

Currently we have allow users to slice by baseCols, which can be one of:

  1. feature columns
  2. prediction columns
  3. score/performance columns

But sometimes, especially in manual segmentation, something like the difference between two score/performance columns would be desirable.

Possible Solution

  • Allow users to define column computation logic in UI, e.g. @score:0 MINUS @score:1
  • Compute these columns once they are defined, append them to column list
  • Allow deletion of these columns (in the database representation we will set it to null instead of actually deleting it, to avoid column index shift
@Firenze11 Firenze11 added enhancement New feature or request rfc Request for comments labels Feb 23, 2020
@Firenze11 Firenze11 added this to the P1 - strategic features milestone Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request rfc Request for comments
Projects
None yet
Development

No branches or pull requests

1 participant