Closed jzhang-gp closed 4 years ago
Thanks for surfacing this bug, Jing.
I expanded on the test you had and it only fails [1 ... 100] and nothing else. From manual inspection, [1 ... 100] does not seem to appear any more frequently than [0 ... N] in the training data.
Interestingly, I was able to control the resolver's intent prediction simply by changing the "min" metafeature
from 1 (Droppable
) to not 1 (Numerical
). Given this observation, I will include additional training data and retrain the model to tackle this specific issue.
Ping :)
Thanks for surfacing this bug, Jing.
I expanded on the test you had and it only fails [1 ... 100] and nothing else. From manual inspection, [1 ... 100] does not seem to appear any more frequently than [0 ... N] in the training data.
Interestingly, I was able to control the resolver's intent prediction simply by changing the
"min" metafeature
from 1 (Droppable
) to not 1 (Numerical
). Given this observation, I will include additional training data and retrain the model to tackle this specific issue.
Is this issue solved?
Not yet, Ji Chao. I am free to work on it today, along with the dependency upgrade for pandas
and scikit-learn
[Update] Submitted a PR at the automl_research
repo to address this issue. We can update this PR once that automl_research
PR is approved. :)
Description
Adding the latest intent resolving code for additional intent type.
One weird finding on the following test. Both columns are columns with distinct values. First column is from 0 to 99 while the second is from 1 to 100. The first column is treated as
Numeric
but the second is treated asDroppable
. Is this because the ID data usually starts from 1? @christeefy