-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New API for ML.NET #754
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
Labels
API
Issues pertaining the friendly API
Comments
List of transforms:
|
List of trainers:
|
This was referenced Sep 16, 2018
Merged
This was referenced Sep 25, 2018
Merged
Merged
This was referenced Oct 2, 2018
singlis
added a commit
to singlis/machinelearning
that referenced
this issue
Oct 15, 2018
This adds the SelectColumns Transform and Estimator that is replacing the DropColumns and ChooseColumns Transforms. With this check-in, Drop and Choose are still in the code base but will be removed. In order to support loading older models, SelectColumns supports loading in Drop and Choose transforms. The changes include: - Implementation of the SelectColumnsTransform, SelectColumnsDataTransform and SelectColumnsEstimator - Backward compatibility with Drop and Choose columns by providing functions on SelectColumns that will be called when loading the model. - Entry point apis for calling select from the command line. - Additional tests. These changes are related to dotnet#754.
singlis
added a commit
that referenced
this issue
Oct 20, 2018
…1269) This adds the SelectColumns Transform and Estimator that is replacing the DropColumns and ChooseColumns Transforms. With this check-in, Drop and Choose are still in the code base but will be removed. In order to support loading older models, SelectColumns supports loading in Drop and Choose transforms. The changes include: * Implementation of the SelectColumnsTransform, SelectColumnsDataTransform and SelectColumnsEstimator * Backward compatibility with Drop and Choose columns by providing functions on SelectColumns that will be called when loading the model. * Entry point apis for calling select from the command line. * Additional testing of the new functionality. These changes are related to #754.
singlis
added a commit
to singlis/machinelearning
that referenced
this issue
Oct 25, 2018
replacing them with SelectColumnsTransform. These changes include: * Updates to SelectColumnsTransform to respect ordering when keeping columns. For example, if the input is ABC and CB is selected, the output will be CB. * Updates to code that used Choose or Drop columns, replacing with SelectColumns. * Updates to baseline output for tests to pass * Re-enabled the SavePipeline tests This fixes dotnet#1342 These changes are also related to dotnet#754
singlis
added a commit
that referenced
this issue
Oct 30, 2018
…olumnsTransform (#1371) * Removes ChooseColumnsTransform and DropColumnsTransform classes replacing them with SelectColumnsTransform. These changes include: * Updates to SelectColumnsTransform to respect ordering when keeping columns. For example, if the input is ABC and CB is selected, the output will be CB. * Updates to code that used Choose or Drop columns, replacing with SelectColumns. * Updates to baseline output for tests to pass * Re-enabled the SavePipeline tests This fixes #1342 These changes are also related to #754
singlis
added a commit
to singlis/machinelearning
that referenced
this issue
Nov 21, 2018
This will be replacing the TermLookupTransform and provide a way to specify the mapping betweeen two values (note this is specified and not trained). A user can specify the mapping by providing a keys list and values list that must be equal in size. The Estimator will then generate a 1-1 mapping based on the two lists. The PR references dotnet#754 which covers the conversion of Transformer to use the new Estimator API.
sfilipi
pushed a commit
that referenced
this issue
Dec 21, 2018
* Addition of the ValueMappingEstimator and ValueMappingTransform. This will be replacing the TermLookupTransform and provide a way to specify the mapping betweeen two values (note this is specified and not trained). A user can specify the mapping by providing a keys list and values list that must be equal in size. The Estimator will then generate a 1-1 mapping based on the two lists. The PR references #754 which covers the conversion of Transformer to use the new Estimator API.
@Ivanidzo4ka can you please verify if this can be closed now? |
singlis
added a commit
to singlis/machinelearning
that referenced
this issue
Jan 24, 2019
This provides an example that demonstrates different ways to use the ValueMappingEstimator. This is part of the original change to add the ValueMappingEstimator to the code base and references dotnet#754.
singlis
added a commit
that referenced
this issue
Feb 1, 2019
ValueMappingEstimator example (References #754) Provides examples that demonstrate different ways to use the ValueMappingEstimator. * Added sample links to ValueMap catalog extensions * Added additional documentation to the ValueMappingEstimator, including remarks section.
I believe this can be closed. We have made this new API and have separate issues tracking remaining necessary API work. Please re-open if I'm wrong. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are creating a stable API that:
To that end, we are going to expose a selection of Estimators and Transformers (see #581 ) that cover existing transforms, learners and loaders.
This issue will be used to track the overall project status: what is planned to be done, what is done, etc.
The text was updated successfully, but these errors were encountered: