search for: tre

glm(A~B+C+D+E+F,family = binomial(link = "logit"),data=tre,na.action=na.omit) Error in `contrasts<-`(`*tmp*`, value = "contr.treatment") : contrasts can be applied only to factors with 2 or more levels however, glm(A~B+C+D+E,family = binomial(link = "logit"),data=tre,na.action=na.omit) runs fine glm(A~B+C+D+F,family = binomial...

...box: samba-3.0.7-5 openldap2-2.2.15-5 smbldap-tools-0.8.4-1 So when I try to logon with a defaul user (winnt) I receive C0000001 error code (unsuficient auth). Here the logs for this request: #/var/log /messages Feb 11 19:59:36 glasgow slapd[6674]: conn=583 op=4 SRCH base="dc=labredes,dc=tre-sc,dc=gov,dc=br" scope=2 deref=0 filter="(&(uid=andre)(objectClass=sambaSamAccount))" Feb 11 19:59:36 glasgow slapd[6674]: conn=583 op=4 SRCH attr=uid uidNumber gidNumber homeDirectory sambaPwdLastSet sambaPwdCanChange sambaPwdMustChange sambaLogonTime sambaLogoffTime sambaKic...

Hi all, I'm on Ubuntu 18.04, running R-4.0.0 which I compiled from source, and using valgrind I am always seeing the following message. Does anybody else see that? Is that a known false positive? Any ideas how to fix/suppress? Seems related to TRE, do I need to upgrade that? (base) tdhock at maude-MacBookPro:~/R/binsegRcpp$ R --vanilla -d valgrind -e 'extSoftVersion()' ==9565== Memcheck, a memory error detector ==9565== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==9565== Using Valgrind-3.13.0 and LibVEX; rer...

...24 09:37, Ivan Krylov via R-devel wrote: >> ? Sun, 28 Jul 2024 20:02:21 -0400 >> Duncan Murdoch <murdoch.duncan at gmail.com> ?????: >> >>> gsub("^([0-9]{,5}).*","\\1","123456789") >>> [1] "123456" >> This is in TRE itself: for "^([0-9]{,1})" tre_regexecb returns {.rm_so >> = 0, .rm_eo = 1}, matching "1", but for "^([0-9]{,2})" and above it >> returns an off-by-one result, {.rm_so = 0, .rm_eo = 3}. >> >> Compiling with TRE_DEBUG, I see it parsed correctly:...

Hello the list, As a simple example: > rm(list = ls())> setClass("tre", representation(x="numeric"))> setMethod("show", "tre", def = function(object) cat(object@x))[1] "show"> setMethod("summary", "tre", def = function(object) cat("This is a tre of value ", object@x, "\n"))Crea...

...it must be present. X{,4} is interpreted as X{0,4}. In earlier versions such a sequence was not interpreted as a quantifier. Other regular expression engines may behave either way." And the changelog: "29. Perl 5.34.0 changed the meaning of (for example) {,3} which did not used to be treated as a quantifier. Now it is interpreted as {0,3} and PCRE2 has changed to match. Note that {,} is still not a quantifier." Sadly the previous behavior was also documented in pcre2pattern.3: "For example, {,6} is not a quantifier, but a literal string of four characters" I'...

...inhdizzo at gmail.com> >>>>> on Thu, 8 Oct 2015 20:21:32 -0700 writes: > Ahh, sorry for not googling the error message. Found > [this](http://r.789695.n4.nabble.com/Error-compiling-R-2-10-1-on-AIX-td1017862.html) > post that suggests modifying /src/extra/tre/tre-internal.h > (https://r-forge.r-project.org/scm/viewvc.php/patches/aix_R210_tre.patch?view=markup&root=aix) > for AIX 64 bit. > Is it possible to add this information to the AIX section > of the R-admin manual? Thanks. Actually, I think we (R Core) should just...

...s old Stack Overflow question > > https://stackoverflow.com/questions/19765610/when-does-locale-affect-rs-regular-expressions > > > I was wondering why this is TRUE: > > Sys.setlocale("LC_ALL", "et_EE") > grepl("[A-Z]", "T") > > TRE's documentation at > <https://laurikari.net/tre/documentation/regex-syntax/> says that a > range "is shorthand for the full range of characters between those two > [endpoints] (inclusive) in the collating sequence". > > Yet, T is *not* between A and Z in the Es...

Inspired by this old Stack Overflow question https://stackoverflow.com/questions/19765610/when-does-locale-affect-rs-regular-expressions I was wondering why this is TRUE: Sys.setlocale("LC_ALL", "et_EE") grepl("[A-Z]", "T") TRE's documentation at <https://laurikari.net/tre/documentation/regex-syntax/> says that a range "is shorthand for the full range of characters between those two [endpoints] (inclusive) in the collating sequence". Yet, T is *not* between A and Z in the Estonian collating sequenc...

...ub("a{2-}", "") gsub("a{2-}", "") EXAMPLES: > sessionInfo() R version 2.11.1 Patched (2010-09-16 r52949) Platform: i386-pc-mingw32 (32-bit) ... > regexpr("a{2-}", "") Assertion failed: iter->max == -1 || iter->max == 1, file tre-compile.c, line 1825 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. > sessionInfo() R version 2.12.0 Under development (unstable) (2010-09-14 r52910) Platform: i386-pc-mingw32/i386 (32-bit) .....

...ub("a{2-}", "") gsub("a{2-}", "") EXAMPLES: > sessionInfo() R version 2.11.1 Patched (2010-09-16 r52949) Platform: i386-pc-mingw32 (32-bit) ... > regexpr("a{2-}", "") Assertion failed: iter->max == -1 || iter->max == 1, file tre-compile.c, line 1825 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. > sessionInfo() R version 2.12.0 Under development (unstable) (2010-09-14 r52910) Platform: i386-pc-mingw32/i386 (32-bit) .....

...roblems are self-inflicted. But would be good to know what environment you are using. Thanks for looking - and finding!!! Michael >> On 01 Jan 2016, at 22:06 , Simon Urbanek<simon.urbanek at r-project.org> wrote: >> >> Ok, found the problem - on platforms that support it TRE uses wint_t (from wchar.h) as its type for characters (tre_cint_t) which on AIX is *signed* int. TRE uses liberally conversions between int and tre_cint_t apparently assuming that the latter is unsigned so conversions back to int are suitable for comparisons etc. On other platforms wint_t is unsign...

...er)s) did you use: xlc and xlfortran, or > gcc/gfortran? > > I have made some changes to configure(.ac) so maybe my problems are > self-inflicted. But would be good to know what environment you are using. > Using the dist, plus the following change: diff -ru R-3.2.3.dist/src/extra/tre/tre-internal.h R-3.2.3.1/src/extra/tre/tre-internal.h --- R-3.2.3.dist/src/extra/tre/tre-internal.h 2014-06-13 22:15:07.000000000 +0000 +++ R-3.2.3.1/src/extra/tre/tre-internal.h 2016-01-03 16:08:31.000000000 +0000 @@ -47,7 +47,7 @@ #ifdef TRE_WCHAR /* Wide characters. */ - typedef...

It is known, with a known workaround, see e.g. https://www.stats.ox.ac.uk/pub/bdr/memtests/README.txt . Set suppressions in ~/.valgrindrc, e.g. the CRAN check machine has --suppressions=/data/blackswan/ripley/wcsrtombs.supp It is an issue in your OS (glibc), not TRE nor R. On 10/06/2020 00:21, Toby Hocking wrote: > Hi all, > > I'm on Ubuntu 18.04, running R-4.0.0 which I compiled from source, and > using valgrind I am always seeing the following message. Does anybody > else see that? Is that a known false positive? Any ideas how to > fi...

Ok, found the problem - on platforms that support it TRE uses wint_t (from wchar.h) as its type for characters (tre_cint_t) which on AIX is *signed* int. TRE uses liberally conversions between int and tre_cint_t apparently assuming that the latter is unsigned so conversions back to int are suitable for comparisons etc. On other platforms wint_t is unsign...

This seems to be a problem that goes back a long time - and I hope someone who understands what tre is suppossed to be doing will look at this. A short history of other people who have reported on this on different versions of AIX. I shall only add that I get the same results on AIX 5.3 TL7, AIX 6.1 TL9 and AIX 7.1 TL3. Basically, with settings that work for AIX and 32-bit - the only changes...

...question about this result: > gsub("^([0-9]{,5}).*","\\1","123456789") [1] "123456" The OP expected "12345" as the result. Several points were raised: - The R docs don't mention the case of {,5} for the default perl = FALSE which uses TRE. - perl = TRUE gives the OP's expected result of "12345". - perl = TRUE does *not* give the documented result on at least one system (which is "123456789", because "{,5}" is documented to not be a quantifier, so it should only match the literal string "{...

Hello, I have a question about margins when plotting an unrooted tree (type="unrooted") with the 'ape' package ver. 1.7. When I plot an unrooted tree with: no.margin=TRUE it seems that the margins are still there. It appears to be only when type="unrooted". I'm plotting multiple plots using layout() and would like to be able to get...

The issue seems related to R bug report 15012: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15012 As mentioned in the comments there, a pull request to the TRE library has recently been made, but I don't know about its status. Daniel ________________________________________ Von: R-devel <r-devel-bounces at r-project.org> im Auftrag von Tomas Kalibera <tomas.kalibera at gmail.com> Gesendet: Donnerstag, 17. August 2017 10:14 An: r-devel at...

On 2015-12-30 09:58, Michael Felt wrote: > On 2015-12-29 11:02, Michael Felt wrote: >> This seems to be a problem that goes back a long time - and I hope >> someone who understands what tre is suppossed to be doing will look >> at this. >> >> A short history of other people who have reported on this on >> different versions of AIX. I shall only add that I get the same >> results on AIX 5.3 TL7, AIX 6.1 TL9 and AIX 7.1 TL3. >> >> Basically,...