search for: datall

Hi the list. Is there a bug in mmlcr package ? The following code does not compile: mmlcrTest <- function(dataW){ dataL <- reshape(dataW,idvar="id",timevar="T",varying=list("T0","T1","T2"),direction="long",v.names="score") resultR <- mmlcr(outer= ~ 1 | id, components = list(list(formula =

Hello, I've been trying to use ggplot, but I cannot seem to get my data in the correct form. I usually have a vector x, and a matrix y and I would usually use matplot(x,y) to plot the columns of y against x. Now, if i understand correctly, I should cast x and y into a data.frame and do something like ggplot(x,y,data=data). I think I'm missing something here: do I really need to

...bind(c(NA, NA, NA, NA, 1), c(NA, NA, NA, 1, NA), c(1,1,NA,NA,NA))) names(anchor) <- c("A1","A2", "A3") items <- list(as.data.frame(cbind(c(NA, NA, NA, NA, 1), c(NA, NA, NA, 1, NA), c(1,1,NA,NA,NA)))) #let's assume these are the items that I want to estimate datAll <- testEquatingData(items, AnchoringItems = anchor) Now, after I run the testEquatingData() function, the order of the variables has been changed to A3, V3, A1, A2, V1, V2, instead of, for example A1, A2, A3, V1, V2,V3, or V1, V2, V3, A1, A2, A3. Since I am using the constraint function of the...

The CLONE and CLONE_RANGE ioctls round up the range of extents being cloned to the block size when the range to clone extends to the end of file (this is always the case with CLONE). It was then using that offset when extending the destination file''s i_size. Fix this by not setting i_size beyond the originally requested ending offset. This bug was introduced by a22285a6 (2.6.35-rc1).

dear R users, I have troubles performing Moran.I test as suggested on http://www.ats.ucla.edu/stat/r/faq/morans_i.htm my spatial data are longitude and lattitide of communities. The calculation of the inverse distance matrix according to the homepage (using my data) datAL <- read.csv2("C:\\Konvergenz AL.csv", header=T) ALdist <- as.matrix(dist(cbind(datAL$L?nge,

Returns a file''s size on disk. Had been posted by Chris Ball over a year ago (http://article.gmane.org/gmane.comp.file-systems.btrfs/2873). Chris Mason suggested a couple of improvements back then, which I have implemented in this version: - use u64 to return the result - replaced the loop while (1) { struct btrfs_ordered_extent *ordered;

Hi, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN)

I've tried several times to get superOdoctor to run on this machine, and have had no luck yet. Aside from this error message, # superodoctor ***************************************************************************** Supero Doctor II - Linux version 2.24(060523) Copyright(c) 1993-2006 by Super Micro Computer, Inc. http://supermicro.com/

Hi All I've got an asterisk system, using a couple of Xorcom Astribanks to provide FXS ports. (I'm using the zaptel 1.2 branch, if that matters) I've noticed that the ringing volume is a lot louder than on our old phone system, and people are starting to complain it's too loud. (This is the noise the phone makes when it rings, not the noise in your handset when you ring

Document those places in the btrfs code which are BUGing on non-fatal error conditions that should be handled by proper error paths. This makes it easier to distinguish between what needs fixing versus which BUG_ON''s we might want to keep (to trap code bugs, unexpected inconsistencies, etc). Do this with a trivial macro, ''btrfs_fixable_bug_on'' which just defines to

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them