search for: amredd

...e. Apparently windows 7 is selling like hot buns, so there should be enough market pressure before too long , to encourage the providers of Notepad++ NpptoR to fix it ... Thanks again Bob Robert Kinley bobk@lilly.com Andrew Redd <aredd@stat.tamu.edu> Sent by: amredd@gmail.com 04/03/2010 14:17 To Robert Kinley <KINLEY_ROBERT@lilly.com> cc Subject Re: [R] running R from Notepad++ in Windows 7 I had a conversation with someone the other day about problems on Windows 7. It was caused by the compatibility mode that they were running R in. That mig...

I am developing a package that is only applicable on windows, is there a line I can put in the depends field of the DESCRIPTION file to tell that this should only be build for windows? Are there any other protocols that I should follow? Thanks, -- Andrew May the Open Source be with you. [[alternative HTML version deleted]]

The CRAN policy page (https://cran.r-project.org/web/packages/policies.html) implies that there is a formal procedure for orphaning a package but none is mentioned in the Extensions manual (https://cran.r-project.org/doc/manuals/r-devel/R-exts.html). This page (https://cran.r-project.org/src/contrib/Orphaned/README) implies that one would simply resubmit the package to CRAN with the text

I'm developing packages with CUDA, and I'm running into a problem with memory allocation. Since CUDA involves memory on the GPU device it requires that the program handle memory allocation and deallocation separately from R. The simplest case of allocating a char and then deallocating causes a segmentation fault when R closes. Not on garbage collection but only on exit. Is there

I have a package that I'm developing that I need to unload the library. Long story short I figured out that the leaving the compiled code loaded lead to a segmentation fault, but unloading the code will fix it. I've read the documentation and it appears that there are several ways to do this? What is the popper accepted current standard for unloading compiled code? The options as I

I'm not sure if this is the official behavior but I would expect the na.action function applied to a lm object to return the na.action. Here is what I mean. > x<-0:10 > y<-x+rnorm(10) Warning message: In x + rnorm(10) : longer object length is not a multiple of shorter object length > y[5]<-NA > m<-lm(y~x) > m$na.action 5 5 attr(,"class") [1]

I'm developing some software and running into compiling warning: conditionals.c:104: warning: passing argument 4 of 'dger_' discards qualifiers from pointer target type conditionals.c:104: warning: passing argument 6 of 'dger_' discards qualifiers from pointer target type the netlib documentation states that the arguments x and y should be unchanged on exit. Should should

I go back and forth between windows and linux, and find myself running into problem with line endings. Is there a way to control the line ending conversion when writing files, such as write and cat? More explicitly I want to be able to write files with LF line endings rather than CRLF line ending on windows; and CRLF line endings instead of LF on linux, and I want to be able to control when the

I'm trying to compute sample size requirements for a binomial exact test. we want to show that the proportion is at least 90% assuming that it is 95%, with 80% power so any asymptotic approximations are out of the questions. I was planning on using binom.test to perform the simple test against a prespecified value, but cannot find any functions for computing sample size. do any exist?