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.

Sign up for GitHub

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

Jump to bottom

Return loss (cost) of the solution found #174

Closed
kno10 opened this issue Jan 12, 2022 · 1 comment · Fixed by #178
Closed

Return loss (cost) of the solution found #174

kno10 opened this issue Jan 12, 2022 · 1 comment · Fixed by #178
Assignees
@motiwari

Comments

@kno10
Copy link

kno10 commented Jan 12, 2022

At least the python wrapper does not appear to allow access to the loss of the solution returned.
When comparing the quality of multiple restarts it would be convenient to have this value, instead of needing to recompute it.
@motiwari motiwari self-assigned this Jan 14, 2022
motiwari pushed a commit that referenced this issue Jan 14, 2022
Adding getLossFunction and getAverageLoss, as well as some partial fi…
628ba96 
…xes for #173 and #174
motiwari pushed a commit that referenced this issue Jan 14, 2022
Adding attribute KMedoids.average_loss. Fixes #174
d0684d4
This was referenced Jan 14, 2022
Closed
Merged
@motiwari
Copy link
Owner

Thanks @kno10 ; now the KMedoids object has an average_loss attribute; see the README for an example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@motiwari motiwari

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

BanditPAM v3.0.2 motiwari/BanditPAM
2 participants
@kno10 @motiwari