Skip to content

ValueMappingEstimator in the Conversions catalog is missing the treatAsKeys parameter #2346

Closed

Description

@singlis

When adding samples, I noticed that the treatValuesAsKeys parameter is not available as part of the Conversions catalog. Therefore I am not able to do this:

         var pipeline = ml.Transforms.Conversions.ValueMap(educationKeys, educationValues, true, ("EducationKeyType", "Education"));

And instead have to do this:

            var pipeline = new ValueMappingEstimator<string, string>(ml, educationKeys, educationValues, true, ("EducationKeyType", "Education"));

Therefore we should add another function to the Conversions Catalog to handle this.

Activity

  1. self-assigned this
    on Jan 31, 2019
  2. Ivanidzo4ka commented on Feb 21, 2019

    @Ivanidzo4ka
    Contributor

    Is it still relevant? If yes, would you have time to fix it?

  3. singlis commented on Apr 1, 2019

    @singlis
    MemberAuthor

    Note this was added by @artidoro, #2959

  4. ghost locked as resolved and limited conversation to collaborators on Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions