[R-pkg-devel] debian - how to replicate the error

2022-09-19 Thread Zhang, Xueqiong
Hi, I am seeking help on error messages from Debian-gcc check – 1. My package passed checks on windows and macos, but failed on debian-gcc with testthat.R error. I don’t have a linux box, and was not able to check it via r-hub-linux-platforms since some of bioc dependencies are not

Re: [R-pkg-devel] Non-ASCII and CRAN Checks

2022-09-19 Thread Neal Fultz
This happened to me this summer when working on the recent US census; came up with two possible solutions: 1. Re-encode the column to UTF-8. Example: Encoding(puertoricocounty20$NAME) <- "latin1" puertoricocounty20$NAME <- iconv(puertoricocounty20$NAME, "latin1", "UTF-8") 2. Use gsub to replace

[R-pkg-devel] Non-ASCII and CRAN Checks

2022-09-19 Thread Igor L
Hello everybody, I'm testing my package with the devtools::check() function and I got a warning about found non-ASCII strings. These characters are in a dataframe and, as they are names of institutions used to filter databases, it makes no sense to translate them. Is there any way to make the

Re: [R-pkg-devel] Read and restore .Random.seed in package

2022-09-19 Thread Jan van der Laan
Thanks! I noticed that there was an almost identical question asked on this list only a few days ago that I completely missed. Sorry for that. Your example and the examples there at least give me a better way to write my function. Jan On 19-09-2022 11:58, Achim Zeileis wrote: On Mon, 19

Re: [R-pkg-devel] Unable to create manual

2022-09-19 Thread Uwe Ligges
On 16.09.2022 20:17, Edward Wei wrote: That is an interesting thought. I don't think I have downloaded LaTex explicitly, however, I do have MikTex and I added that file to PATH manually. This is what my current PATH calls:

[R-pkg-devel] Read and restore .Random.seed in package

2022-09-19 Thread Jan van der Laan
I have a function in which I need to draw some random numbers. However, for some use cases, it is necessary that the same random numbers are drawn (when the input is the same) [1]. So I would like to do a set.seed in my function. This could, however, mess up the seed set by the user. So