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

Fit Predict method #4

Closed
momonga-ml opened this issue Aug 9, 2021 · 3 comments · Fixed by #40
Closed

Fit Predict method #4

momonga-ml opened this issue Aug 9, 2021 · 3 comments · Fixed by #40
Assignees
Labels
good first issue Good for newcomers

Comments

@momonga-ml
Copy link
Contributor

Currently, no fit predict is supported. Behaviour is desirable and probable would need to use Parametric UMAP base or other means as workaround.

@momonga-ml
Copy link
Contributor Author

Also see #10

@matthewmeadows81
Copy link

For the RandomizedSearchCV I get TypeError: _BaseScorer.call() missing 1 required positional argument: 'y_true' for random_search.fit(coordinates) when I place error_score="raise". Really like the code, but when I run it with GridSearchCV to see if it works it doesn't choose the optimal parameters.

@momonga-ml
Copy link
Contributor Author

@matthewmeadows81 This is the following the "Tuning with HDBSCAN" example which initializes `validity_scorer = make_scorer(hdbscan.validity.validity_index,greater_is_better=True)?

As for the issue with GridSearchCV not choosing the optimal parameters, it could be due to a number of reasons. It could be that the scoring metric you're using is not suitable for your data or problem, or it could be that the range of parameters you're searching over does not include the optimal parameters.
`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants