similar to: What' wrong?

Hi, Suppose that I have a list where each component is a list of two matrices. I also have a vector of weights. How can I collapse my list of lists into a single list of two matrices where each matrix in the result is the weighted sum of the corresponding matrices. I could use a loop but this is a nested calculation so I was hoping there is a more efficient way to do this. To help clarify,

> sessionInfo() R version 2.15.0 (2012-03-30) Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit) locale: [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8 attached base packages: [1] grid datasets splines utils stats [6] graphics grDevices methods base other attached packages: [1] effects_2.1-0 colorspace_1.1-1 [3] nnet_7.3-1

I'm doing prediction of the survival cases using gene expression profiles(Affymetrix chips). Can somebody tell me how to use the Cox PH model to select genes and make a prediction of survival? Thanks. Guangchun

Dear r-users, I want to use the Cox's ph model to analyze survival data set. How can I extract the model coefs. and Wald test p-value or Score? For example: I use the data set melanom in iSwR package. > library(survival) > data(melanom) > attach(melanom) > cox.model <- coxph(Surv(days,status==1)~sex) > summary(cox.model) Call: coxph(formula = Surv(days, status == 1) ~

Dear R-users/helpers, Does anyone tell me how to retrieve the data frame column names? I'm working on coxph model to analyze survival data of Affy DNA chips. I get the coxph coef p-value for each probe and want output the probe name with the p-value. The probe names are the data frame column names. How can I do this? Thanks for your help. Guangchun

[This email is either empty or too large to be displayed at this time]

Hi, Thank you for your work on this card! I have quite a few boxes that run various 3wares cards with diverse firmware revs. Are there any caveats with respect to models and firmware versions in terms of how they might interact ? ---Mike At 01:25 PM 10/08/2003 -0700, Paul Saab wrote: >ps 2003/08/10 13:25:46 PDT > > FreeBSD src repository > >

Currently when converting a Windows guest we do a minimum installation of the viostor driver, configure the RHEV guest agent and leave RHEV to properly install viostor and all remaining drivers. This works well if RHEV is properly configured and the installation is not interrupted on first boot. However, if the target of the conversion is not RHEV, RHEV is not properly configured, or the first

This patch allows paths in virt-v2v.conf to be either relative or absolute. If relative, they are relative to software-root. This allows virt-v2v.conf to use files provided by packages independent of virt-v2v. --- lib/Sys/VirtV2V/Config.pm | 10 ++++++---- 1 files changed, 6 insertions(+), 4 deletions(-) diff --git a/lib/Sys/VirtV2V/Config.pm b/lib/Sys/VirtV2V/Config.pm index f703152..121e774

Martin Maechler writes: > There may be one small problem: IIUC, the wayback machine is a > +- private endeavor and really great and phantastic but it does > need (US? tax deductible) donations, https://archive.org/donate/, > to continue thriving. > This makes me hesitate a bit to link to it within the "base R" > documentation. But that may be wrong -- and I should

The code for mounting the transfer iso in Converter::Windows didn't do the same level of error checking as the same code in GuestOS::RedHat. This change moves the GuestOS code into Config, and updates both GuestOS::RedHat and Converter::Windows to use Config. Fixes RHBZ#596091 --- lib/Sys/VirtV2V/Config.pm | 51 ++++++++++++++++++++++++ lib/Sys/VirtV2V/Converter/Windows.pm |

We were unconditionally creating /temp/v2v in the guest, and later using case_sensitive_path to look the path up again. If C:\Temp already existed, this would lead to unpredictable results. Fixes RHBZ#672521 --- lib/Sys/VirtV2V/Converter/Windows.pm | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-) diff --git a/lib/Sys/VirtV2V/Converter/Windows.pm

During a Windows conversion, _prepare_virtio_drivers aborts the conversion completely if the configured virtio driver path does not exist. If the path exists but is empty, the conversion completes correctly by defaulting to the non-virtio drivers. This patch treats a missing directory just like missing drivers, by reporting a message, then defaulting to non-virtio drivers. ---

Hi List I have a series of zip archives each containing several files. One of these files is called goCats.txt and I would like to read it into R from the archive. It's a simple tab delimited text file. pathToZip <- '/home/iain/Documents/Work/Results/bovineMacRNAData/deAnalysis/afInfection/commonNorm/twoHrs/af2hrs.zip' z <- unz(pathToZip, 'goCats.txt', 'r') zT

>>>>> Thomas Levine <_ at thomaslevine.com> >>>>> on Fri, 28 Jul 2017 18:53:16 +0000 writes: > The attached patch corrects a dead link in the treering > documentation. The URL in the manual [1] refers to a > personal home page belonging to Christine Hallman (user > "hallman") on the website of the University of Arizona

This removes another chunk of functionality from GuestOS. --- MANIFEST | 1 + lib/Sys/VirtV2V/Config.pm | 339 +++++++++++++++++++++++++++++++++++++ lib/Sys/VirtV2V/Converter.pm | 56 +----- lib/Sys/VirtV2V/GuestOS.pm | 94 ---------- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 46 ++++-- v2v/virt-v2v.pl | 96 +---------- 6 files

Previously, only the LibVirtXML connection translated network and bridge names in imported metadata. This change moves this functionality in Converter, making it available to LibVirt connections as well. At the same time, the format of the config file is switched to XML. The primary driver for this is that the allowable syntax of a foreign network/bridge name is not known. Rather than create a

This is my lightly tested patch which allows pre-conversion of Windows guests. You also need to supply rhsrvany.exe and firstboot scripts. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc.

Previously, only the LibVirtXML connection translated network and bridge names in imported metadata. This change moves this functionality in Converter, making it available to LibVirt connections as well. At the same time, the format of the config file is switched to XML. The primary driver for this is that the allowable syntax of a foreign network/bridge name is not known. Rather than create a

This patch refactors the data transfer code with several goals: * Have a common read(source)/write(target) loop so that common processing can happen in the middle of it, e.g. format change/progress bar * Provide volume metadata to transfers to allow smarter reading/writing, e.g. of sparse files * Simplify the data transfer code The patch *isn't* NFC because there are some minor behaviour