Extract "dependent.variable.name" from a ranger object about ranger HOT 6 CLOSED

You are right, it is currently not saved. I think we can add it as you suggest, we just need to add something for the x/y interface (where there might be no name).

from ranger.

IMHO for x/y interface, dependent.variable.name should be NULL as we are not getting it either from a named argument or a named datastructure (such as a dataframe).

from ranger.

For the xy/ interface we could default to using deparse(substitute(y)), no? Taking the name of the object might be more informative than a NULL

from ranger.

But then it would be an object name and not a variable name, right? I think people want to use dependent.variable.name to subset data later, which wouldn't make sense with x/y.

from ranger.

Ah, sure - I was primarily worried about having default behavior that doesn't yield NULL, and assumed that x/y interface would be used in a context where target and features are in distinct objects anyway, hence falling back to object names is the next best thing to having variable names. Obviously, if y = somedata$sometarget then that point is moot, kind of.

from ranger.

Thanks, merged #698.

from ranger.