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

New version: MLJMultivariateStatsInterface v0.5.0 #68737

Merged

Conversation

JuliaRegistrator
Copy link
Contributor

Bumps the MultivariateStats requirement to 0.10, which forces some breaking changes (#51; @OkonSamuel):

  • (breaking) The output of fitted_params and report for LDA models has changed. See the doc-strings for details.
  • (breaking) Interpreting some output (now and previously) needs an ordering of target classes, and this ordering may no longer agree with levels(y). However the class label order adopted is now explicitly output by fitted_params.
  • (breaking) In BayesianLDA and BayesianSubspaceLDA target class priors may no longer be specified as vectors. They must either be dictionaries or UnivariateFinite objects from CategoricalDistributions.jl.

UUID: 1b6a4a23-ba22-4f51-9698-8599985d3728
Repo: https://github.com/JuliaAI/MLJMultivariateStatsInterface.jl.git
Tree: 8bd8e29df231647b93085e1495ad1cac1188cfaf

Registrator tree SHA: 8e1a5ac2695627143951512d700c7e3c445102ec
@github-actions
Copy link
Contributor

Your new version pull request met all of the guidelines for auto-merging and is scheduled to be merged in the next round.


If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

@JuliaTagBot JuliaTagBot merged commit 0a3a55f into master Sep 21, 2022
@JuliaTagBot JuliaTagBot deleted the registrator/mljmultivariatestatsinterface/1b6a4a23/v0.5.0 branch September 21, 2022 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants