All suggestions made by others here are useful, but I would suggest that
computer scientists are probably a better -- or at least valuable
additional -- resource for this sort of knowledge than R programmers. A web
search on "self-documenting code" and/or "reproducible research" should
yield lots o
I wonder if the lintr package might be helpful.
--
Don MacQueen
Lawrence Livermore National Laboratory
7000 East Ave., L-627
Livermore, CA 94550
925-423-1062
Lab cell 925-724-7509
On 9/26/18, 7:00 AM, "R-help on behalf of Spencer Brackett"
wrote:
R users,
Is anyone aware o
On 26/09/2018 10:24 AM, Spencer Graves wrote:
It depends on what you want, but I've found it very useful to
create packages and submitting them to CRAN. See "Creating R Packages"
for how to do that.[1] Part of this involves creating vignettes using
Rmarkdown within RStudio. Creating
It depends on what you want, but I've found it very useful to
create packages and submitting them to CRAN. See "Creating R Packages"
for how to do that.[1] Part of this involves creating vignettes using
Rmarkdown within RStudio. Creating R packages and routinely running "R
CMD chec
I use R CMD BATCH foo which produces a file called foo.Rout and provided the
script includes
sessionInfo() constitutes a quite sufficient summary for my purposes, it isn’t
exactly pretty, but it
is informative.
> On Sep 26, 2018, at 3:00 PM, Spencer Brackett
> wrote:
>
> R users,
>
> Is any
R users,
Is anyone aware of the proper procedure for summarizing a script(your
complete list of functions, arguments , and error codes within your R
console for say a formal report or publication?
Many thanks,
Best wishes,
Spencer Brackett
-- Forwarded message -
From: CHATTON
6 matches
Mail list logo
