Closed alexpghayes closed 3 years ago
Existing column names (this is fairly complete, but not perfect -- it was scraped from the \value{}
section of .Rd
files)
k
clusters, these will be as.factor(1:k)
,
or as.factor(0:k)
if there's a noise term.
used_by: Mclustconf.int = TRUE
.
used_by:
conf.int = TRUE
.
used_by:
ratetable
term is present) If
the data.frame = TRUE
argument is supplied to pyears
, this is simply the contents
of x$data
.
used_by: pyearsts
or zoo
object.
used_by:
~~
for covariances, or ~
for regression parameters)
used_by: lavaanY1
, Y2
, etc).
used_by:
x
was called
with dfbeta = TRUE
)
used_by: aaregboot
needs custom info.
used_by:
NA
for noise component
used_by: MclustSome current conflicts I am aware of for tidy()
(some of these not in the list above):
acf
/ autocorrelation
comp
/ component
conf.high
/ upper
conf.low
/ lower
exp
/ expected
df
/ num.df
n
/ N
/ size
parameter
/ term
/ variable
p
/ proportion
strata
/ stratum
response
/ y.level
/ y.value
statistic
/ z
It seems like there's also some redundancy in column names that describe "percent of variance" explained type information.
nzero
is used by cv.glmnet()
. The description above is "number of coefficients that are exactly zero for given lambda." I think this may be reversed. The documentation for cv.glmnet()
states that this is actually the "number of non-zero coefficients at each lambda." If you agree (and if appropriate), I am happy to file an issue in modeltests
instead, or to submit a PR.
A PR or an issue would be ideal!
This issue has been automatically closed due to inactivity.
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
This issue thread is for proposals for column names changes. Please read #452 before commenting.