similar to: OpenSSH flow diag

Dear all I have the following problem. M <- matrix(0,3,3) # dimension of M is dinamic and this can lead to the next subscript diag(M[1,1]) <- rep(100,1) #Error in `diag<-`(`*tmp*`, value = 100) : # only matrix diagonals can be replaced diag(M[1,1,drop=F]) <- rep(100,1) #Error in diag(M[1, 1, drop = F]) <- rep(100, 1) : # incorrect number of subscripts diag(M[2:3,1:2]) <-

I would say it is a mis-feature. If the 'x' argument of diag() is a vector of length 1, then it creates an identity matrix of that size, instead of creating a 1x1 matrix with the given value: ? diag(3) [,1] [,2] [,3] [1,] 1 0 0 [2,] 0 1 0 [3,] 0 0 1 Of course this makes it cumbersome to use diag() in a package, when you are not sure if the input vector is

If something goes wrong in the kvm io bus handling, the virtio-ccw diagnose may return a negative error value in the cookie gpr. Document this. Signed-off-by: Cornelia Huck <cohuck at redhat.com> --- Even if the virtio spec is the correct place to specify what diag 500 subcode 3 does, we also should mention here that the cookie may be an error. ---

Dear all, I am trying to use the Matrix package to do some calculations on rather large and sparse matrices. An example of such a matrix is given below. mig<-0.2 side<-10 np<-side^2 mig.mat<-matrix(0,np,np) diag(mig.mat[1:(np-side),(side+1):np])<-mig/4 diag(mig.mat[(side+1):np,1:(np-side)])<-mig/4 diag(mig.mat[-np,-1])<-mig/4

This is not at all something new(*). As maintainer of the Matrix package, I don't like this inconsistency of base R's diag(). We have had the following -- forever, almost surely inherited from S and S+ : diag(x) preserves the storage mode of x for 'complex' and 'double' precision, but converts integer and logicals to double : > storage.mode(x <- 1i + 1:7);

From: Jean-Christian de Rivaz <jc at eclis.ch> I suspect that some instructions about how to use the diag/mbr was not updated when the source file was renamed to handoff.S. Here is a simple proposition to fix that. Jean-Christian de Rivaz --- diag/mbr/README | 4 ++-- diag/mbr/handoff.S | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/diag/mbr/README

The following changes since commit 7c1b588f9a918b5e251773f0ef4f3812859cc159: H. Peter Anvin (1): Merge remote-tracking branch 'genec/diag-geodsp-perl-for-hpa' are available in the git repository at: git://github.com/geneC/syslinux.git diag-mbr-fix-for-hpa Gene Cumm (1): diag/mbr: Clarify README Jean-Christian de Rivaz (1): Update diag/mbr instruction to match

Martin Maechler wrote: > diag(x) preserves the storage mode of x for 'complex' and > 'double' precision, but converts integer and logicals to double : Duncan Murdoch wrote: > I think the change to preserve integer makes sense, but preserving > logical does not. A diagonal matrix has zeros off the diagonal, and > they are not logical. Having diag() sometimes

Yes, both are rooted in age-old design infelicities (in which, basically, interactive expedience has taken precedence over consistency and generality). Unfortunately, they are quite difficult to rectify, because there are bound to be countless uses of, say, diag(5) as a 5x5 identity matrix which would break if it suddenly meant the 1x1 matrix(5) instead. We'd need a very carefully

From: Sylvain Gault <sylvain.gault at gmail.com> The Makefile used to have a dependency to an unused linker script. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- diag/mbr/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/diag/mbr/Makefile b/diag/mbr/Makefile index 5b7153c..7901fea 100644 --- a/diag/mbr/Makefile +++ b/diag/mbr/Makefile @@

Along Luke's lines, would(n't) it be enough to look for existence of attribute 'class' to decide whether to dispatch or not, i.e. if c() is needed or not? Even without .subset(), there is a remarkable improvement. I think it's worth condition the code on dispatch or not. For example: [HB-X201]{hb}: svn diff diag.R Index: diag.R

Full_Name: David Duffy Version: 1.0.1 OS: Linux Submission from: (NULL) (152.98.96.21) Documentation for diag() states that "If x is a vector (or a 1-d array) then diag(x) returns a diagonal matrix whose diagonal is x." > m<-matrix(1:4,ncol=1) > diag(m) [1] 1 diag(as.vector(m)) gives the advertised performance. Fix: Change documentation.

Hi All, I'm wondering why when passing a single numeric value that contains any decimals to diag() that the value is silently coerced to a integer for constructing an identify matrix. To me, an input like diag(5.435) seems fairly ambiguous and is more than likely a programming mistake, since it's not obvious that a 5x5 identity matrix should be created. I've seen some code where other

(I asked this question on StackOverflow <http://stackoverflow.com/q/30035939/1191259> a short time ago; sorry if you're seeing it again. Feel free to answer there as well if you like. The code formatting and such on that site can be nice.) I benchmarked matrix and vector subsetting to extract the diagonal of a square matrix against the diag() function, and the latter lost by a wide

As kindly pointed out to me (oh my decaying gray matter), is.object() is better suited for this test; $ svn diff src/library/base/R/diag.R Index: src/library/base/R/diag.R =================================================================== --- src/library/base/R/diag.R (revision 68345) +++ src/library/base/R/diag.R (working copy) @@ -23,9 +23,11 @@ stop("'nrow' or

Dear all, According to CHANGES IN R 3.0.0: o diag() as used to generate a diagonal matrix has been re-written in C for speed and less memory usage. It now forces the result to be numeric in the case diag(x) since it is said to have 'zero off-diagonal entries'. diag(x) does not work for character vector in R 3.0.0 any more. For example, v <- c("a",

> From: Martin Maechler <maechler at lynne.stat.math.ethz.ch> > diag() should not work only for pure matrices, but for all > "matrix-like" objects for which ``the usual methods'' work, such > as > as.vector(.), c(.) > > That's why there has been the c(.) in there. > > You can always make code faster if you write the code so it only >

Dear list A strange bug in the psych package is due to the behavior of the diag function: It gives the expected values for 1, a vector (-1,1), but not for -1 Is this a known feature? > diag(1) [,1] [1,] 1 > diag(c(-1,1)) [,1] [,2] [1,] -1 0 [2,] 0 1 > diag(-1) Error in diag(-1) : invalid 'nrow' value (< 0) Bill William Revelle

It concerns trival diagonal matrices: > diag(1) [,1] [1,] 1 > diag(rnorm(1)) <0 x 0 matrix> > diag(rnorm(1),nrow=1) [,1] [1,] 0.4843697 There's an obvious work around... but I thought it was worth notifying the list. Regards, John Marsland ********************************************************************** This is a commercial communication from

git://git.zytor.com/users/genec/syslinux.git Branch diag-geodsp-for-hpa http://git.zytor.com/?p=users/genec/syslinux.git;a=shortlog;h=refs/heads/diag-geodsp-for-hpa Updates to diag/geodsp/Makefile and an additional variable (XZ) in mk/syslinux.mk. This removes unnecessary parts and makes the recipes more generic by using make variables. -- -Gene