Skip to content

Estimators and their catalog extensions should have matching names #2853

@artidoro

Description

@artidoro

In #2827, one of the items is to make sure the estimators and their catalog extensions have matching names. Like in trainers, we should keep the suffix estimator only in the estimator name, and remove it from the catalog extension, something like the following:

NameEstimator Name(...)

The question now is: How do we reconcile the names and which convention should we follow?

Most estimator names follow the convention: ActionPerformingEstimator, while in the catalog usually we use the convetion: PerformAction.

Some examples are:

Estimator Name Catalog Name
KeyToBinaryVectorMappingEstimator MapKeyToBinaryVector
MutualInformationFeatureSelectingEstimator SelectFeaturesBasedOnMutualInformation
CountFeatureSelectingEstimator SelectFeaturesBasedOnCount
... ...

cc/ @sfilipi @TomFinley @glebuk @eerhardt @rogancarr @ivanbasov

Metadata

Metadata

Assignees

No one assigned

    Labels

    APIIssues pertaining the friendly API

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions