Don't have invisible meta data from scoring, that cannot be replaced
It turns out that the Score activity in the Designer, adds some invisible meta data, called Score, that if you do any Arithmetic work on, will remove that metadata on the column, and make the Evaluator stop working. Just spent about 14 tech support calls tracking this down.
Here is what he said:
This is because the Evaluate Model module is expecting a ‘Scored Dataset’, which means the Score columns (predicted column, Scored Labels, Scored Probabilities) all have metadata assigned to them so that their ‘Feature type’ is Numeric/String Score instead of Numeric/String Feature. Passing the scored dataset into ‘Apply Math Operation’ removes the Score metadata and reverts it back to regular ‘Feature’ metadata (normal dataset). As it turns out, there is no way to assign/re-assign this ‘Score’ meta data to normal dataset, unless it were produced by ‘Score Model’ module.
And this is my reply:
Now, since the whole idea is to provide an UX for non-programmers, I would have to say that having undocumented metadata tagging columns, with no way to re-apply, is not in the spirit of user-friendly UX.
Thank you for your feedback.
What's the output mode of your Apply Math module? Do you use "Inplace"?
Could you please share why and what kind of Arithmetic work you need to do with the output of Score Model?
Could you please contact email@example.com for me to follow up with your case?