Releases: JuliaAI/MLJBase.jl
Releases · JuliaAI/MLJBase.jl
v1.12.1
v1.12.0
MLJBase v1.12.0
- (enhancement) Arrange that the objects returned by
evaluate/evaluate!store the currently displayed "1.96SE" estimates of the radius of the confidence interval for each performance estimate, to be accessible via a new propertyuncertainty_radius_95(#1034) - (enhancement) Allow users to specify a tag for a model or machine they are evaluating, as in
evaluate("my_model"=>model, ...)in place ofevaluate(model, ...), to be accessible in the returned object via a new property,tag. Include the tag in the display of the returned object and vectors of the same (#1034) - (enhancement) Allow users to pass a vector of (possibly tagged) models or machines in
evaluate/evaluate!calls, as inevaluate([model1, model2], ...)orevaluate(["knn with K=5"=>model1, "random forest"=>model2], ...)(#1034).
Merged pull requests:
- Enhance performance evaluations (#1034) (@ablaom)
- Fix show for CompactPerformanceEvaluation (#1036) (@ablaom)
- Disambiguate internal conflict:
MMI.classesandCategoricalDistributions.classes. (#1037) (@ablaom) - For a 1.12 release (#1038) (@ablaom)
Closed issues:
v1.11.0
v1.10.1
v1.10.0
MLJBase v1.10.0
- Add support for CategoricalArrays 1.0 and CategoricalDistributions 0.2. This changes the behaviour of the re-exported methods
levelsandunique, as applied toCategoricalArrayandUnivariateFinite. Whereas previously these returned a vector of "raw" values, they now return aCategoricalVector. See these CategoricalArrays.jl release notes.
Merged pull requests:
v1.9.2
v1.9.1
v1.9.0
MLJBase v1.9.0
For the release notes:
- Allow tuples, in addition to vectors, when specifying
resampling=...inevaluate/evaluate!, and fix a mistake in the error message for invalidresamplingvalues (#1010)
Merged pull requests:
v1.8.2
v1.8.1
MLJBase v1.8.1
Merged pull requests:
- Fix deprecated
Varargexpression (#1000) (@devmotion) - For a 1.8.1 release (#1001) (@ablaom)