|
The term "classifier" is widely used for (at least) three very different entities:
The overloading of vocabulary between #1 and #2 tends not to problematic, but the use of the same term for both #2 and #3 causes endless grief when I'm working with software developers. I've tried out various terms for #3 over the years: "applier", "interpreter", "executer", etc., alone or prefixed by "classifier", but keep wishing there was something both standard and distinctive. So consider this a poll: what do you call #3 in conversation and/or when naming a software component? |
FYI, for 1. I meant the mathematical object output by the algorithm, i.e. a hyperplane for linear SVMs, or a tree structure for decision tree learners. But one would like a generic term for this across all learning algorithms. "Code" is true for 3, but one would ideally like a way to talk about this part of a piece of software vs. other parts.
(Aug 28 '11 at 09:34)
Dave Lewis
|
|
I'd call 1) a model, to an instance of the model and 3) as the prediction function of this model. Or maybe predictor? I think the problem is that "the prediction function" could very well be the mathematical expression of the function (i.e., 1)
(Aug 27 '11 at 12:12)
Alexandre Passos ♦
|
|
I tend to refer to #2 as a model, and #3 as a classifier. For #1, I think I also use classifier, or sometimes classification algorithm. |
