Closed wf-r closed 1 year ago
@wf-r Thanks for your findings. You are right, val3
should be treated as a valid value, it's a defect, and we will fix it as soon as possible.
The issue has been fixed. Please, reinstall the latest version from GitHub by the following command:
pip install --upgrade git+https://github.com/autodeployai/pypmml.git
Please, let me know if you still have a problem.
@wf-r Can we close the issue? Please let me know if you have any issues.
Thanks for the quick fix, issue is fixed!
Hi,
according to Link, if a categorical field contains at least one value with a valid property, these values completely define the set of valid values. Otherwise any value should be valid by default.
Is the second part respected in PyPmml?
If I test the following model in PyPmml 0.9.16 on Python 3.8.6, it seems that "val1" and "val2" are considered valid, however "val3" is not.
Note that adding
invalidValueTreatment="asIs"
to the MiningField fixes this.Best Wolfgang