tribuo changes types between input dataset and prediction about tech.ml.dataset

[behrica]

This is problematic as usual accuracy is calculated by comparing:
[0 1] and ["0" "0"], which is eventually problematic in automatic evaluations as nobody might see the different types,
and this gets evaluated as "non matching" even though they do match.
In metamorph.ml and its predict method I will try to fail on all this situations

[behrica]

Any news on this issue ?
The fact that the tribuo trainer changes he "dataype" in its prediction from float to string makes it a bad player among the different models.
A model which is trained on [0 1 0 1 ..] (as int), should never predict "0" or "1".
I think a well behaving (classification) model should never predict anything which it never saw in training data.
0 and "0" is not the same in this context.

[cnuernber]

I agree