Hello,
The output of kable() is a character vector, so you can solve your
problem with a regex.
res <- do.call("rbind", efas) %>%
kable()
res2 <- sub("^\\|[^|]+(\\|.*)", "\\1", res)
head(res2)
Alternatively, a more tidyverse like way would be to pipe the output of
kable() through sub().
I have been trying to write a function in Rstudio that extracts an
increasing number of latent factors for the EFA and reports fit measures
for each solution in a final table. Below, I pasted what I was able to come
up with.
Unfortunately, it has some critical limitations:
The for loop requires t
Hi Serena
I'll add one more "in addition" to this list of suggestions. It may not
be what you were thinking of, but may be far simpler in the long run.
The complexity of your approach comes from having separate data files
for each subject and trial, for which you have to have a convention for
Many thanks for the info.
I see the point but I'll think calling the spData would be a cheaper
price to pay. If each package one load provide access to their variables
things are likely to get messy.
I guess many R users would like to control the variables in their global
environment.
And sinc
Hello,
>This is *very* unlikely to be a bug. People should always exercise a
>great deal of caution about conjecturing bugs when they encounter a
>phenomenon that they don't understand.
Ok, I over reacted and I should let the package maintainers
qualify what is a bug or not. My point is that
This is intended/expected because the spdep package *depends* on the
spData package (see https://cran.r-project.org/web/packages/spdep/),
which means that the maintainer of spdep intends also spData to be
*attached* whenever spdep is attached.If they would have only
imported it, then spData wou
Helllo,
Thanks for the info. I still think these variables should not be loaded
when library(spdep) is called.
But I'll handle it following your suggestion.
Thanks,
Jeremie
> It turns out that that 'x' comes from the spData package and lives
> inside that package (part of its namespace)
Hello,
I'm using the package pROC in RStudio to create my ROC-curves and I have
patients in my data - healthy or sick - in the column "Status" and the value
"SUVmax" to examine it.
I used the following code:
plot.roc(daten$Status,daten$SUVmax,percent=TRUE,ci=TRUE,print.auc=TRUE,main="ROC-Kurve
On 23/07/18 22:30, Jeremie Juste wrote:
Hello,
I found a dangerous issue in the library spdep. I get variables x and y
that cannot be removed by rm() and I don't don't how they show up. Can
anyone reproduce this?
I cannot.
This is *very* unlikely to be a bug. People should always exercise
It turns out that that 'x' comes from the spData package and lives
inside that package (part of its namespace).
> spData::x
[1] 0 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450
This is conceptually no different from other objects in package
namespace, although we are more used to
Hello,
I found a dangerous issue in the library spdep. I get variables x and y
that cannot be removed by rm() and I don't don't how they show up. Can
anyone reproduce this?
~$ R --vanilla
> rm(list=ls())
> library(spdep)
> x
[1] 0 30 60 90 120 150 180 210 240 270 300 330 360 390 420 450
11 matches
Mail list logo
