You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug report
The documentation of QuantityCuts at the bottom of the page says cuts are input as dictionary entry “column_name”: (lower value, upper value). However, when you implement the stage in a pipeline this gets interpreted as a tuple and doesn’t work, so the docs should say “column_name”: [lower value, upper value] .
Before submitting
Please check the following:
I have described the situation in which the bug arose, including what code was executed, information about my environment, and any applicable data others will need to reproduce the problem.
I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a descriprion of what I expected instead.
If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.
The text was updated successfully, but these errors were encountered:
Bug report
The documentation of QuantityCuts at the bottom of the page says cuts are input as dictionary entry “column_name”: (lower value, upper value). However, when you implement the stage in a pipeline this gets interpreted as a tuple and doesn’t work, so the docs should say “column_name”: [lower value, upper value] .
Before submitting
Please check the following:
The text was updated successfully, but these errors were encountered: