My apologies for not including sessionInfo(), and I'm a bit angry at myself
for that. Retrying in a fresh session of R, I get different results. More
specifically, I get the expected result where accuracy is the same in the
first and the last line. As I didn't include my sessionInfo() in my
previou
I don't see the issue here. It would be helpful if people would report
their sessionInfo() when reporting whether or not they see this issue.
Mine is
> sessionInfo()
R version 3.4.3 (2017-11-30)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Arch Linux
Matrix products: default
BLAS/LAPACK:
This is nothing specific to parallel::clusterApply() per se. It is the
default behavior of R where it allows for partial argument names. I
don't think there's much that can be done here except always using
fully named arguments to the "apply" function itself as you show.
You can "alert" yourself
Hi,
I wonder if the following is a design decision in the default bib style for
utils::cite().
Create a bibentry object:
> bibs <- bibtex::read.bib(package = "tools")
> bibs
Murdoch D (2009). "Parsing Rd files." http://developer.r-project.org/parseRd.pdf>.
When an entry is cited with with a
I ran this code in RStudio Server on a linux machine, but I don’t know the
version offhand. I will try to get it tomorrow. Thanks.
Thanks,
Greg Michaelson
www.datarobot.com
704-981-1118
> On Mar 14, 2018, at 4:47 PM, Joris Meys wrote:
>
> To my surprise, I can confirm on Windows 10 using
Hi!
I recognized that the argument matching of clusterApply (and therefore
parLapply) goes wrong when one of the arguments of the function is called "c".
In this case, the argument "c" is used as cluster and the functions give the
following error message "Error in checkCluster(cl) : not a valid
To my surprise, I can confirm on Windows 10 using R 3.4.3 . As tail is not
recognized by Windows cmd, I replaced with:
system('powershell -nologo "& "Get-Content -Path temp.csv -Tail 1')
The last line shows only 7 digits after the decimal, whereas the first have
15 digits after the decimal. I agr
What OS are you on? On Ubuntu 17.10 with R 3.4.3 all seems well (see
below for your example, I just added a setwd()).
[ That said, I long held a (apparently minority) view that csv is for all
intends and purposes a less-than-ideal format. If you have that much data,
you do generally not want to
Hello, I have looked on https://www.r-project.org/bugs.html , but it seems
that this is the only way to do it.
The issue is that the precision used by write.csv is on consistant for big
files. See the following code:
First I create a large dataframe filled with random uniform values. Then I
wri
On 13 March 2018 at 17:29, Christophe DUTANG wrote:
| So, I was wondering if this warning was removable at all? Does anyone
encounter this issue?
That is a pretty old topic.
Did you look into Writing R Extensions? The first mention is
* Do be very careful with passing arguments between R,
It does not answer direcly your question, but have you tried "bit64"
CRAN package :)
https://cran.r-project.org/web/packages/bit64/index.html
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
11 matches
Mail list logo
