similar to: Only referenc copy when calling C routine?

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

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

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

I try memory.size function to find out available memory size, but surprisingly R complains it can't find the function. ?memory.size also failed. Is it not in the base library? If so, why can't my R find it? I am using the binary 1.9.0 version for Mandrake 9.1. Thanks in advance. Daehyok Shin Terrestrial Hydrological Ecosystem Modellers Geography Department University of North

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 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 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

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

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

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 have read R's Writing Extensions manual and am still confused about how to use some of the routines there when I call from C. Specifically, I am writing a little test function which I will optimize using the nmmin function which underlies R's optim() with Nelder-Mead. I guess I wonder what library/header files I should be using. I was using R_ext/Applic.h and linking with libR but I

Currently, enable/disable turbo mode on AMD is broken: $ xenpm enable-turbo-mode 0 <-- works and proper CPU MSR bit is set $ xenpm enable-turbo-mode 1 <-- silently broken, MSR bit not set Since ->turbo is per policy, when user requests to enable/disable turbo mode, we need to set the bit in all of the ->cpus that this policy affects. --- xen/arch/x86/acpi/cpufreq/powernow.c | 2

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

Currently cpufreq and xenpm are out of sync. Fix cpufreq reporting of if turbo mode is enabled or not. Fix xenpm to not decode for tristate, but a boolean. Signed-off-by: Jacob Shin <jacob.shin@amd.com> --- tools/misc/xenpm.c | 14 +++----------- xen/drivers/cpufreq/utility.c | 2 +- 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/tools/misc/xenpm.c

Hello, everyone I have a piece of code that looks like this: mrets <- merge(mrets, BMM.SR=apply(mrets, 1, MyFunc, ret="BMM.AV120", stdev="BMM.SD120")) mrets <- merge(mrets, GM1.SR=apply(mrets, 1, MyFunc, ret="GM1.AV120", stdev="GM1.SD120")) mrets <- merge(mrets, IYC.SR=apply(mrets, 1, MyFunc, ret="IYC.AV120",

Hi, This patch removes the magic number "31" for readability. The number "31" means the idle domain ID. In detail: - display the idle domain ID with "Idle" instead of "31" - write to the file "log-idle.log" instead of "log-dom31.log". Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Thanks, -- KUWAMURA