Skip to content

Conversation

@GalOshri
Copy link
Contributor

@GalOshri GalOshri commented Oct 1, 2018

This adds release notes for ML.NET 0.6.

@codemzs
Copy link
Member

codemzs commented Oct 1, 2018

For type system you can add issue #673 that contains the spec and benchmarks.

@justinormont
Copy link
Contributor

justinormont commented Oct 1, 2018

Should we specifically call out the changes to which data-types are allowed/disallowed to have missing values? I think it's uncommon for users to have NA values in data types other than R4 as most pipelines are mostly R4 for Features & Key/R4/BL for Label.

#RESOLVED

* New APIs for ML.NET

* While the `LearningPipeline` APIs that were released with ML.NET 0.1 were easy to get started with, they had obvious limitations in functionality. Certain tasks that were possible with the internal version of ML.NET like inspecting model weights, creating a transform-only pipeline, and training from an initial predictor could not be done with `LearningPipeline`.
* The important concepts for understanding the new API are introduced [here](https://github.com/dotnet/machinelearning/blob/3cdd3c8b32705e91dcf46c429ee34196163af6da/docs/code/MlNetHighLevelConcepts.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3cdd3c8 [](start = 128, length = 40)

now that it's merged, you should use https://github.com/dotnet/machinelearning/blob/master/docs/code/MlNetHighLevelConcepts.md etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is still a link to master but it is a permalink (in case the content of the file changes or it gets moved).

* Replaced ML.NET's Dv type system with .NET's standard type system ([#863](https://github.com/dotnet/machinelearning/pull/863))

* ML.NET previously had its own type system which helped it more efficiently deal with things like missing values (a common case in ML). This type system required users to work with types like `DvText`, `DvBool`, `DvInt4`, etc.
* This update replaces the Dv type system with .NET's standard type system to make ML.NET easier to use and to take advantage of innovation in .NET.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

easier to use [](start = 94, length = 13)

probably mention the fact that now only floats and doubles have missing values, represented with NaN?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@GalOshri can you also add pointer to sample for ONNX scoring and if we have any data re: the perf speedup for prediction can we share? I feel uncomfortable explaining a big perf speedup with no backing evidence :(


* Up to ~200x speedup in prediction engine performance ([#973](https://github.com/dotnet/machinelearning/pull/973))

* This improvement leads to a significant speedup when making predictions for single records.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This improvement leads to a significant speedup [](start = 6, length = 47)

LOL. First rule of tautology club is the first rule of tautology club.

Copy link
Contributor

@Zruty0 Zruty0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

Copy link
Contributor

@justinormont justinormont left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@shauheen shauheen merged commit 70b3c3b into dotnet:master Oct 1, 2018
* The important concepts for understanding the new API are introduced [here](https://github.com/dotnet/machinelearning/blob/3cdd3c8b32705e91dcf46c429ee34196163af6da/docs/code/MlNetHighLevelConcepts.md).
* A cookbook that shows how to use these APIs for a variety of existing and new scenarios can be found [here](https://github.com/dotnet/machinelearning/blob/3cdd3c8b32705e91dcf46c429ee34196163af6da/docs/code/MlNetCookBook.md).
* These APIs are still evolving, so we would love to hear any feedback or questions.
* The `LearningPipeline` APIs have moved to the `Microsoft.ML.Legacy` namespace.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would mention that we plan on removing the LearningPipeline APIs in the next 0.7 release.

@GalOshri GalOshri deleted the release-notes-0.6 branch October 1, 2018 22:48
@ghost ghost locked as resolved and limited conversation to collaborators Mar 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants