search for: incoherency

In data OME in MASS I would like to extract the first 5 observations per subject (=ID). So I do library(MASS) OMEsub <- split(OME, OME$ID) OMEsub <- lapply(OMEsub,function(x)x[1:5,]) unsplit(OMEsub, OME$ID) - which results in [[1]] [1] 1 1 1 1 1 [[2]] [1] 30 30 30 30 30 [[3]] [1] low low low low low Levels: N/A high low [[4]] [1] 35 35 40 40 45 [[5]] [1] coherent incoherent coherent

>>>>> Serguei Sokol >>>>> on Wed, 19 Feb 2020 15:21:21 +0100 writes: > Hi, > I was bitten by a little incoherence in dimnames assignment or may be I > missed some point. > Here is the case. If I assign row names via dimnames(a)[[1]], when > nrow(a)=1 then an error is thrown. But if I do the same when nrow(a) > 1 >

Hello, I have a question about function arima.sim I tried to somulate a AR(1) process, with no innovation, no error term. I used this code: library(forecast) e=rnorm(100,mean=0,sd=0) series=arima.sim(model=list(ar=0.75),n=100,innov=e)+20 Then I tried to applicate ti this series auto.arima function: mod1<-auto.arima(series,stepwise=FALSE,trace=TRUE,ic='aicc') The best model returned

somewhat related to a previous discussion [1] on how 'names<-' would sometimes modify its argument in place, and sometimes produce a modified copy without changing the original, here's another example of how it becomes visible to the user when r makes or doesn't make a copy of an object: x = NULL dput(x) # NULL class(x) = 'integer' # error: invalid

...www.tropenklinik.de > > > > -----Ursprüngliche Nachricht----- > Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Rowland Penny > Gesendet: Mittwoch, 15. Juli 2015 17:35 > An: samba at lists.samba.org > Betreff: Re: [Samba] 4.2.2 as AD with 2 DCs: database incoherency > > On 15/07/15 14:31, mathias dufresne wrote: >> Hi all, >> >> I'm having a test AD domain composed with 2 DC, using Sernet's version >> of Samba 4.2.2. >> >> These two DC are Centos 6.6 (dc20) and Debian 7.8 (dc00). >> >> These two are...

On 15/07/15 14:31, mathias dufresne wrote: > Hi all, > > I'm having a test AD domain composed with 2 DC, using Sernet's version of > Samba 4.2.2. > > These two DC are Centos 6.6 (dc20) and Debian 7.8 (dc00). > > These two are using TDB as a backend (as we have no other choice at this > stage of Samba's development). > > *dc20*:~# ldbsearch -H $sam

Am 16.07.2015 um 14:02 schrieb Rowland Penny: > /etc/hosts should be: > > 127.0.0.1 localhost.localdomain localhost uhm no - you want 127.0.0.1 normally resolved to localhost and hence 127.0.0.1 localhost localhost.localdomain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes

...ne creation worked after upgrading to Samba4 4.2.3. I didn't yet filled that zone but I ran: samba-tool ldapcmp ldap://DC00.ad.domain.tld ldap://DC20.ad.domain.tld -Uadministrator on DC00. Just to see if previous errors were also solved after upgrade. Regarding initial issue which was database incoherency I copied /var/lib/samba/private/sam.ldb.d/DC=AD,DC=DOMAIN,DC=TLD from DC20 to DC00 (with both Samba services stopped) to see if this could be achieve and used as quick answer to incoherency issue. The idea was all DC should have the same database, let's push the database (piggy work, often effi...

Hi, I was bitten by a little incoherence in dimnames assignment or may be I missed some point. Here is the case. If I assign row names via dimnames(a)[[1]], when nrow(a)=1 then an error is thrown. But if I do the same when nrow(a) > 1 it's OK. Is one of this case works unexpectedly? Both? Neither? a=as.matrix(1) dimnames(a)[[1]]="a" # error: 'dimnames' must be a list

Hi all, I'm having a test AD domain composed with 2 DC, using Sernet's version of Samba 4.2.2. These two DC are Centos 6.6 (dc20) and Debian 7.8 (dc00). These two are using TDB as a backend (as we have no other choice at this stage of Samba's development). *dc20*:~# ldbsearch -H $sam '(objectclass=group)' dn | tail -3 # returned 27392 records # *27389* entries # 3 referrals

If we change the behavior NULL--[[--assignment from `[[<-`(NULL, 1, "a" ) # gives "a" (*not* a list) to `[[<-`(NULL, 1, "a" ) # gives list("a") then we have more consistency there *and* your bug is fixed too. Of course, in other situations back-compatibility would be broken as well. Would that change the result of L <-

>>>>> Martin Maechler >>>>> on Sat, 22 Feb 2020 20:20:49 +0100 writes: >>>>> William Dunlap >>>>> on Fri, 21 Feb 2020 14:05:49 -0800 writes: >> If we change the behavior NULL--[[--assignment from >> `[[<-`(NULL, 1, "a" ) # gives "a" (*not* a list) >> to >>

...-Ursprüngliche Nachricht----- >>> Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Rowland >>> Penny >>> Gesendet: Mittwoch, 15. Juli 2015 17:35 >>> An: samba at lists.samba.org >>> Betreff: Re: [Samba] 4.2.2 as AD with 2 DCs: database incoherency >>> >>> On 15/07/15 14:31, mathias dufresne wrote: >>> >>>> Hi all, >>>> >>>> I'm having a test AD domain composed with 2 DC, using Sernet's version >>>> of Samba 4.2.2. >>>> >>>> These two DC...

Hello, I'm running a samba 3.0.14a server in production on a fedora core 3 (kernel 2.6.9-1.667smp) with a least 250 clients (XP Pro SP2) (up to 400 sometimes). A few days ago, a problem appeared with a soft that we are using for a long time. (Petit Robert, a french dictionnary). When someone launch the dictionnary, many clients are freezed when they try to access to the "start

Hello, I upgraded to ferret 0.10.10 and I noticed a strange behaviour with queries. Now the queries return strange results. For example, the two following queries return the same results: familynames|firstnames:andre familynames|firstnames:andr Another example, the first query returns a correct result + incoherent results, the second query returns only the correct result:

Hi all, I tried "samba-tool ldapcmp" several times to solve this issue, without success. On DC acting as full FSMO: dc20:~# samba-tool ldapcmp ldap://dc00.ad.dgfip.lan ldap://dc20.ad.dgfip.lan domain ERROR(ldb): uncaught exception - ldb_wait: Time limit exceeded (3) File "/usr/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175, in _run return

On Thu, Dec 31, 2015 at 09:08:22PM +0200, Michael S. Tsirkin wrote: > +#ifdef CONFIG_SMP > +#define fence() metag_fence() > +#else > +#define fence() do { } while (0) > #endif James, it strikes me as odd that fence() is a no-op instead of a barrier() for UP, can you verify/explain?

On Thu, Dec 31, 2015 at 09:08:22PM +0200, Michael S. Tsirkin wrote: > +#ifdef CONFIG_SMP > +#define fence() metag_fence() > +#else > +#define fence() do { } while (0) > #endif James, it strikes me as odd that fence() is a no-op instead of a barrier() for UP, can you verify/explain?

...> #endif > > James, it strikes me as odd that fence() is a no-op instead of a > barrier() for UP, can you verify/explain? fence() is an unfortunate workaround for a specific issue on a certain SoC, where writes from different hw threads get reordered outside of the core, resulting in incoherency between RAM and cache. It has slightly different semantics to the normal SMP barriers, since I was assured it is required before a write rather than after it. Here's the comment: > This is needed before a write to shared memory in a critical section, > to prevent external reordering of...

i wonder about the following examples showing incoherence in how type conversions are done in r: x = TRUE x[2] = as.raw(1) # Error in x[2] = as.raw(1) : # incompatible types (from raw to logical) in subassignment type fix it seems that there is an attempt to coerce the raw value to logical here, which fails, even though as.logical(as.raw(1)) # TRUE likewise, x[2]