similar to: Deep copy in R

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

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

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

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

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

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, Everybody: This may not be a "bug", but for me it is an unexpected outcome. A factor variable's levels do not retain their ordering after the levels function is used. I supply an example in which a factor with values "BC" "AD" (in that order) is unintentionally re-alphabetized by the levels function. To me, this is very bad behavior. Would you agree? #

On 15 Feb 2018, at 15:45, Siegmar Gross via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > today I've tried to build llvm-6.0.0rc2 using Cmake on my "SUSE Linux > Enterprise Server 12.3 (x86_64)" with the following commands (gcc-6.4.0 > is necessary for CUDA-9.0). > > > wget http://prereleases.llvm.org/6.0.0/rc2/llvm-6.0.0rc2.src.tar.xz > wget