Re: [R-pkg-devel] What to do when a package is archived from CRAN
Hi, You can generally see what the reason is from the archive page, where it says: A summary of the most recent check results can be obtained from the check results archive. On that page, https://cran-archive.r-project.org/web/checks/2023/2023-08-19_check_results_prqlr.html is the note: Version: 0.5.0 Check: installed package size Result: NOTE installed size is 18.5Mb sub-directories of 1Mb or more: libs 18.2Mb This is too big for CRAN, see https://cran.r-project.org/web/packages/policies.html quoted here: Packages should be of the minimum necessary size. Reasonable compression should be used for data (not just .rda files) and PDF documentation: CRAN will if necessary pass the latter through qpdf. As a general rule, neither data nor documentation should exceed 5MB (which covers several books). A CRAN package is not an appropriate way to distribute course notes, and authors will be asked to trim their documentation to a maximum of 5MB. Where a large amount of data is required (even after compression), consideration should be given to a separate data-only package which can be updated only rarely (since older versions of packages are archived in perpetuity). Similar considerations apply to other forms of “data”, e.g., .jar files. Source package tarballs should if possible not exceed 10MB. It is much preferred that third-party source software should be included within the package (as e.g. a vendor.tar.xz file) than be downloaded at installation: if this requires a larger tarball a modestly increased limit can be requested at submission. Sarah On Sat, Aug 26, 2023 at 4:26 PM SHIMA Tatsuya wrote: > > Hi, > > I noticed that my submitted package `prqlr` 0.5.0 was archived from CRAN > on 2023-08-19. > <https://CRAN.R-project.org/package=prqlr> > > I submitted prqlr 0.5.0 on 2023-08-13. I believe I have since only > received word from CRAN that it passed the automated release process. > <https://github.com/eitsupi/prqlr/pull/161> > So I was very surprised to find out after I returned from my trip that > this was archived. > > The CRAN page says "Archived on 2023-08-19 for policy violation. " but I > don't know what exactly was the problem. > I have no idea what more to fix as I believe I have solved all the > problems when I submitted 0.5.0. > > Is there any way to know what exactly was the problem? > (I thought I sent an e-mail to CRAN 5 days ago but have not yet received > an answer, so I decided to ask my question on this mailing list, > thinking that there is a possibility that there will be no answer to my > e-mail, although I may have to wait a few weeks for an answer. My > apologies if this idea is incorrect.) > > Best, > Tatsuya > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.sarahgoslee.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] (no subject)
Hi, The Writing R Packages manual is the main documentation, specifically: https://cran.r-project.org/doc/manuals/R-exts.html#The-DESCRIPTION-file As for indentation, don't. Just use a newline. I don't know of any templates, but the source code for many/most packages is on RForge and/or github, so you can look at as many DESCRIPTION files as you'd like to find the solutions you need. If that doesn't help, then please share actual examples of what isn't working in your file. Sarah On Mon, Apr 17, 2023 at 8:15 PM Socorro Dominguez wrote: > > Hello! > > I need some help. > > Could you explain how to write the *Description* field in the *Description* > file when we need to add links? I don't find any rules on how to write it > when it includes links such as > > Also, whenever I try to do a new line in the *Description* field with the > four spaces for indentation, I get an error from the R CMD > > If you could provide me with some sort of template example, I would be > extremely grateful. > > Best, > > Socorro > > -- > Best regards, > > Socorro E. Dominguez-Vidaña > s.doming...@ht-data.com > > [[alternative HTML version deleted]] > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.numberwright.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] how to add .Rd in man folder for inst/ext file?
Hi, Well, at the most basic, you create an appropriately-named and formatted text file in the man directory. The Writing R Extensions manual is full of information: https://cran.r-project.org/doc/manuals/R-exts.html Roxygen is an alternative approach to creating the Rd files yourself. https://cran.r-project.org/web/packages/roxygen2/vignettes/roxygen2.html The package.skeleton() function is a helper for the do it yourself approach. Sarah On Mon, Dec 19, 2022 at 9:17 AM Sanjeev Sariya wrote: > > Hi devel team, > > I have recently added one file in the inst/extdata folder. > > I'd like to add details about it in the man folder by creating a .Rd file > for the respective file. > > I created .Rd files for other datasets long time back, however, I do not > remember the steps now. Their skeleton looks like the attached file. > > I am using conda environment (not R studios) > Kindly guide me further. > best > > -- > Sanjeev M > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee (she/her) http://www.sarahgoslee.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Unable to post messages to this group
Clearly you can post messages to this group, since this message was received. R-package-devel requires that the first time someone posts, their message is approved by a human. After that first post, they may post normally. It's not a problem, or anything you've done - this policy applies to everyone, and cuts down enormously on spam since the moderators only approve relevant posts. Since your post appeared here, you've been cleared. The policy is on the about page where you signed up: https://stat.ethz.ch/mailman/listinfo/r-package-devel You have to be a subscriber to the list in order to post any message. Even then, your first messages are only posted after one manual moderator approvement. The moderation team are all volunteers, and sometimes they are busy or away from the computer, especially on weekends. Sarah On Mon, Jul 13, 2020 at 5:28 AM Binit Kumar wrote: > > Hi Team, > I am unable to post messages to this group and keep getting "waiting for > moderator" message from bounce email i.e. "R-package-devel > ". > Is there any criteria of sending the message to devel group? > > > Thanks & Regards, > > Binit Kumar > -- Sarah Goslee (she/her) http://www.numberwright.com __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] pdflatex is not available
It sounds like you're on a Mac? Then you need to install MacTeX, http://www.tug.org/mactex/ to get pdflatex. Sarah On Fri, Dec 13, 2019 at 7:11 PM Cathy Lee Gierke wrote: > Does anyone know why I might get this error? > > Hmm ... looks like a package > > Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : > > pdflatex is not available > > Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : > > * pdflatex is not available* > > *Error in running tools::texi2pdf()* > > You may want to clean up by 'rm -Rf > > /var/folders/0m/41bxx35j5x9f_tks7zrd7jh0gn/T//Rtmpuv00M5/Rd2pdf8f2a123193cb' > > * checking for detritus in the temp directory ... OK > > * DONE > > > > There are no clues in the Rdlatex.log > I have attached the ...manual.tex file. Is there a way to check it for > non-ascii or non-printing characters on a Mac? I have had that problem > before, but I'm not finding any now. Maybe I have the wrong command? > > > find /Users/user/CATkit/CATkit/man | perl -ne 'print if /[^[:ascii:]]/' > > find /Users/user/CATkit/CATkit/man/CatCall.rd | perl -ne 'print if > /[^[:ascii:]]/' > > > Should there be a pdf file somewhere? > > Thanks, > Cathy Lee Gierke > > > <http://www.goodreads.com/author/show/23924.Martin_Luther_King_Jr_> > ______ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > -- Sarah Goslee (she/her) http://www.sarahgoslee.com [[alternative HTML version deleted]] __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [Rd] base::format adds extraneous whitespace for some inputs
I can reproduce this. It has to do with whether the value rounds down to 9 or up to 10, and thus needs another space, I think. I agree that it shouldn't happen, but at least you can get rid of the space by using trim = TRUE. # rounds to 9 vs 10 format(9.95, digits = 2) format(9.96, digits = 2) format(9.95, digits = 2, nsmall = 2) format(9.96, digits = 2, nsmall = 2) format(9.95, digits = 2, nsmall = 2, trim=TRUE) format(9.96, digits = 2, nsmall = 2, trim=TRUE) # rounds to 99 vs 100 format(99.94, digits = 3) format(99.95, digits = 3) format(99.94, digits = 3, nsmall = 2) format(99.95, digits = 3, nsmall = 2) format(99.94, digits = 3, nsmall = 2, trim=TRUE) format(99.95, digits = 3, nsmall = 2, trim=TRUE) > sessionInfo() R version 3.5.3 (2019-03-11) Platform: x86_64-redhat-linux-gnu (64-bit) Running under: Fedora 28 (Workstation Edition) Matrix products: default BLAS/LAPACK: /usr/lib64/R/lib/libRblas.so locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=C [9] LC_ADDRESS=C LC_TELEPHONE=C [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] colorout_1.2-0 loaded via a namespace (and not attached): [1] compiler_3.5.3 tools_3.5.3 > # rounds to 9 vs 10 > > format(9.95, digits = 2) [1] "9.9" > format(9.96, digits = 2) [1] "10" > > format(9.95, digits = 2, nsmall = 2) [1] "9.95" > format(9.96, digits = 2, nsmall = 2) [1] " 9.96" > > format(9.95, digits = 2, nsmall = 2, trim=TRUE) [1] "9.95" > format(9.96, digits = 2, nsmall = 2, trim=TRUE) [1] "9.96" > > # rounds to 99 vs 100 > > format(99.94, digits = 3) [1] "99.9" > format(99.95, digits = 3) [1] "100" > > format(99.94, digits = 3, nsmall = 2) [1] "99.94" > format(99.95, digits = 3, nsmall = 2) [1] " 99.95" > > format(99.94, digits = 3, nsmall = 2, trim=TRUE) [1] "99.94" > format(99.95, digits = 3, nsmall = 2, trim=TRUE) [1] "99.95" On Thu, Jun 20, 2019 at 3:19 AM David J. Birke wrote: > > Dear R Core Team, > > First of all, thank you for your amazing work on developing and > maintaining this wonderful language. > > I just stumbled upon the following behavior in R version 3.6.0: > > format(9.91, digits = 2, nsmall = 2) > format(9.99, digits = 2, nsmall = 2) > > yield "9.91" and " 9.99" with an extraneous whitespace. > > My expected output for the second command is "9.99". > > I have not found anything explaining the whitespace in the help files. > Therefore, I am writing to report this behavior as a possible bug. > > Best wishes, > David > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel -- Sarah Goslee (she/her) http://www.numberwright.com __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [R-pkg-devel] How to write example results to a tempdir()?
Don't change the working directory! That has all kinds of unpleasant
side effects for the unsuspecting user, possibly even more so than
writing to a file.
Instead, write the file to the temp directory, and read it from there, with e.g.
wd <- tempdir()
write(dat, file.path(wd, 'Ttest_1981-2000.dat'))
Using file.path() means that the appropriate path delimiter for that
OS will be used.
Sarah
On Wed, Apr 25, 2018 at 12:30 PM, Jose A Guijarro <jguijar...@aemet.es> wrote:
> Dear all,
>
> I am struggling to update my package climatol from version 3.0 to 3.1.
> The old version had all examples under a "dontrun" section because they
> needed files created by other examples that the user had to run first.
>
> As this is not acceptable anymore, I made the examples runnable and
> prepared small ad-hoc datasets, but then writing files to the user space
> is against the CRAN policy rules, and I was suggested to run them on a
> temporal directory. Therefore I changed all my examples to read/write
> files to a tempdir(), as in:
>
> \examples{
> #Set a temporal working directory and write input files:
> wd <- tempdir()
> setwd(wd)
> data(Ttest) #(This loads matrix 'dat' and data.frame 'est.c')
> write(dat,'Ttest_1981-2000.dat')
> write.table(est.c,'Ttest_1981-2000.est',row.names=FALSE,col.names=FALSE)
> rm(dat,est.c) #remove loaded data from memory space
> #Now run the example:
> dd2m('Ttest',1981,2000)
> #Input and output files can be found in directory:
> print(wd)
> }
>
> But now CRAN checks return this warning ten times (one for every example
> in the package):
>
> Warning: working directory was changed to ‘/tmp/RtmpWSRK2F’, resetting
>
> Any hint on how to solve the problem will be highly appreciated...
>
> Jose
>
--
Sarah Goslee
http://www.functionaldiversity.org
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] MAP-DP Clustering Algorithm package
A complete sentence ends in a period. On Tue, Jul 11, 2017 at 4:19 AM, Thorsten Wagner <thorsten.wag...@mpi-dortmund.mpg.de> wrote: > Hi, > > I’ve implemented the MAP-DP clustering algorithm in R following MatLab > scripts of this paper: > http://journals.plos.org/plosone/article/citation?id=10.1371/journal.pone.0162259 > > Here is the repository: > https://github.com/thorstenwagner/R-ClustMAPDP > > I would like to add the package to CRAN but something seems to be wrong with > my description file: > "Malformed Description field: should contain one or more complete sentences.” > > I would be happy if someone could tell me the reason. > > Best, > Thorsten > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel -- Sarah Goslee http://www.functionaldiversity.org __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [Rd] a question about optim.R and optim.c in R
Hi, On Mon, Jul 7, 2014 at 4:34 PM, Zhiyuan Dong zhiyuan.d...@gmail.com wrote: Hi, I am learning R by reading R source code. That's very brave of you. You might also try reading some of the documentation and contributed documentation, like: http://adv-r.had.co.nz/C-interface.html and http://cran.r-project.org/doc/manuals/r-devel/R-exts.html Sarah Here is one question I have about the optim function in R. The context : In the optim.R, after all the prep steps, the main function call call is made via : .External2(C_optim, par, fn1, gr1, method, con, lower, upper). So, it seems to me, to follow what is going on from here, that I should read the optim function in \src\library\stats\src\optim.c where it has this signature : SEXP optim(SEXP call, SEXP op, SEXP args, SEXP rho) I am not sure I follow here : In the .External2 call, we have 7 parameters : par, fn1, gr1, method, con, lower, upper; This does not seem to match the signature of SEXP optim(SEXP call, SEXP op, SEXP args, SEXP rho) However, it seems (from the source code) that the 7 parameters are somehow embedded in the 'args' parameter. I am not sure what is going on...Am I missing something? Thanks much!!! Best, Zhiyuan -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] ASCII art in function documentation?
Now that I'm at the computer with my R code, I've used both
\preformatted{}
and \cr to force line breaks.
Some combination of those may work for you.
Sarah
On Thu, Sep 5, 2013 at 11:10 AM, Rainer M Krug rai...@krugs.de wrote:
Sarah Goslee sarah.gos...@gmail.com writes:
Untested, but did you try wrapping the whole thing in a single code block:
Nope - also in one line.
Rainer
\code{
all
the
things
}
Sarah
On Thu, Sep 5, 2013 at 10:10 AM, Rainer M Krug rai...@krugs.de wrote:
Hi
I want to include ascii art in a function documentation which should
look as follow:
,
| +--+--+--+
| | 1/16 | 1/16 | 1/16 |
| +--+--+--+
| | 1/16 | 8/16 | 1/16 |
| +--+--+--+
| | 1/16 | 1/16 | 1/16 |
| +--+--+--+
`
to keep the monospaced font even in html, I decided to use \code{}:
,
| \code{+--+--+--+}
|
| \code{| 1/16 | 1/16 | 1/16 |}
|
| \code{+--+--+--+}
|
| \code{| 1/16 | 8/16 | 1/16 |}
|
| \code{+--+--+--+}
|
| \code{| 1/16 | 1/16 | 1/16 |}
|
| \code{+--+--+--+}
`
But the result was an empty line between each text:
,
| '+--+--+--+'
|
| '| 1/16 | 1/16 | 1/16 |'
|
| '+--+--+--+'
|
| '| 1/16 | 8/16 | 1/16 |'
|
| '+--+--+--+'
|
| '| 1/16 | 1/16 | 1/16 |'
|
| '+--+--+--+'
`
and when no empty lines were included obviously put everything behind
each other.
My question:
Is there a way that I can achieve the ASCII art as shown above? Is there
a way of having a \linebreak which does not insert a new line?
Thanks,
Rainer
--
#secure method=pgpmime mode=sign
--
Rainer M. Krug
email: RMKrugatgmaildotcom
--
Sarah Goslee
http://www.functionaldiversity.org
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] ASCII art in function documentation?
Untested, but did you try wrapping the whole thing in a single code block:
\code{
all
the
things
}
Sarah
On Thu, Sep 5, 2013 at 10:10 AM, Rainer M Krug rai...@krugs.de wrote:
Hi
I want to include ascii art in a function documentation which should
look as follow:
,
| +--+--+--+
| | 1/16 | 1/16 | 1/16 |
| +--+--+--+
| | 1/16 | 8/16 | 1/16 |
| +--+--+--+
| | 1/16 | 1/16 | 1/16 |
| +--+--+--+
`
to keep the monospaced font even in html, I decided to use \code{}:
,
| \code{+--+--+--+}
|
| \code{| 1/16 | 1/16 | 1/16 |}
|
| \code{+--+--+--+}
|
| \code{| 1/16 | 8/16 | 1/16 |}
|
| \code{+--+--+--+}
|
| \code{| 1/16 | 1/16 | 1/16 |}
|
| \code{+--+--+--+}
`
But the result was an empty line between each text:
,
| '+--+--+--+'
|
| '| 1/16 | 1/16 | 1/16 |'
|
| '+--+--+--+'
|
| '| 1/16 | 8/16 | 1/16 |'
|
| '+--+--+--+'
|
| '| 1/16 | 1/16 | 1/16 |'
|
| '+--+--+--+'
`
and when no empty lines were included obviously put everything behind
each other.
My question:
Is there a way that I can achieve the ASCII art as shown above? Is there
a way of having a \linebreak which does not insert a new line?
Thanks,
Rainer
--
--
Sarah Goslee
http://www.functionaldiversity.org
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] large dataset - confused
Hi, On Mon, Jul 23, 2012 at 1:32 PM, walcotteric walco...@msu.edu wrote: I'm trying to load a dataset into R, but I'm completely lost. This is probably due mostly to the fact that I'm a complete R newb, but it's got me stuck in a research project. I've tried just opening the text file in WordPad and copying the data directly into R, but it's too big and causes the program to crash. Any suggestions or assistance? I'm kinda desperate and lost. Sure. First of all, you need to post to the R-help list, not the R-devel list. Then you need to read the Intro to R that came with R when you installed it. Then you need to read the posting guide for R-help, and provide the requested information, including: how big is your dataset? what format is it in? (text file isn't very informative) what R commands have you used? (read.table() perhaps) and so on. Also, what do you mean by crash? R stops working? You get an error message? Sarah -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] How to create arbitrary number of loops
That sounds like a job for recursion.
And also, a question for r-help and not r-devel.
Sarah
On Wed, Mar 28, 2012 at 5:34 PM, Dai, Hongying, h...@cmh.edu wrote:
Dear R users,
I'm wondering how I can generate an arbitrary number of loops in R.
For instance, I can generate two for loops to get ICC among any two-way
combination among 10 variables. Here is the code
n-10
for (i in 1:(n-1))
{
for (j in (i+1):n)
{
icc(cbind(DATA[,i],DATA[,j]))
}
}
If I need three-way combination, then a code with three for loops will be:
n-10
for (i in 1:(n-2))
{
for (j in (i+1):(n-1))
{
for (k in (j+1):n)
{
icc(cbind(DATA[,i],DATA[,j],DATA[,k]))
}
}
}
But how can I write a code if I need all m=2, 3, 4,... loops for arbitrary
m-way combinations?
Thanks!
Daisy
--
Sarah Goslee
http://www.functionaldiversity.org
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] requesting a new SIG mailing list
Dear Martin, Thank you for confirming what I'd already suspected about the mailing list software. I've added hydrology explicitly to the list description, and hope that the hydrologists find it a welcoming home. We've got a solid core of participants, so R users should find it a useful resource. Sarah On Thu, Feb 16, 2012 at 6:39 AM, Martin Maechler maech...@stat.math.ethz.ch wrote: Hi, I'm the site maintainer of the r-sig-...@r-project.org mailing lists (and back from vacations). Sarah Goslee sarah.gos...@gmail.com on Wed, 15 Feb 2012 12:16:01 -0500 writes: Hi all, It would be great if Sara of someone of the maintainers of the r-sig-ecology list could add that info to the info page. I'm talking with the other maintainer about revising both the short and the long descriptions. I think that r-sig-env would be much more intuitive for environmental scientists coming from fields different from ecology, but I don't think it is possible to change the name of an existing mailing list. yes, that would be only doable with much effort, and (unless even more effort is put in) it would invalidate all current links to the current archives etc. However, I'm wondering if it would be possible to create an alias termed 'r-sig-env' to 'r-sig-ecology' ?, in order to make the name of the list more intuitive for environmental scientists but without disturbing the current users. I don't know that there is any mechanism for doing either of those things. Changing the name would be disruptive, and I don't know of an alias option. there is none, on the mailing list level. On the mail server side, I could create such aliases, but then these would only apply to e-mail addresses and the ML software would still speak of the official ML name... Given all the issues and opinions heard so far, I'd also propose trying to have hydrologists and other env.scientists join the r-sig-ecology for the time being. Brian Ripley has already mentioned the very important point, that there's some often non-negligible admin overhead for each list, and I can add that indeed, we have had several lists that always remained too small and so never started flying. -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] requesting a new SIG mailing list
Hi all, It would be great if Sara of someone of the maintainers of the r-sig-ecology list could add that info to the info page. I'm talking with the other maintainer about revising both the short and the long descriptions. I think that r-sig-env would be much more intuitive for environmental scientists coming from fields different from ecology, but I don't think it is possible to change the name of an existing mailing list. However, I'm wondering if it would be possible to create an alias termed 'r-sig-env' to 'r-sig-ecology' ?, in order to make the name of the list more intuitive for environmental scientists but without disturbing the current users. I don't know that there is any mechanism for doing either of those things. Changing the name would be disruptive, and I don't know of an alias option. I think ecology is a more inclusive term than environmental anyway, but then I'm an ecologist. Sarah -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] requesting a new SIG mailing list
Hello, I'm one of the maintainers of the r-sig-ecology list, and I think it would be entirely appropriate to include hydrology within the scope of the list. There hasn't been much hydrologic discussion, as you noted, but not because we wish to exclude it. Sarah On Tue, Feb 14, 2012 at 11:31 AM, Mauricio Zambrano-Bigiarini mauricio.zambr...@jrc.ec.europa.eu wrote: Another possibility could be to use the R-sig-ecology, which seems to be more related to hydrology: analytical techniques and topics that are appropriate for discussion on R-sig-ecology are quite broad. For examples of what might be appropriate for discussion on this list, please see the Environmentrics Task View (http://cran.r-project.org/web/views/Environmetrics.html) (taken from: https://stat.ethz.ch/mailman/listinfo/r-sig-ecology) However, I did a quick search on the archives of 'R-sig-ecology' for the year 2011, and I could only found one single mail related to hydrology: https://stat.ethz.ch/pipermail/r-sig-ecology/2011-July/002274.html (in the same search I couldn't find any single reference to hydrology in the R-sig-geo during the year 2011) -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] seq.Date bug?
I was prompted to try it myself: On Tue, Jan 31, 2012 at 2:56 PM, Dirk Eddelbuettel e...@debian.org wrote: R seq(as.Date(Sys.Date()), by=-1 months, length=6) [1] 2012-01-31 2011-12-31 2011-12-01 2011-10-31 2011-10-01 2011-08-31 R Notice how October appears twice. As does December. Now, date arithmetic is gruesome but the documentation for seq.Date et al does not hint it wouldn't honour the by= argument. So a bug, or merely a somewhat less than desirable features. The by argument chokes on month if the current day is greater than the shortest month in the sequence (presumably due to the irregular nature of month lengths): For leap year 2012: seq(as.Date(2012/1/29), by=month, length.out=12) # works [1] 2012-01-29 2012-02-29 2012-03-29 2012-04-29 2012-05-29 [6] 2012-06-29 2012-07-29 2012-08-29 2012-09-29 2012-10-29 [11] 2012-11-29 2012-12-29 seq(as.Date(2012/1/30), by=month, length.out=12) # fails [1] 2012-01-30 2012-03-01 2012-03-30 2012-04-30 2012-05-30 [6] 2012-06-30 2012-07-30 2012-08-30 2012-09-30 2012-10-30 [11] 2012-11-30 2012-12-30 While for non-leap year 2011: seq(as.Date(2011/1/28), by=month, length.out=12) # works [1] 2011-01-28 2011-02-28 2011-03-28 2011-04-28 2011-05-28 [6] 2011-06-28 2011-07-28 2011-08-28 2011-09-28 2011-10-28 [11] 2011-11-28 2011-12-28 seq(as.Date(2011/1/29), by=month, length.out=12) #fails [1] 2011-01-29 2011-03-01 2011-03-29 2011-04-29 2011-05-29 [6] 2011-06-29 2011-07-29 2011-08-29 2011-09-29 2011-10-29 [11] 2011-11-29 2011-12-29 sessionInfo() R version 2.14.1 (2011-12-22) Platform: x86_64-redhat-linux-gnu (64-bit) locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=C LC_NAME=C [9] LC_ADDRESS=C LC_TELEPHONE=C [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C attached base packages: [1] stats graphics grDevices utils datasets methods base loaded via a namespace (and not attached): [1] tools_2.14.1 -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] seq.Date bug?
As Duncan pointed out, this is documented in ?seq.POSIXt: Using ‘month’ first advances the month without changing the day: if this results in an invalid day of the month, it is counted forward into the next month: see the examples. But ?seq.Date gives the impression that the construct Dirk and I tried should work: ## find all 7th of the month between two dates, the last being a 7th. st - as.Date(1998-12-17) en - as.Date(2000-1-7) ll - seq(en, st, by=-1 month) rev(ll[ll st ll en]) is given as an example, and it is not pointed out that this won't work for the 30th of the month. Normally one can extrapolate from patterns given in the examples, and here that isn't true. So perhaps the help should be modified slightly instead? Sarah -- Sarah Goslee http://www.sarahgoslee.com __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Undocumented functions
Why not use package.skeleton() to construct empty help files? But if you're determined to change the function names instead, grep and sed are very useful tools for that sort of thing. (The OS versions, not the R grep()). Sarah On Thu, Dec 15, 2011 at 7:01 AM, Nicola Sturaro Sommacal mailingl...@nicolasturaro.com wrote: Hi! I am building a package. This package will not submitted to CRAN. I write the help files for the most important functions of my package, I cannot write it for all functions. This may sounds strange, but so there! I know that all user-level functions should be documented, so I have to move my undocumented functions to a non-user-level. It's right? To move my functions to a non-user-level I can write them as hidden functions, with a dot before the names. This require a very long check of my code to change the call to the function preceding it by a dot. So, this is not a real choice. There are other way to reach my purpose? Thank you very much for help. Sincerely, Nicola -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] broken save(..., compress=xy)
Hi, 2011/9/23 Hervé Pagès hpa...@fhcrc.org: Hi, With current R devel and R 2.13.1: aa=1:5 save(aa, file=aa.rda, compress=xy) Error in identical(compress, gzip) || compress : invalid 'y' type in 'x || y' The options for compress are gzip bzip2 or xz (and not xy), at least on my linux system. Are you sure you want xy? Sarah Thanks! H. sessionInfo() R version 2.13.1 (2011-07-08) Platform: x86_64-unknown-linux-gnu (64-bit) locale: [1] LC_CTYPE=en_CA.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_CA.UTF-8 LC_COLLATE=en_CA.UTF-8 [5] LC_MONETARY=C LC_MESSAGES=en_CA.UTF-8 [7] LC_PAPER=en_CA.UTF-8 LC_NAME=C [9] LC_ADDRESS=C LC_TELEPHONE=C [11] LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION=C attached base packages: [1] stats graphics grDevices utils datasets methods base -- -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] nchar( NA )
Hi Romain, Did you read the help for nchar? Value: For ‘nchar’, an integer vector giving the sizes of each element, currently always ‘2’ for missing values (for ‘NA’). It may be unexpected behavior, but it's *well-documented* unexpected behavior. Sarah On Fri, Jun 18, 2010 at 4:52 PM, Romain Francois rom...@r-enthusiasts.com wrote: Hello, Is this expected ? nchar( c( , NA ) ) [1] 0 2 Should not the second one be NA ? Romain -- Sarah Goslee http://www.functionaldiversity.org __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
