Skip to content

Forgetting the threshold in logPrediction causes bad request #114

Description

@tbillington

When calling logPrediction using the nodejs library, I passed the option parameter in with computeFeatureContributions: true, however I forgot to add threshold too.

When I ran the code I got back a generic Error: bad request. It took me a little bit of fiddling with double checking urls, the app was running, etc before I checked the examples and tried adding threshold to see if it would help.

I initially assumed I wouldn't need the threshold because tuning was not supported for my model type in the first place.

Once I added threshold my code was working again.

Is there a better error that can be provided to clients if they are accidentally misusing the API?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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