similar to: R-Oracle (was Internal data types)

Displaying 20 results from an estimated 10000 matches similar to: "R-Oracle (was Internal data types)"

1999 Nov 23
1
Internal data types
Hi- I'm very interested in using R, though I am still new to it. However, all of the data I'm working with is currently stored in Oracle. So, either I get data from Oracle, save it to a text file, and then import it to R, or I write an R <-> Oracle bridge. I've taken the second approach, but I'm sure that I haven't done it entirely correctly. For starters, is there
2002 Sep 10
1
setGeneric(); R CMD check
1. Is it always the case that when defining generic functions in a package, the package needs to be installed as a binary package to avoid having the generic functions in the .GlobalEnv? 2. Defining a generic function in a "non-binary" package triggers a check warning $ R CMD check ... ... * checking for code/documentation mismatches ... WARNING Objects
2001 Apr 05
0
Re: [R] Hmisc and Design libraries
Great news! Having spent a significant amount of time porting/mantaining some packages on S4/Splus 5.x and R, I'm interested in your experience as you port Hmisc and Design; I'd like to know of your progress in order to help improve available R/Splus portability tools both at the C and the S language code. These tools include the package SLanguage written by John Chambers, and
2003 Apr 22
0
ROracle 0.5-0 package update
An update to the ROracle package is now in CRAN. Version 0.5-0 * This version has an experimental dynamic SQL binding to data frames. SQL statements can be "prepared" (parsed and cached for improved performance), and columns of data frames bound to them for automatic data transfer). For details see the help() for "Oracle", "dbPrepareStatement" and
2002 Dec 12
1
lattice/points and pch="c" inconsistencies
Hi, The current lattice/grid packages seem to position character plotting symbols (e.g., ".") differently than the base function points. The following shows what I mean: ## plain old points() positions the pch="." right at y = c(0,1), ## and thus abline(h = c(0,1)) completely hides the points "." ## (provided the output device has enough resolution, like
2001 Apr 24
2
assigning objects from .C/.Call
Hi, In section 4.6.7 of "Writing R Extensions" (Version 1.2.1, 2001-01-15) the C function defineVar() is described as "... the equivalent of assign(symbol, value, envir = rho, inherits = FALSE) ..." I interpreted the above (wrongly) as meaning that defineVar() makes a copy of its "value" argument into the object whose name is specified in "symbol" in
2000 Nov 20
2
precision, incorrect(?) tapply() NA's
Hi, Summary: I ran into some unexpected behavior in approx() and tapply() that introduced NA's in "clean" data due to (?) numerical accuracy/round off. The culprit seems to be in match() that coerces it's arguments to character, loosing precision in the process. [R development version 1.2.0, 08 Nov 2000, on Linux] Example: > r > [1] 0.6931472 0.6931472 0.6931472
2000 Nov 20
2
precision, incorrect(?) tapply() NA's
Hi, Summary: I ran into some unexpected behavior in approx() and tapply() that introduced NA's in "clean" data due to (?) numerical accuracy/round off. The culprit seems to be in match() that coerces it's arguments to character, loosing precision in the process. [R development version 1.2.0, 08 Nov 2000, on Linux] Example: > r > [1] 0.6931472 0.6931472 0.6931472
2000 Feb 21
1
OpenSSH doesn't compile under Solaris 2.3 Sparc
Hi, We are trying to get OpenSSH-1.2.2 stable release to compile under Solaris 2.3 Sparc. It worked perfect for Solaris 2.5, Solaris 2.5.1, Solaris 7 (All on Sparc) and Linux 2.2.13 Intel x86 OpenSSL installs fine without problem, zlib is installed fine without problems and egd.pl installs fine without problems. These are all the current releases, I can get the version numbers if you need
2001 Feb 07
1
RE: [R] Removing "row.names"
> Date: Wed, 7 Feb 2001 09:33:12 -0800 (PST) > From: Thomas Lumley <tlumley@u.washington.edu> > To: Kurt Hornik <Kurt.Hornik@ci.tuwien.ac.at> > cc: Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk>, R-devel@r-project.org > Subject: Re: [Rd] RE: [R] Removing "row.names" > MIME-Version: 1.0 > > On Wed, 7 Feb 2001, Kurt Hornik wrote: > > >
1999 Dec 10
1
FAQ: 8.2 How can I debug dynamically loaded code?
I'm having some trouble following the instructions in the FAQ for debugging. I can run 'R -d gdb' at the command line and it works; also, I have run gdb from emacs before. But I can't figure out how to put the two together: I've tried following the instructions in the FAQ, but I seem to be missing something. Can someone with experience tell me exactly how I should invoke gdb
2009 Feb 04
2
Sweave and \Sexpr{}
Hi: I am trying to create a dynamic latex table using \Sexpr{} but it's not evaluating it. I also tried the example below without Sweave and also fails. I have also copied the Sweave.sty to my working directory but nothing seems to work. Do I need to have certain package in order to run \Sexpr{}? \documentclass[a4paper]{article} \usepackage{C:/R/R-2.8.1/share/texmf/Sweave} \begin{document}
2003 Oct 16
4
data() misbehaving inside a function
Calls of the form data(package = pkg) inside a function incorrectly fail ("pkg" is a local variable). For instance, foo <- function(pkg) data(package = pkg) foo("base") Error in .find.package(package, lib.loc, verbose = verbose) : none of the packages were found ## workaround -- force argument "package" to be an expression ## (not a
2001 Feb 09
1
tabular data (was RE: [R] Removing "row.names")
Hi, I agree that replacing data.frames for modeling functions would be too painful. Also I agree with Thomas that new class(es) for tabular data should not inherit from data.frame, and that data.frames should conceptually inherit from some other base tabular data class. At this point I'm not suggesting anything in concrete --- I haven't sorted it out in my own mind --- but I want
2017 Mar 03
0
Control statements with condition with greater than one should give error (not just warning) [PATCH]
>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>> on Fri, 3 Mar 2017 00:52:16 -0800 writes: > I'd like to propose that the whenever the length of condition passed > to an if or a while statement differs from one, an error is produced > rather than just a warning as today: >> x <- 1:2 >> if (x == 1)
2000 Jan 28
2
Memory woes
Hello all- I'm having some problems with memory consumption under R. I've tried increasing the appropriate memory values, but it keeps asking for more; I've even upped the heap size to 600M, significantly eating into swap (256M real, 500+M swap). So, performance slows to a crawl. What I'm trying to do is run isoMDS on a 4000x4000 matrix. My first question is, how much memory
2000 Mar 03
2
Re: [Omega-devel] StatDataML
Hi, I just had a very quick look at the StatDataML proposal --- nice work! At the risk of showing my ignorance, I want to mention my first impressions. My first impression is that defining datasets in terms of arrays and list is a bit too high a level. What about simpler vectors, scalars? (I know that R/S don't have scalars, but other systems/applications do.) Can we think of a core
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
On Fri, Mar 3, 2017 at 9:22 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>>> on Fri, 3 Mar 2017 00:52:16 -0800 writes: > > > I'd like to propose that the whenever the length of condition passed > > to an if or a while statement differs from one, an
2002 Aug 16
1
Summary:ROracle error
Oracle is finally up and running on RH 7.3 now. I will try to summarize the pitfalls to avoid here for future reference. 1> Make sure you have the Pro C/C++ drivers in Oracle client installed. This can be verified by looking for the existence of the proc directory in $ORACLE_HOME. Existence of proc means it worked 2> Put the following in the .bashrc script in root export
2017 Mar 03
2
Control statements with condition with greater than one should give error (not just warning) [PATCH]
I'd like to propose that the whenever the length of condition passed to an if or a while statement differs from one, an error is produced rather than just a warning as today: > x <- 1:2 > if (x == 1) message("x == 1") x == 1 Warning message: In if (x == 1) message("x == 1") : the condition has length > 1 and only the first element will be used There are