On Thu, Apr 4, 2013 at 2:06 PM, Henrik Bengtsson wrote:
> For 'R CMD check', it appears that option '--outdir' is not recognized
> and generates warning "unknown option '--outdir'". R CMD check --help
> says:
>
> Usage: R CMD check [options] pkgs
> [...]
> Options:
> [...]
> -o, --outdir=DIR
All right. I'm still stuck even with all of the help.
Here is the first part:
>R CMD INSTALL --no-multiarch cudasize_1.0.tar.gz
R CMD INSTALL --no-multiarch cudasize_1.0.tar.gz
* installing to library 'c:/myRlib'
* installing *source* package 'cudasize' ...
** libs
nvcc -m32 --shared -o cuda4.
Wow!
This is just amazing!
Thanks so much. I didn't realize how intense this is.
From: Duncan Temple Lang [dtemplel...@ucdavis.edu]
Sent: Thursday, July 18, 2013 3:08 PM
To: Hodgess, Erin
Cc: r-devel@r-project.org
Subject: Re: [Rd] question about Makeco
Hi Erin
See the code below.
Basically, I have created a new routine that you will
call from R as
.C("cuda4", 1L, "5")
where 1L is the number of arguments you are passing and "5" is the character
vector of arguments.
We are using .C() here for simplicity. For other cases involving data, .Call
Hi again.
I put in the extern statement.
However, I'm not sure what you mean by changing the signature, please.
I changed out the routine name from "stuff" to "cuda4" in the cuda4.cu program.
Still getting:
> library(cudasize)
library(cudasize)
>
> .C("cuda4",as.character(5))
.C("cuda4",a
Hi Erin
It appears that there is only one file in src that is compile, i.e. cuda4.cu.
That does not contain a routine named cuda4, which is what you are trying to
invoke
via the .Call("cuda4") expression.
Instead, it contains two routines - one kernel square_array which runs
on the GPU, and th
Hi again:
Here is another problem that I am having. Hope this will be the last one. I
really want to see if I can put it together. Sorry for belaboring the issue.
Well, here is my story:
c:\Program Files\R\R-3.0.1\bin\i386>R CMD build cudasize
R CMD build cudasize
* checking for file 'cudasi
[cross-posted on R-devel and Bioc-devel, since the functions from the
parallel package discussed here are mirrored in the BiocGenerics package]
Hi,
I am currently running a lengthy simulation study (no details necessary)
on a large multi-core system. The simulated data sets are stored in a
lon
Hi Erin
Glad you are making progress on this with Brian's help.
I thought I would mention a different approach that might save you some
programming time and actually make the code more flexible at the same time.
Basically, in a high-level language like R, it is nice to keep the code
calling a
You will need a src/Makevars.win to get a .cu file to compile. It is
not a known extension: see ยง1.1.4 of 'Writing R Extensions'
Most likely you need something like
cudasize.dll:
nvcc -m32 --shared -o $@ cuda4.cu
in Makevars.win.
Also, heed the advice about trying R CMD INSTALL befor
Now let's try again. I set up the CYGWIN environment command as kindly
suggested by Prof. Ripley.
Here are my next steps:
R CMD build cudasize
* checking for file 'cudasize/DESCRIPTION' ... OK
* preparing 'cudasize':
* checking DESCRIPTION meta-information ... OK
* cleaning src
Warning:
C:/Use
On 2013-07-16 07:55, Hans W Borchers wrote:
I have been told by the CRAN administrators that the following code generated
an error on 64-bit Fedora Linux (gcc, clang) and on Solaris machines (sparc,
x86), but runs well on all other systems):
> fn<- function(x, y) ifelse(x^2 + y^2<= 1, 1 -
Thanks for the help.
What bothers me is that it works on most systems and does not work on
some more 'exotic' systems -- though it should work everywhere however
small the user chooses the tolerance (with some warnings, maybe).
I decided I will apply my own integration routines in this example as
On 18/07/2013 07:45, Hodgess, Erin wrote:
Dear R development:
I'm not sure if this is the appropriate list, but it's a start.
I would like to put together a package which contains a CUDA program on Windows
7. I believe that it has to do with the Makeconf file in the etc directory.
That
14 matches
Mail list logo
