Skip to content

refactor: remove kmedoids from default pipeline strategies - #40

Merged
Harsh16gupta merged 1 commit into
masterfrom
remove-kmedoids-pipeline
Aug 7, 2026
Merged

refactor: remove kmedoids from default pipeline strategies#40
Harsh16gupta merged 1 commit into
masterfrom
remove-kmedoids-pipeline

Conversation

@Harsh16gupta

Copy link
Copy Markdown
Collaborator
  • Remove kmedoids-auto strategy from createAdaptiveConfig() and createPipelineConfig()
  • Add comments in kmedoids.ts, autoK.ts, benchmark.ts, cluster.ts noting kmedoids is retained but not active (too slow ~38s for ~500 notes)
  • Remove K-Medoids references from README.md
  • Clean up kmedoids references in StrategySection.tsx and AppStateContext.tsx
  • Update pipelineConfig tests to reflect 2 strategies instead of 3

@Harsh16gupta

Copy link
Copy Markdown
Collaborator Author

when i was testing on 500 notes then the kmedoids was very slow
kmedoids-auto | kmedoids | 10 | 0.5919 | 0 | 37765ms | [62, 42, 79, 80, 80, 37, 39, 19, 47, 11]
so i have removed it

- Remove kmedoids-auto strategy from createAdaptiveConfig() and createPipelineConfig()
- Add comments in kmedoids.ts, autoK.ts, benchmark.ts, cluster.ts noting
  kmedoids is retained but not active (too slow ~38s for ~500 notes)
- Remove K-Medoids references from README.md
- Clean up kmedoids references in StrategySection.tsx and AppStateContext.tsx
- Update pipelineConfig tests to reflect 2 strategies instead of 3
@Harsh16gupta
Harsh16gupta force-pushed the remove-kmedoids-pipeline branch from 432b7e5 to b0e7ba3 Compare August 7, 2026 13:00
@Harsh16gupta
Harsh16gupta merged commit e6d30fd into master Aug 7, 2026
1 check passed
@Harsh16gupta

Copy link
Copy Markdown
Collaborator Author

The pipeline is still there in the code but we don't run the pipeline on every run. If we want to go back to the k-medoids, we can easily do that

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.

1 participant