search for: call_r

...ase, the main() function needs to do some initialization stuff on R before one can invoke functions like mkString(), but I have not been able to find what this initialization should be. If someone could point me in the right direction I'd appreciate it. Also, where is the documentation for the call_R function? It is mentioned several times in the Writing R Extensions document, but I have not been able to find the documentation for it. TIA! Kynn [[alternative HTML version deleted]]

character arguments with call_R do not work except in the first position. (In other positions, they just yield a single blank character.) The error is at line 1858 of dotcode.c which should be changed from STRING(CAR(pcall))[i]=s; to STRING(CAR(pcall))[0]=s; Jim -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-....

...locfit package produced the following warning: ---------%<---------------- Installing package `locfit' ... libs /vol/bin/gcc -I/vol/math/R/include -I/usr/local/include -mieee -g -O2 -c S_e nter.c -o S_enter.o S_enter.c: In function `basis': S_enter.c:39: warning: passing arg 3 of `call_R' from incompatible pointer type ... /usr/bin/ld: Warning: Unresolved: call_R ----------%<---------------- By the way, the installation finishes with no errors, but locfit does not work. A similar thing happens with KernSmooth: ----------%<---------------- Warning: Unresolved: dqrdc_ dq...

I would like to use the call_R mechanism. Unfortunately I don't fully understand what the arguments are from the example in "R-0.64.2/demos/dynload". Could anybody explain me how I have to define the arguments, e.g., I want to call R with 5 doubles (or double[5]) and func does not return a value (is that possible...

...e working directories before genoud() was called, thus effectively preventing me from using multiple chips on the same machine. If you have any insights as to why or can suggest a work-around, it would be appreciated. The pasted-in files below are as follows: test_cluster.r, the main R script; call_R.csh, a shell script that calls the model; sin.r, an R script that is the "model". Together call_R.csh and sin.r make up the external model. Thanks for any help, Scott Waichler Pacific Northwest National Laboratory Richland, WA USA 509-372-4423 (voice) 509-372-6089 (fax) scott.waichler...

...n integer vector), where the external pointer object is a parameter named "ptr_attribute". The function extracts the pointer object from param; i.e. this function does what I want it to do. My question is: is there a way to do this using the .C() interface, rather than .Call()? Using call_R seems a possibility - has anyone had luck going this route? Any suggestions appreciated. Thanks, Patrick [[alternative HTML version deleted]]

...e to the database within OO [pretty easy] Some of the (many) things that I do not have a good grasp on are: - which R functions are available to the calling app. There is a list of functions listed in Chapter 5 of the "Writing R Extensions" doc. But there is also a function defined as: call_R(char*, long, void**, char**, long*, char**, long, char**); which appears to provide access to all R functions. Is this the case? - how do R and optional R packages (such as Bioconductor) interact via libR.so? - Do all optional packages have to be defined when building libR.so? (this doesn't...

Hey, I just read another post about calling R from C. Someone on stackoverflow (DWin makes me suspect its David W.?) referenced this: http://www.math.univ-montp2.fr/~pudlo/R_files/call_R.pdf Which made me think: Why is a loop in R bad, but in C not? And where exactly does looping cost the most? I wrote a piece of code for my bachelor's thesis where I loop from 1 to 500, and estimate a boosted model in every iteration. The procedure takes 2-6 minutes. In this example the loo...

I also have several packages in my RW0633 in Windoze and I would like to keep them in one place when I update the R system. Brian say to modify Rprofile to ..lib.loc <- c("c:/MyR/library",.Library) now Rprofile has a line like .lib.loc <- unique(c(unlist(strsplit(getenv("RLIBS"),":")),.Library) Sorry to be dense but where should I put the

...a register destination. I try to implement this by replacing a call to register by: - splitting the basic block around the call. - replacing the call (which is at the end of the first basic block) with : -- Loading the link register with the address of the new basic block -- and generating a 'CALL_R' which in the end results in a 'branch to register' (but, for llvm, it is treated as a call) So: __BB_2: ... call_to_reg Rx ... results in: __BB_2: ... load_immediate R15, __BB_3 branch_to_reg Rx __BB_3: ... where __BB_2 falls through to __BB__3 This works when...

Hi Is there a way to call R-Functions from C directly ? Is there an API Any comments are welcome. Thanks Reinhard -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To:

...is simple test have significant implications for my software development approach. I hope others find this information useful as well. I have attached the code files in the bottom. Below I provide a summary output, and interpret the results. [All times in table below are in microseconds] m/n/time_.Call_R/time_.Call_C++/.Call_overhead/time_.C_R/time_.C_C++/.C_overhead 100/10/3.23/1.33/*1.90*/16.89/0.96/*15.93* 200/15/5.38/3.44/*1.94*/30.77/2.81/*27.96* 500/20/12.48/10.4/*2.08*/78.12/9.37/*68.75* Interpretation: 1- .Call overhead holds nearly constant, i.e. independent of data size. This is expecte...

I have made available the work of the last weekend that I mentioned in my previous messages on ftp://sirio.stat.unipd.it/pub/R. Many thanks to Peter D. and Ross I. for their suggestions. If you think that the work is of some interest, I can upload it to CRAN. guido m. This is the README enclosed in the distribution. -------------------------------------------------------------------------

...anagement than Splus 3.x. There are several key memory bugs listed in the release notes. One being that Splus doesn't recover memory well (at all?) in for loops. 2. I've found R to be much faster than 5.1 in handling loops. 3. Also, R seems to be much faster when being called from C (using call_R) than Splus. 4. Splus 5.1 seems to handle large data sets better---if you don't do much with them. ########################################################################### thomas at biostat.washington.edu 1. There is not a lot known about the precise circumstances that affect the relati...

...installation I receive the following message : Installing package `locfit' ... libs gcc -I/usr/lib/R/include -I/usr/lib/R/include/R_ext -mieee-fp -fPIC -O2 -m486 -fno-strength-reduce -g -c S_enter.c -o S_enter.o S_enter.c: In function `basis': S_enter.c:39: warning: passing arg 3 of `call_R' from incompatible pointer type gcc -I/usr/lib/R/include -I/usr/lib/R/include/R_ext -mieee-fp -fPIC -O2 -m486 -fno-strength-reduce -g -c adap.c -o adap.o gcc -I/usr/lib/R/include -I/usr/lib/R/include/R_ext -mieee-fp -fPIC -O2 -m486 -fno-strength-reduce -g -c band.c -o band.o ... IT SEEMS...

Duncan - (but sent to R-devel, for any other thoughts?) How do you envision RSPerl being used? Without having seen the details, I can think of playing with strings; is there a preferred incantation for stringification of R objects (serialization)? (actually, the main problem I'm having is that I know how I want to code something like: Robject <-

...Most cases (especially NULL) are actually coding errors. NULL will be disallowed in future. .C() now passes a pairlist as a SEXP to the compiled code. This is as was documented, but pairlists were in reality handled differently as a legacy from the early days of R. o call_R and call_S are deprecated. They still exist in the headers and as entry points, but are no longer documented and should not be used for new code. BUG FIXES: o str(x, width) now obeys its width argument also for function headers and other objects x where deparse() is appli...

...Most cases (especially NULL) are actually coding errors. NULL will be disallowed in future. .C() now passes a pairlist as a SEXP to the compiled code. This is as was documented, but pairlists were in reality handled differently as a legacy from the early days of R. o call_R and call_S are deprecated. They still exist in the headers and as entry points, but are no longer documented and should not be used for new code. BUG FIXES: o str(x, width) now obeys its width argument also for function headers and other objects x where deparse() is appli...

...fix in R-exts.texi, PR#523. o Linpack.h now makes clear which routines are actually in R. o Entry-point "pythag" is now loaded even though it is not necessarily used in R. Where "hypot" is available pythag just calls hypot after checking for special values. o call_R will now correctly handle character vector arguments. o The alphabet links on top of HTML function indices with more than 100 entries now contain only the letters which are really first letters of at least one entry. -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'...

...fix in R-exts.texi, PR#523. o Linpack.h now makes clear which routines are actually in R. o Entry-point "pythag" is now loaded even though it is not necessarily used in R. Where "hypot" is available pythag just calls hypot after checking for special values. o call_R will now correctly handle character vector arguments. o The alphabet links on top of HTML function indices with more than 100 entries now contain only the letters which are really first letters of at least one entry. -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'...