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

Basic ranking methods for results organization module #18

Open
1 of 4 tasks
hannah-rae opened this issue Jun 7, 2021 · 3 comments
Open
1 of 4 tasks

Basic ranking methods for results organization module #18

hannah-rae opened this issue Jun 7, 2021 · 3 comments

Comments

@hannah-rae
Copy link
Contributor

hannah-rae commented Jun 7, 2021

We discussed having some basic methods for returning a list of items with their outlier scores, which should be implemented as separate results organization modules:

  • Output list of items in the order they are returned by the algorithm (algorithm-order)
  • Output list of items in the order they are read by the data loader and passed to the algorithms (item- or original-order)
  • Output list of items in order of ascending outlier score (ascending-order)
  • Output list of items in order of descending outlier score (descending-order)
@hannah-rae
Copy link
Contributor Author

We talked early on about having different options for what order to save the results in. Currently the save_scores module saves samples in descending outlier order (most outlier-y to least). We could add a parameter that would allow the user to specify the order that the samples are written in the csv based on these four options. I'm curious to hear from others if you agree with that solution and if you think it would be useful still?

cc @stevenlujpl @wkiri @urebbapr @bdubayah

@wkiri
Copy link
Collaborator

wkiri commented Oct 25, 2021

@hannah-rae In terms of saving time/effort, it seems like the user can already achieve all of these by sorting on different columns in the output .csv file, right? Also I believe the option currently implemented is the first one (algorithm-order) rather than sorting by score.

@stevenlujpl
Copy link
Collaborator

@hannah-rae I am not sure if I understand the algorithm-order and item-order methods. in terms of supporting ascending-order, we may also need to modify the outlier ranking algorithms.

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

No branches or pull requests

3 participants