similar to: R-alpha: is.vector(.., mode=..) bug (old)

Displaying 20 results from an estimated 10000 matches similar to: "R-alpha: is.vector(.., mode=..) bug (old)"

2010 Sep 03
1
How to use lm() output for systemfit() 'Seemingly unrelated regression'
I am having problem using output of lm() function for further analysing using systemfit package. Basicaly, the problem s following - I generate several formulas using lm() > fo1 <- lm(r98[,2] ~ f98[,1] + f98[,2] + ... + f98[,43]) > fo2 <- lm(r98[,1] ~ f98[,1] + f98[,2] + ... + f98[,43]) and than I want to estimate a general model using package systemfit. > fitsur <-
2005 Jul 31
1
BUG: Standard Time v. DST calculated wrong by Samba Server
FYI, the same bug apears if one mounts the file system using "cifs": -rwxr----- 1 user 2532415 2000-04-02 00:34:50.000000000 -0800 fo1.mp3* -rwxr----- 1 user 3876671 2000-03-12 21:33:20.000000000 -0800 fo2.mp3* Linda W wrote: > Summary: > There appears to be a bug in the "time range" Samba is using on > dates where time is scheduled to "Spring Forward"
2005 Jul 30
0
Samba bug: 1 out of 387 files off by 1 hour (DST/ST bug)
Summary: There appears to be a bug in the "time range" Samba is using on dates where time is scheduled to "Spring Forward" from Standard to Daylight Savings time. Might want to review the code for "Falling back", as well... Details: This started out with my thinking it was an rsync problem, but it appears to be something to do with how samba is exporting the file
2008 Sep 30
1
Quantile Regression for Longitudinal Data. Warning message: In rq.fit.sfn
Hi, I am trying to estimate a quantile regression using panel data. I am trying to use the model that is described in Dr. Koenker's article. So I use the code the that is posted in the following link: http://www.econ.uiuc.edu/~roger/research/panel/rq.fit.panel.R While this code run perfectly, it does not work for my data providing a warning message: In rq.fit.sfn(D, y, rhs = a) : tiny
2004 Jul 27
0
PANIC: internal error; winbind daemon (3.0.4) crashes
Hello, I'm using samba 3.0.4, compiled with Kerberos 1.3.1-7, in an W2k3 ADS environment and Kerberos and the Winbind daemon are used for authentication. While checking a winbindd.log file I saw the following PANIC internal error: winbindd.log ========= [2004/07/21 12:15:00, 1] nsswitch/winbindd_group.c:winbindd_getgroups(1032) user 'root' does not exist [2004/07/21 12:15:00, 1]
2004 Sep 01
0
Issues after upgrade to 3.0.6 from 3.0.4; fixed in 3.0.7?
Hello, I run samba 3.0.4 on a RHL9 server. Samba is a domain member of a W2k3 ADS and I use CUPS as printing mechanism; therefore Samba is compiled with Kerberos 1.3.1-7 and cups-devel. 3.0.4 runs pretty good, printing via CUPS runs well too, only the following messages I see constantly (this flooding my logs) while using 3.0.4: winbindd.log ========= [2004/07/27 16:07:04, 1]
2011 Apr 30
1
More flexible aggregate / eval
Dear list, I would like to do some calculation using different grouping variables. My 'df' looks like this: # Some data set.seed(345) id <- seq(200,400, by=10) ids <- sample(substr(id,1,1)) group1 <- rep(1:3, each=7) group2 <- rep(1:2, c(10,11)) group3 <- rep(1:4, c(5,5,5,6)) df <- data.frame(id, ids, group1, group2, group3) df <- rbind(df, df, df) df$time <-
2020 Jul 02
2
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Thu, Jul 2, 2020 at 11:48 AM Will Deacon <will at kernel.org> wrote: > On Thu, Jul 02, 2020 at 10:32:39AM +0100, Mark Rutland wrote: > > On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > > > -#define read_barrier_depends() __asm__ __volatile__("mb": : :"memory") > > > +#define __smp_load_acquire(p)
2020 Jul 02
2
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Thu, Jul 2, 2020 at 11:48 AM Will Deacon <will at kernel.org> wrote: > On Thu, Jul 02, 2020 at 10:32:39AM +0100, Mark Rutland wrote: > > On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > > > -#define read_barrier_depends() __asm__ __volatile__("mb": : :"memory") > > > +#define __smp_load_acquire(p)
2020 Jul 02
0
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Thu, Jul 02, 2020 at 12:08:41PM +0200, Arnd Bergmann wrote: > On Thu, Jul 2, 2020 at 11:48 AM Will Deacon <will at kernel.org> wrote: > > On Thu, Jul 02, 2020 at 10:32:39AM +0100, Mark Rutland wrote: > > > On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > > > > -#define read_barrier_depends() __asm__ __volatile__("mb": :
2023 Nov 08
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
So, to summarize, the open questions are: (1) Should as.complex(NA_character_) give complex(r=NA_real_, i=0) instead of NA_complex_? (2) Should the first argument in c(NA, x) and c(NA_integer_, x), where typeof(x) == "complex", be promoted to complex(r=NA_real_, i=0) instead of NA_complex_? My opinions: (1) No. The imaginary part of the
2023 Nov 09
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
>>>>> Mikael Jagan >>>>> on Wed, 8 Nov 2023 11:13:18 -0500 writes: > So, to summarize, the open questions are: > (1) Should as.complex(NA_character_) give complex(r=NA_real_, i=0) > instead of NA_complex_? > (2) Should the first argument in c(NA, x) and c(NA_integer_, x), > where typeof(x) == "complex", be promoted
2018 Feb 09
0
[RFC HACK] Make clang hate percpu.h less in 32-bit mode
Neither clang nor GCC like this very much with -m32: long long ret; asm ("movb $5, %0" : "=q" (ret)); However, GCC can tolerate this variant: long long ret; switch (sizeof(ret)) { case 1: asm ("movb $5, %0" : "=q" (ret)); case 8: ; } Clang, on the other hand, won't accept that because it validates the inline asm for the '1' case
2010 Feb 10
3
What is the difference between typeof and storage.mode?
S Programming by Venables and Ripley (2000) says on page 8, "R objects have another way to give information using the function \tttext{typeof}, which often gives the same information as \tttext{storage.mode}." It implies that there are some differences between typeof and storage.mode. However, according to ?typeof and ?storage.mode, it doesn't seem to be so. Could somebody let me
2020 Jul 02
2
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > Rather then relying on the core code to use smp_read_barrier_depends() > as part of the READ_ONCE() definition, instead override __READ_ONCE() > in the Alpha code so that it is treated the same way as > smp_load_acquire(). > > Acked-by: Paul E. McKenney <paulmck at kernel.org> > Signed-off-by: Will Deacon
2020 Jul 02
2
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > Rather then relying on the core code to use smp_read_barrier_depends() > as part of the READ_ONCE() definition, instead override __READ_ONCE() > in the Alpha code so that it is treated the same way as > smp_load_acquire(). > > Acked-by: Paul E. McKenney <paulmck at kernel.org> > Signed-off-by: Will Deacon
2020 Jul 02
0
[PATCH 04/18] alpha: Override READ_ONCE() with barriered implementation
On Thu, Jul 02, 2020 at 10:32:39AM +0100, Mark Rutland wrote: > On Tue, Jun 30, 2020 at 06:37:20PM +0100, Will Deacon wrote: > > -#define read_barrier_depends() __asm__ __volatile__("mb": : :"memory") > > +#define __smp_load_acquire(p) \ > > +({ \ > > + __unqual_scalar_typeof(*p) ___p1 = \ > > + (*(volatile typeof(___p1) *)(p));
1997 Sep 03
1
R-alpha: speed of sort(.) and order(.)
sort() and order() are not quite the same, as "one knows": o order allows breaking ties by more than one argument; o sort allows a 'partial' and 'na.last' argument Still, the following timing (on a `simple' UltraSparc I) suggest that actually two different algorithms are used > N <- 10000 > typeof(x0 <- 1:N) # --- x0 : already sorted --- [1]
2023 Nov 07
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
Thanks Martin. My hang-up was not on what the outcome of as.complex(NA) should be, but rather, how I should read code like c(x, y) generally. Till now, I have thought of it like 'c(x, y)' is c(as(x, typeof(y)), y)` when "type(y) > type(x)". Basically in my mind, "coercion" in R <-> as.<newtype>(.) (or coerceVector() in C). So I tracked down the source
2005 May 10
0
Implementation of the names attribute of attribute lists
Dear all, Internally, the attribute list appears to be implemented as an generic list vector with a names attributes (i.e., the attribute slot in the object's SEXPREC structure would point toward a VECTOR_SEXPREC representing a generic vector). > attributes(c(a=1)) $names [1] "a" > typeof(attributes(c(a=1))) [1] "list" From R, it appears as if the named list had