similar to: 0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)

Displaying 20 results from an estimated 2000 matches similar to: "0/1 vector for indexing leads to funny behaviour (PR#8389) (maybe a documentation deficiency?)"

2005 Dec 13
4
0/1 vector for indexing leads to funny behaviour (PR#8389)
Full_Name: Axel Rasche Version: 2.2.0 OS: Linux Submission from: (NULL) (141.14.21.81) Dear Debuggers, This is not a serious problem. Are 0/1 vectors intended to be used as index vectors? If yes, there is a bug. If not, it leads just to some funny behaviour rather than an error message. In the appendix is some simple code to reproduce the problem. A logical vector as.logic(a) helps by indexing
2005 Jun 15
3
write.table confused by rownames/colnames (PR#7941)
Full_Name: Axel Rasche Version: 2.1.0 OS: Win2000 Submission from: (NULL) (141.14.21.81) Hi, write.table does not accept the second statement with <col.names = NA, row.names = FALSE>. I do not see why this should not be possible. test = matrix(1:4, 2, 2, dimnames = list( c("a","b"), c("c","d") )) write.table(test, file = "test.txt",
2008 Aug 13
1
summary.manova rank deficiency error + data
Dear R-users; Previously I posted a question about the problem of rank deficiency in summary.manova. As somebody suggested, I'm attaching a small part of the data set. #*************************************************** "test" <- structure(.Data = list(structure(.Data = c(rep(1,3),rep(2,18),rep(3,10)), levels = c("1", "2", "3"), class =
2009 Feb 18
0
Index-G1 error
I am using some functions from package clusterSim to evaluate the best clusters layout. Here is the features vector I am using to cluater 12 signals: > alpha.vec [1] 0.8540039 0.8558350 0.8006592 0.8066406 0.8322754 0.8991699 0.8212891 [8] 0.8815918 0.9050293 0.9174194 0.8613281 0.8425293 In the following I pasted an excerpt of my program:
2010 Oct 07
2
[LLVMdev] [Q] x86 peephole deficiency
Hi all, I am slowly working on a SwitchInst optimizer (http://llvm.org/PR8125) and now I am running into a deficiency of the x86 peephole optimizer (or jump-threader?). Here is what I get: andl $3, %edi je .LBB0_4 # BB#2: # %nz # in Loop: Header=BB0_1 Depth=1 cmpl $2, %edi
2010 Oct 07
0
[LLVMdev] [Q] x86 peephole deficiency
On Oct 6, 2010, at 6:16 PM, Gabor Greif wrote: > Hi all, > > I am slowly working on a SwitchInst optimizer (http://llvm.org/PR8125) > and now I am running into a deficiency of the x86 > peephole optimizer (or jump-threader?). Here is what I get: > > > andl $3, %edi > je .LBB0_4 > # BB#2: # %nz >
2010 Oct 07
1
model.frame deficiency
The model.frame function has trouble with a certain type of really long formula. Here is a test: tname <- paste('var', 1:50, sep='') tmat <- matrix(rnorm(500), ncol=50, dimnames=list(NULL, tname)) tdata <- data.frame(tmat) temp1 <- paste( paste(tname, tname, sep='='), collapse=', ') temp2 <- paste("~1 + cbind(", temp1, ")")
2010 Oct 13
2
[LLVMdev] [Q] x86 peephole deficiency
Am 07.10.2010 um 19:50 schrieb Chris Lattner: > > On Oct 6, 2010, at 6:16 PM, Gabor Greif wrote: > >> Hi all, >> >> I am slowly working on a SwitchInst optimizer (http://llvm.org/ >> PR8125) >> and now I am running into a deficiency of the x86 >> peephole optimizer (or jump-threader?). Here is what I get: >> >> >> andl $3,
2010 Apr 13
0
dbFD computing distinct species wrong?
Hi everyone, I am working with the dbFD function of the FD package, and there's something funny happening with the value of sing.sp in the output. Basically, I have a species-function matrix and a community matrix. One site in particular has 6 species, 4 of which have identical functional coding. I thus expect nbsp = 6 and sing.sp = 2 for this site. However, nbsp = sing.sp = 6. This
2005 Apr 14
1
(no subject)
I have an issue with W2K/XP using Folder Redirection to a Samba homes share (or any share for that matter). This is only a problem when access?for a user is via an ACE (ACL) and not the traditional file system permissions. So for example (user is test in this example): # ls -ld History/ drwxrwx---+?? 3 root???? root???????? 4096 Apr 12 21:15 History/ # getfacl History # file: History # owner: root
2024 Apr 21
1
x[0]: Can '0' be made an allowed index in R?
?s 08:55 de 21/04/2024, Hans W escreveu: > As we all know, in R indices for vectors start with 1, i.e, x[0] is not a > correct expression. Some algorithms, e.g. in graph theory or combinatorics, > are much easier to formulate and code if 0 is an allowed index pointing to > the first element of the vector. > > Some programming languages, for instance Julia (where the index for
2012 Dec 23
1
I small deficiency in postfix 2.6.6 on Centos 6.3
posfconf debugger_command does not work. This is a 'known' problem with 2.6 and fixed in postfix 2.9. This is tied into the large code rewrite in 2.9, and thus cannot be patched in 2.6. You can see my thread on this over on the postfix list. There was a comment how those running 4 year old code can look forward to the new troubleshooting and support features in 2.10...
2010 Oct 13
0
[LLVMdev] [Q] x86 peephole deficiency
On Oct 13, 2010, at 11:22 AM, Gabor Greif wrote: > Hi Chris, > > I had a look into MachineCSE, but it looks like MBB-oriented. > The above problem is an inter-block one. Also MCSE seems > to perform value numbering on virtual/physical registers, which > does not map very well to status register bits that are implicitly > defined. > Any chance to recast this issue as a
2003 Nov 22
3
summary.manova and rank deficiency
Hi all, I have received the following error from summary.manova: Error in summary.manova(manova.test, test = "Pillai") : residuals have rank 36 < 64 The data is simulated data for 64 variables. The design is a 2*2 factorial with 10 replicates per treatment. Looking at the code for summary.manova, the error involves a problem with qr(). Does anyone have a suggestion as to how to
2007 Aug 05
0
null hypothesis for two-way anova
Dear R community, Confused by some of my lab results I ask for the definition of the null hypothesis of a two-way analysis of variance in R (anova() and aov()). Starting with the following model y = a_i + b_j , i in A and j in B is the tested null hypothesis H_0: a_i = 0 for all i in A or H_0: a_m = a_n for any m and n in A? Consequently the same questions for interaction effects.
2005 Apr 18
2
Folder Redirection broken if access is from ACL only
I have an issue with W2K/XP using Folder Redirection to a Samba homes share (or any share for that matter). This is only a problem when access for a user is via an ACE (ACL) and not the traditional file system permissions. So for example (user is cath in this example): [root@gandalf users]# ll -d cath drwxrwx---+ 5 root root 4096 Apr 15 20:40 cath [root@gandalf users]# getfacl cath # file: cath
2015 Sep 24
0
v2.2.19 release candidate released
W dniu 23.09.2015 o 15:30, Timo Sirainen pisze: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.19.rc1.tar.gz.sig > > A lot of changes since v2.2.18, so here's a release candidate first. If no bugs are reported, I'm planning on making the final release sometimes this week. The most interesting new features here
2009 Mar 13
1
lsfit w/ rank-deficient x
Dear R-devel, It seems that lsfit incorrectly reports coefficients when the input matrix 'x' is rank-deficient, see the example below: ## here values of 'b' and 'c' are incorrectly swapped > x <- cbind(a=rnorm(100), b=0, c=rnorm(100)); y <- rnorm(100); lsfit(x, y)$coef Intercept a b c -0.0227787 0.1042860 -0.1729261 0.0000000 Warning
2020 Aug 30
0
Network rebuild advice needed
You have a duplicate RID pool, so the RIDs that it thinks it can allocate are already allocated. dbcheck on Samba 4.5 and later (so should work for your 4.7) can fix that. Run that on the source server locally. Andrew Bartlett On Sat, 2020-08-29 at 17:42 -0700, Peter Pollock wrote: > Tried the join. Failed to find a writeable DC > Tried with --server and gave it the name of one of the
2019 Jan 20
0
auth-worker service failed since recent MariaDB upgrade
Op 20/01/2019 om 15:30 schreef Bogomil Vasilev via dovecot: > Hello Aki, > > This patch seems to have done the trick - hopefully it works fine and > doesn't mask the problem. > From the patch content, I see that it's from 4th of December. > Is there a reason why this hasn't made it yet into upstream? It is still being tested in QA (other stuff came first). It is