similar to: Can't find memory.size()

The interface for dates in R is a little confusing to me. I want to create a vector of Date objects from vectors of years, months, and days. One solution I found is: years <- c(1991, 1992) months <- c(1, 10) days <- c(1, 2) dates <- as.Date(ISOdate(years, months, days)) But, in this solution the ISOdate function converts the vectors into characters, which can cause serious

I am handling spatial data of huge volumes, so sensitive to the silent duplication of data in script programs. In the following R program, exactly when is the vector data deeply copied? Thanks in advance. 1 v <- 1:10000 2 z <- f(v) --------- function f ---------- 3 f <- function(x) { 4 y = x 5 y[10] = 1 6 xf = date.frame(x=x) 7 xf$x[10] = 1 8

I am curious if there is any way to list only variables or functions in current environment, rather than listing all objects? Thanks. -- Daehyok Shin (Peter) Geography Department Univ. of North Carolina-Chapel Hill

I am curious if there is any way to list only variables or functions in current environment, rather than listing all objects? Thanks. -- Daehyok Shin (Peter) Geography Department Univ. of North Carolina-Chapel Hill

Exactly where does R search for foo.R if I type source("foo.R")? Only from current working directory (same as getwd()), from all directories specified by e.g. $PATH? Thanks. Daehyok Shin

Exactly where does R search for foo.R if I type source("foo.R")? Only from current working directory (same as getwd()), from all directories specified by e.g. $PATH? Thanks. Daehyok Shin

What happens when I pass an array to a dynamically linked C routine? Is only its reference copied when an array is passed and returned? Or, is its whole content copied? In R extension manual, I found the following description. But, I can't know exactly which is true. "There can be up to 65 further arguments giving R objects to be passed to compiled code. Normally these are copied before

When I tried the following commands, I got a strange message. > x<-data.frame(y=c(1:10)) > plot(x$z) Error in xy.coords(x, y, xlabel, ylabel, log) : x and y lengths differ "The data frame, x, does not have a field named z." may be better user-friendly message for this kind of common error. Daehyok Shin

When I tried the following commands, I got a strange message. > x<-data.frame(y=c(1:10)) > plot(x$z) Error in xy.coords(x, y, xlabel, ylabel, log) : x and y lengths differ "The data frame, x, does not have a field named z." may be better user-friendly message for this kind of common error. Daehyok Shin

I am looking for a package to read and write NetCDF files. NetCDF package says it can only read, not write. Another package for the standard binary file format? Daehyok Shin

I have found the use of save( ) and attach( ) when supported by a pair of functions written by my colleague John Miyamoto, move( ) and rm.sv( ) quite useful in managing (1) collections of useful homebrew functions, (2) project workspaces, and (3) "packages" under development. An .Rdata file containing these and other handy functions together with a brief supporting document can be

While installing my small package, I met a tricky problem. For clarity, let me explain it with the following simplified example. In ~/pkg/R/aclass.R, setClass("aclass", contains="bclass", representation(i="numeric")) In ~/pkg/R/bclass.R, setClass("bclass", representation(j="numeric")) After building a "pkg" package, the file

Dear R list, I am having some trouble drawing a bar-graph with two groups, both of which are stacked. A sample of my data (IUCN and national conservation status for marine and terrestrial species) look like this: Status IUCN Terrestrial IUCN Marine National CS Terrestrial National CS Marine NE 168 69 16 69 LC 41 6 148 6 NT 5 4 7 4 VU 4 2 7 2 EN 4 2 4 2 CR 1

Dear R list, It appears that my request from yesterday got a bit garbled. I have tried to rephrase and retype it - please let me know if you can help me - I am having some trouble drawing a bar-graph with two groups, both of which are stacked. I would like to plot the conservation status according to two classifications (i.e. my groups - IUCN status and national status), and for each of those

Hi, Assuming that your dataset is similar to the one below: set.seed(25) dat1<- data.frame(Algae.Mass=sample(40:50,10,replace=TRUE),Seagrass.Mass=sample(30:70,10,replace=TRUE),Terrestrial.Mass=sample(80:100,10,replace=TRUE),Other.Mass=sample(40:60,10,replace=TRUE),Site.X.Treatment=rep(c("ALA1A","ALA1U"),each=5),stringsAsFactors=FALSE) library(reshape2)

What's the preferred way in R for handling samples with binary data (like chemical fingerprints encoded as hexadecimal strings with 0's and 1's indicating the absence or presence of chemical features) in methods such as clustering and MDS. Do you always have to expand the fingerprint data into individual variables (which can be a few hundreds) or can they be used directly as binary

Hi: I am a very recent user of R 1.40 for MacOSX and went through the help files but did not not find the function that I am looking for. I have two comma separated files which I want to partly combine. File 1 has 49670 lines and 26 columns (separated by commas) and looks like this: ...

Thanks John. Your approach worked fine for my small toy program. Now, I would like to run my module pass on a huge project (still a single executable) consisting of a few thousand bit code files scattered in many different directories. And some of them are static libraries. Do you still think it's a good idea to manually gather and link them with llvm-ld? I've seen other module pass

On 8/19/11 4:36 PM, Jinwook Shin (HOTWING) wrote: > > Thanks John. Your approach worked fine for my small toy program. Now, > I would like to run my module pass on a huge project (still a single > executable) consisting of a few thousand bit code files scattered in > many different directories. And some of them are static libraries. Do > you still think it's a good idea

Thanks John. I appreciate your help. I have taken the libLTO approach and it worked like a charm :) For those who wanted to achieve the same thing, below are the steps I've taken. John -- a small question: I thought I wouldn't need to touch Makefiles at all, but that wasn't the case. Could you take a look at Step 4) and tell me what you think? Thanks! 1) Create your own libLTO and