Re: [R] Small R documentation bug in ?anyDuplicated

>>>>> Bert Gunter >>>>> on Sun, 6 Dec 2020 08:23:44 -0800 writes: > All: I did not want to bother R folks for an R Bugzilla > account, so I'll just note what appears to be a > documentation bug here > In R version

[R] Small R documentation bug in ?anyDuplicated

All: I did not want to bother R folks for an R Bugzilla account, so I'll just note what appears to be a documentation bug here In R version 4.0.3, ?anyDuplicated says: "anyDuplicated(.) is a “generalized” more efficient shortcut for any(duplicated(.)). However, anyDuplicated returns an in

[R] nlme::gls potential bug

Hi there, I have been using the nlme::gls package created in R to fit a pretty simple model (linear with AR error) y(t) = beta*x(t) + e(t)              where e(t) ~ rho*e(t-1) + Z(t)        and Z(t)~ N(0,sig^2) I call the R routine glsObj <- nlme::gls(y ~ x -1, data=data, correlation =

Re: [R] Mac-specific encoding bug

Interesting! The odd thing is it works perfectly well on Linux platforms, at least - I guess it must be something to do with the Mac locales. Thanks! On Sun, May 7, 2017 at 1:51 PM, peter dalgaard wrote: > >> On 7 May 2017, at 08:36 , Oliver Keyes wrote:

Re: [R] Mac-specific encoding bug

> On 7 May 2017, at 08:36 , Oliver Keyes wrote: > > Hey all, > > I've ran into a weird quirk on Mac platforms, which you can read fully > at https://github.com/Ironholds/urltools/issues/70 > > The long and the short of it is that one specific codepoint - \u04cf - > does

[R] Mac-specific encoding bug

Hey all, I've ran into a weird quirk on Mac platforms, which you can read fully at https://github.com/Ironholds/urltools/issues/70 The long and the short of it is that one specific codepoint - \u04cf - does not print in a UTF-8-y way by default, except when run through cat(). Compare, for

Re: [R] Is this a bug in quantmod::OpCl?

On Fri, Apr 8, 2016 at 10:51 AM, James Hirschorn wrote: > > > On 04/06/2016 07:58 PM, Joshua Ulrich wrote: >> >> On Tue, Apr 5, 2016 at 9:17 PM, James Hirschorn >> wrote: >>> >>> OpCl works on xts objects but not on quantmod.OHLC objects.

Re: [R] Is this a bug in quantmod::OpCl?

On Tue, Apr 5, 2016 at 9:17 PM, James Hirschorn wrote: > > OpCl works on xts objects but not on quantmod.OHLC objects. Is this a bug? > Thanks for the minimal, reproducible example. Looks like a bug. There's no as.quantmod.OHLC.xts method, so the zoo method is

[R] Is this a bug in quantmod::OpCl?

OpCl works on xts objects but not on quantmod.OHLC objects. Is this a bug? Example error: x.Date <- as.Date("2003-02-01") + c(1, 3, 7, 9, 14) - 1 set.seed(1) x <- zoo(matrix(runif(20, 0, 1), nrow=5, ncol=4), x.Date) q <- as.quantmod.OHLC(x,c("Open","High","Low","Close")) # error OpCl(q) #>

[R] 答复: the bug of function base::order

Oh, Thank you! I made a stupid mistake! -邮件原件- 发件人: ONKELINX, Thierry [mailto:thierry.onkel...@inbo.be] 发送时间: 2014年11月10日 16:03 收件人: 岳�S; r-help@r-project.org 主题: RE: [R] the bug of function base::order No that is not a bug. You are confusing order() with sort(). Please do read

Re: [R] Is this a bug or am I making a mistake?

-project.org] On Behalf | Of Walter Anderson | Sent: Monday, January 06, 2014 11:17 AM | To: Sarah Goslee | Cc: R Help | Subject: Re: [R] Is this a bug or am I making a mistake? | | On 01/06/2014 11:14 AM, Sarah Goslee wrote: | Hi Walter, | | I can't reproduce your results. Please

Re: [R] Is this a bug or am I making a mistake?

Dunlap TIBCO Software wdunlap tibco.com -Original Message- From: Patrick Connolly [mailto:p_conno...@slingshot.co.nz] Sent: Sunday, January 12, 2014 12:56 AM To: William Dunlap Cc: Walter Anderson; Sarah Goslee; R Help Subject: Re: [R] Is this a bug or am I making a mistake? On Mon

Re: [R] Is this a bug or am I making a mistake?

On Jan 6, 2014, at 11:16 AM, Walter Anderson wrote: On 01/06/2014 11:14 AM, Sarah Goslee wrote: Hi Walter, I can't reproduce your results. Please provide some data that demonstrates the problem. http://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example

[R] Is this a bug or am I making a mistake?

I have a data frame that I am extracting some records from and noticed the following issue I originally used tmp - subset(dd, dd$EVYEAR==2012 dd$EVMONTH=='02') and noticed that I wasn't ending up with all of the records I should have; however, when I used tmp - dd[dd$EVYEAR==2012

Re: [R] Is this a bug or am I making a mistake?

Hi Walter, I can't reproduce your results. Please provide some data that demonstrates the problem. http://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example subset() and [ differ in their handling of NA values, and you don't need the dd$ in the arguments to subset().

Re: [R] Is this a bug or am I making a mistake?

On 01/06/2014 11:14 AM, Sarah Goslee wrote: Hi Walter, I can't reproduce your results. Please provide some data that demonstrates the problem. http://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example subset() and [ differ in their handling of NA values, and you

Re: [R] Is this a bug or am I making a mistake?

, TIBCO Software wdunlap tibco.com -Original Message- From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On Behalf Of Walter Anderson Sent: Monday, January 06, 2014 11:17 AM To: Sarah Goslee Cc: R Help Subject: Re: [R] Is this a bug or am I making a mistake

[R] freetype 2.5.1 and mono 3.2.5 (was Re: new bugs and new bundles Re: [Rd] R/Sweave/cairo/freetype bug fix.)

The freetype people fixed the 2nd set of issues with system fonts shipped with Mac OS X, and released 2.5.1 almost immediately after that. So there are new bundles under http://sourceforge.net/projects/outmodedbonsai/files/R/ . Just a reminder that the official R binaries for windows/mac OS X

[R] new bugs and new bundles Re: [Rd] R/Sweave/cairo/freetype bug fix.

The most up-to-date version of freetype (2.5.0.1) have problems with at least two of the system fonts shipped with Mac OS X. So the p1 in 2.5.0.1p1: cairo-1.12.16+freetype-2.5.0.1p1_macosx.tar.bz2 cairo-1.12.16+freetype-2.5.0.1p1_windows.tar.bz2 means 2.5.0.1 +

[R] Nulls being coerced : Bug or design?

Hello, Consider the following transcript x=NULL x$date=10 x $date [1] 10 or x=NULL x[10]=10 x [1] NA NA NA NA NA NA NA NA NA 10 Wouldn't one expect that x remain NULL despite the further additions (i.e the x$date, x[10]) etc? Is coercing appropriate here? Cheers Saptarshi

Re: [R] Nulls being coerced : Bug or design?

Well, feel free to make up any semantics that you like for a language you write, but R already has its own and tells you what to expect: From ?NULL: NULL can be indexed (see Extract) in just about any syntactically legal way: whether is makes sense or not, the result is always NULL. Objects with

Re: [R] Nulls being coerced : Bug or design?

On Jun 21, 2013, at 1:21 PM, Saptarshi Guha wrote: Hello, Consider the following transcript x=NULL x$date=10 x $date [1] 10 or x=NULL x[10]=10 x [1] NA NA NA NA NA NA NA NA NA 10 Wouldn't one expect that x remain NULL despite the further additions (i.e the x$date,

Re: [R] new window cairo bundle Re: [Rd] R/Sweave/cairo/freetype bug fix.

Freetype 2.4.12 was released in early May. Just so that we are clear that this is a freetype bug which affects R's use of Cairo (among other things). So there are updated bundles, and also bundles for Mac OS X as well, for both a patched 2.4.11 and 2.4.12 proper. The accompanying *.txt has a

[R] new window cairo bundle Re: [Rd] R/Sweave/cairo/freetype bug fix.

--- On Mon, 1/4/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: --- On Sat, 30/3/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: ... was committed to freetype in January and will form the next release (2.4.12). It is perhaps worth repeating the quote:  'The official R

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

On Apr 1, 2013, at 5:18 AM, Hin-Tak Leung wrote: --- On Sat, 30/3/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: ... was committed to freetype in January and will form the next release (2.4.12). It is perhaps worth repeating the quote: 'The official R binaries for windows ...

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

--- On Sat, 30/3/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: ... was committed to freetype in January and will form the next release (2.4.12). It is perhaps worth repeating the quote: 'The official R binaries for windows ... are compiled against static libraries of cairo 1.10.2 ...

[R] R/Sweave/cairo/freetype bug fix.

The problem was first seen with R/Sweave (#c0) then reproduced directly with cairo (#c10) and was eventually traced to freetype. The 5-part bug fix: 610ee58e07090ead529849b2a454bb6c503b4995 da11e5e7647b668dee46fd0418ea5ecbc33ae3b2 e1a2ac1900f2f16ec48fb4840a6b7965a8373c2b

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

Huh? This is utterly incomprehensible without reading the redhat bugzilla, and even after reading, I'm not sure what the issue is. Something with bold Chinese fonts in X11, but maybe also affecting Latin fonts, ? Please explain yourself. -pd On Mar 30, 2013, at 09:25 , Hin-Tak Leung

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

Perhaps that's too much details. There is (will be) a new freetype because of cairo's unanticipated usage (which R uses, among other cairo users). Most people should upgrade or request an upgrade eventually, when they are comfortable. --- On Sat, 30/3/13, peter dalgaard pda...@gmail.com wrote:

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

On Mar 30, 2013, at 9:24 AM, Hin-Tak Leung wrote: Perhaps that's too much details. There is (will be) a new freetype because of cairo's unanticipated usage (which R uses, among other cairo users). Most people should upgrade or request an upgrade eventually, when they are comfortable.

Re: [R] [Rd] R/Sweave/cairo/freetype bug fix.

... was committed to freetype in January and will form the next release (2.4.12). -- On Sat, Mar 30, 2013 18:54 GMT Simon Urbanek wrote: On Mar 30, 2013, at 9:24 AM, Hin-Tak Leung wrote: Perhaps that's too much details. There is (will be) a new freetype because

Re: [R] BRugs has a bug to use OpenBUGS_PATH

to use OpenBUGS/BRugs in a portable way in windows, so I set the environment variable OpenBUGS_PATH to tell BRugs the path to OpenBugs. But the R library BRugs is still failed to be loaded. I looked in the BRugs' source code, and found that there is a bug in the BRugs R windows findOpenBUGS.R file

[R] BRugs has a bug to use OpenBUGS_PATH

OpenBUGS_PATH to tell BRugs the path to OpenBugs. But the R library BRugs is still failed to be loaded. I looked in the BRugs' source code, and found that there is a bug in the BRugs R windows findOpenBUGS.R file. It contains the function definition of findOpenBUGS. In line 38 version.inst - NA should

Re: [R] BRugs has a bug to use OpenBUGS_PATH

. But the R library BRugs is still failed to be loaded. I looked in the BRugs' source code, and found that there is a bug in the BRugs R windows findOpenBUGS.R file. It contains the function definition of findOpenBUGS. In line 38 version.inst - NA should be version.full - NA. Otherwise

[R] list files - unix bug?

Hi, when I call the function list.files() it also lists directories, although the parameter include.dirs is set to FALSE by default. The function also lists directories when the parameter include.dirs is explicitly set to FALSE list.files(include.dirs=FALSE). I have tested this also on a mac os -

Re: [R] list files - unix bug?

On Aug 3, 2012, at 10:50 , Simon Schafferer wrote: Hi, when I call the function list.files() it also lists directories, although the parameter include.dirs is set to FALSE by default. The function also lists directories when the parameter include.dirs is explicitly set to FALSE

Re: [R] list files - unix bug?

Simon Schafferer wrote Hi, when I call the function list.files() it also lists directories, although the parameter include.dirs is set to FALSE by default. The function also lists directories when the parameter include.dirs is explicitly set to FALSE list.files(include.dirs=FALSE). I

[R] Is this a bug for my fault?

Dear sir/madam, I tried to recode some complex multiple variables and run into a problem that r can change only some column that I want to change. I can reproduce the problem with this idfortest - c(6,23,46,63,200,238,297,321,336,364,386,392,414,434,441) id - seq(1:500) id[id==idfortest] the

Re: [R] Is this a bug for my fault?

you probably want to use %in%: idfortest - c(6,23,46,63,200,238,297,321,336,364,386,392,414,434,441) id - seq(1:500) id[id %in% idfortest] [1] 6 23 46 63 200 238 297 321 336 364 386 392 414 434 441 take a look at what 'id == idfortest' gives; study up on the recycling of arguments. On

Re: [R] Is this a bug for my fault?

On Aug 18, 2011, at 5:52 AM, Rut S wrote: Dear sir/madam, I tried to recode some complex multiple variables and run into a problem that r can change only some column that I want to change. I can reproduce the problem with this idfortest -

Re: [R] Is this a bug for my fault?

On Thu, Aug 18, 2011 at 04:52:58PM +0700, Rut S wrote: I tried to recode some complex multiple variables and run into a problem that r can change only some column that I want to change. I can reproduce the problem with this idfortest -

Re: [R] is this a bug?

the Romans ever done for us? ~~ From: Brian Diggs dig...@ohsu.edu To: R-help@r-project.org Sent: Fri, June 17, 2011 11:58:44 PM Subject: Re: [R] is this a bug? On 6/17/2011 2:24 PM, (Ted

Re: [R] is this a bug?

? ~~ From: Brian Diggs dig...@ohsu.edu To: R-help@r-project.org Sent: Fri, June 17, 2011 11:58:44 PM Subject: Re: [R] is this a bug? On 6/17/2011 2:24 PM, (Ted Harding) wrote: And the extra twist in the tale is exemplified by this mini

Re: [R] is this a bug?

-Original Message- From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On Behalf Of Albert-Jan Roskam Sent: Saturday, June 18, 2011 2:44 AM To: Brian Diggs; R-help@r-project.org Subject: Re: [R] is this a bug? Thanks a lot to all who responded

[R] is this a bug?

Hello, Is the following a bug? I always thought that df$varname - does the same as df[varname] - df - data.frame(weight=round(runif(10, 10, 100)), sex=round(runif(100, 0, 1))) df$pct - df[weight] / ave(df[weight], df[sex], FUN=sum)*100 names(df) [1] weight sexpct ### -- ok

Re: [R] is this a bug?

Sent: Friday, June 17, 2011 1:49 PM To: R Mailing List Subject: [R] is this a bug? Hello, Is the following a bug? I always thought that df$varname - does the same as df[varname] - df - data.frame(weight=round(runif(10, 10, 100)), sex=round(runif(100, 0, 1))) df$pct - df[weight

Re: [R] is this a bug?

[mailto:r-help-boun...@r-project.org] On Behalf Of Albert-Jan Roskam Sent: Friday, June 17, 2011 1:49 PM To: R Mailing List Subject: [R] is this a bug? Hello, Is the following a bug? I always thought that df$varname - does the same as df[varname] - df - data.frame(weight=round

Re: [R] is this a bug?

in that data.frame. Bill Dunlap Spotfire, TIBCO Software wdunlap tibco.com -Original Message- From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On Behalf Of Albert-Jan Roskam Sent: Friday, June 17, 2011 1:49 PM To: R Mailing List Subject: [R] is this a bug? Hello

Re: [R] Removing elements ..., NO bug in which() function

RK == Rumen Kostadinov rkost...@gmail.com on Sun, 13 Feb 2011 12:46:52 -0500 writes: RK Thanks Sarah, RK Yes, the function behaves Exactly as documented: RK check this out: a = c(1,2,3,4,5) a[which(a!=6)] RK [1] 1 2 3 4 5 a[!which(a==6)] RK numeric(0)

Re: [R] Removing elements ..., NO bug in which() function

On Wed, Feb 23, 2011 at 1:02 PM, Martin Maechler maech...@stat.math.ethz.ch wrote: RK == Rumen Kostadinov rkost...@gmail.com     on Sun, 13 Feb 2011 12:46:52 -0500 writes:    RK Thanks Sarah,    RK Yes, the function behaves Exactly as documented:    RK check this out:     a = c(1,2,3,4,5)

Re: [R] perhaps regular expression bug with | sign ??

William Dunlap wrote: sub(x='|t|',pattern = '\|t',replacement='zz') [1] zz|t| Warning messages: 1: '\|' is an unrecognized escape in a character string 2: unrecognized escape removed from \|t How can \| be an unrecognized escape? This flatly contradicts help('regex'), It would

[R] perhaps regular expression bug with | sign ??

Here is my interaction with R: sub(x='|t|',pattern = '|t',replacement='zz') [1] zz|t| So I say to myself Clearly the | signs need to be escaped, so let's try this sub(x='|t|',pattern = '\|t',replacement='zz') [1] zz|t| Warning messages: 1: '\|' is an unrecognized escape in a character string

Re: [R] perhaps regular expression bug with | sign ??

you need to escape it (twice): sub(x='|t|',pattern = '\\|t',replacement='zz') [1] zz| On Fri, Apr 9, 2010 at 4:35 PM, David.Epstein david.epst...@warwick.ac.ukwrote: Here is my interaction with R: sub(x='|t|',pattern = '|t',replacement='zz') [1] zz|t| So I say to myself Clearly the |

Re: [R] perhaps regular expression bug with | sign ??

Try this: sub(x='|t|',pattern = '\\|t',replacement='zz') On Fri, Apr 9, 2010 at 5:35 PM, David.Epstein david.epst...@warwick.ac.uk wrote: Here is my interaction with R: sub(x='|t|',pattern = '|t',replacement='zz') [1] zz|t| So I say to myself Clearly the | signs need to be escaped, so

Re: [R] perhaps regular expression bug with | sign ??

David - Here's the last paragraph of the Details section of the regex help page: Patterns are described here as they would be printed by ‘cat’: (_do remember that backslashes need to be doubled when entering R character strings_, e.g. from the keyboard). You can get around this

Re: [R] perhaps regular expression bug with | sign ??

-Original Message- From: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] On Behalf Of David.Epstein Sent: Friday, April 09, 2010 1:36 PM To: r-help@r-project.org Subject: [R] perhaps regular expression bug with | sign ?? Here is my interaction with R: sub(x

[R] Is this a bug (or a feature) in hist(x)$density ??

Hi all, A friend send me a question on why does this: x-rpois(100,1) sum( hist(x)$density ) Gives out 2 I tried this: sum( hist(x, freq =T)$density ) It didn't help. Then he came back with the following insight: # with breaks b-c(0,0.9,1:8) sum(hist(x,breaks=b)$density) # Much more then 2

Re: [R] Is this a bug (or a feature) in hist(x)$density ??

On Mar 13, 2010, at 3:39 PM, Tal Galili wrote: Hi all, A friend send me a question on why does this: x-rpois(100,1) sum( hist(x)$density ) Gives out 2 Yes. And... hist(x)$breaks [1] 0.0 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 I tried this: sum( hist(x, freq =T)$density ) It didn't help.

Re: [R] Is this a bug (or a feature) in hist(x)$density ??

Hi Tal, basically, by summing over the (pointwise) density, you are approximating the integral over the density (which should be around 1) - but to really do a rectangular approximation, you will of course need to multiply each function value by the width of the corresponding rectangle. I'd

Re: [R] Is this a bug (or a feature) in hist(x)$density ??

Thanks David and Stephan, David's reply was very helpful since I now realize how I made in my head the (wrong) assumption that the hist would automatically produce rectangular bars with the width of 1 (since the distribution is a discrete one). The call: hist(x)$breaks Helped to bring me back to

Re: [R] cut.POSIXt misconception/feature/bug?

On 3/10/2010 11:26 PM, Petr PIKAL wrote: Hi Thanks for clarification. Actually I knew that with first case I get some data with NAs at the beginning and at the end. Maybe my English is not good enough to understand that to get vector of dates split to several chunks I need to put also

Re: [R] cut.POSIXt misconception/feature/bug?

On 3/11/2010 11:52 AM, Brian Diggs wrote: I've included a patch against cut.POSIXt.Rd with these proposed changes. Apparently the patch didn't make it through, so I'm just pasting it below. -- Brian Diggs, Ph.D. Senior Research Associate, Department of Surgery, Oregon Health Science

[R] cut.POSIXt misconception/feature/bug?

Dear all recently I tried to split vector of dates according to some particular date to 2 (more) chunks, but I was not able to perform correct setting. When I want split to 3 chunks it partially works however from help page I supposed to get result without NA. Details: Using both ‘right

Re: [R] cut.POSIXt misconception/feature/bug?

In the first case you did not look far enough into the data: dat - seq(c(ISOdate(2000,3,20)), by = day, length.out = 60) br-dat[c(23, 42)] cut(dat, breaks=br, right=T, include.lowest=T) [1] NANANA NANANA [7] NANA

Re: [R] cut.POSIXt misconception/feature/bug?

On 3/10/2010 1:01 AM, Petr PIKAL wrote: Dear all recently I tried to split vector of dates according to some particular date to 2 (more) chunks, but I was not able to perform correct setting. When I want split to 3 chunks it partially works however from help page I supposed to get result

Re: [R] cut.POSIXt misconception/feature/bug?

Hi Thanks for clarification. Actually I knew that with first case I get some data with NAs at the beginning and at the end. Maybe my English is not good enough to understand that to get vector of dates split to several chunks I need to put also end date and last date to get the whole vector.

Re: [R] cut.POSIXt misconception/feature/bug?

Thanks You are second who responded. In my previous mail I suggested slight modification for cut.POSIXt help page to help those who do not use this too often to avoid this trap. Regards Petr Brian Diggs dig...@ohsu.edu napsal dne 10.03.2010 20:47:49: On 3/10/2010 1:01 AM, Petr PIKAL wrote:

[R] Is this a bug? (layout and par)

Dear R users, I think I have spotted a bug in R, but as I am not sure, I first post it to you. Here is a minimal working example: default - par(no.readonly=TRUE); par(font=1, adj=0.5, cex=1, cex.lab=1, cex.axis=0.5, font.axis=2, lend=2, family=Times, omi=c(0, 0, 0, 0)) layout(mat=matrix(data

Re: [R] Is this a bug? (layout and par)

On 2010-02-15 7:06, Martin Ivanov wrote: Dear R users, I think I have spotted a bug in R, but as I am not sure, I first post it to you. Here is a minimal working example: default- par(no.readonly=TRUE); par(font=1, adj=0.5, cex=1, cex.lab=1, cex.axis=0.5, font.axis=2, lend=2, family=Times

[R] randomForest: impact of bug fixed in version 4.5-13

The NEWS of the randomForest R library mention that version 4.5-13 fixed a bug in predict.randomForest() when newdata is a matrix with no rownames. I think it corresponds to the difference in files predict.randomForest.R which is the new line if (is.null(rn)) rn - keep As I've been using version

[R] Possible command line bug.

the startup message. It appears as if I can call either --slave or --quiet, but both together doesn't work. (Just the slave option seems used.) Am I missing something or is this a bug? -N __ R-help@r-project.org mailing list https://stat.ethz.ch

[R] Problem with dist (bug?)

Dear list, using package proxy. In one situation, the dissimilarity between two vectors based on method=correlation returns a value of 1.9. That should not happen, should it? The correlation is normally the cos() of the angle between the two vectors That dissimilarity Any clue?

Re: [R] Problem with dist (bug?)

Dear list, here is the code that generates the problem: library(proxy) scot-read.csv(scot.csv,header=TRUE) scot24_climate-scot24[,1105:1109] # Scotland dist_scot24_climate- dist(scot24_climate,method=correlation,diag=TRUE,upper=TRUE) max(dist_scot24_climate) is 1.9. I do not think it should

[R] Is this a bug?

This programme for(T in 1:3){ for(j in 1:(5-1)){ for(k in (j+1):5){ for(l in (j+2):5){ print(paste(1 JKL:, j,k,l,sep= )) } } } } Prints out (among other things) [1] 1 JKL: 4 5 6 That is for(l in (j+2):5) sets l to 6 one more than the upper limit. cheers Worik

Re: [R] Is this a bug?

Answer: No. On Tue, 1 Sep 2009, Worik R wrote: This programme for(T in 1:3){ for(j in 1:(5-1)){ for(k in (j+1):5){ for(l in (j+2):5){ print(paste(1 JKL:, j,k,l,sep= )) } } } } Prints out (among other things) [1] 1 JKL: 4 5 6 That is for(l in (j+2):5) sets l to 6 one

Re: [R] Is this a bug?

On Aug 31, 2009, at 8:31 PM, Worik R wrote: This programme for(T in 1:3){ for(j in 1:(5-1)){ for(k in (j+1):5){ for(l in (j+2):5){ print(paste(1 JKL:, j,k,l,sep= )) } } } } Prints out (among other things) [1] 1 JKL: 4 5 6 That is for(l in (j+2):5) sets l to 6 one

Re: [R] ggsave to .png bug in ggplot2 (?)

Chris Friedl wrote: Text is really small and legend boxes are huge in this plot when saved to .png with ggsave. Plot is correct (i.e. looks the same as the screen) when saved with dev.print. Saving to .pdf with ggsave give the correct output. You are not alone. Things like this always

Re: [R] ggsave to .png bug in ggplot2 (?)

be extracted from a given body of data. ~ John Tukey -Oorspronkelijk bericht- Van: r-help-boun...@r-project.org [mailto:r-help-boun...@r-project.org] Namens Dieter Menne Verzonden: donderdag 20 augustus 2009 9:13 Aan: r-help@r-project.org Onderwerp: Re: [R] ggsave to .png bug in ggplot2

Re: [R] ggsave to .png bug in ggplot2 (?)

ONKELINX, Thierry wrote: My workaround is to always save my plots to pdf. .. In that case I convert the pdf to png outside R. The best tools I found for that are Ghostfriend (http://www.noliturbare.com/index.php) and www.zamzar.com. Which is also my approach, but not using ggsave or

[R] ggsave to .png bug in ggplot2 (?)

Text is really small and legend boxes are huge in this plot when saved to .png with ggsave. Plot is correct (i.e. looks the same as the screen) when saved with dev.print. Saving to .pdf with ggsave give the correct output. I'm a noob at ggplot2 so this may be user error rather than a bug.

[R] is that a bug

Dear people, I was using plot function, and kept getting information such as Error in axis(1, 1:4, LETTERS[1:4]) : too few arguments. I use the examples given in 'axis' help, and got same error information. Can any of you please tell me what's the problem and how can I fix it? Thanks a lot and

Re: [R] is that a bug

KunW wrote: Dear people, I was using plot function, and kept getting information such as Error in axis(1, 1:4, LETTERS[1:4]) : too few arguments. I use the examples given in 'axis' help, and got same error information. Can any of you please tell me what's the problem and how can I fix it?

Re: [R] is that a bug

Peter Dalgaard wrote: KunW wrote: Dear people, I was using plot function, and kept getting information such as Error in axis(1, 1:4, LETTERS[1:4]) : too few arguments. I use the examples given in 'axis' help, and got same error information. Can any of you please tell me what's the

[R] foruntes candidate?? WAS:Re: Bug in is ?

Douglas Bates [after a tortuous discussion of the behavior of is(7,integer)]: As for the question of the bug in is, ... it depends what your definition of `is' is. [Bill Clinton] --- Good one, Douglas! Chuck On Thu, 25 Sep 2008, Douglas Bates wrote: On Thu, Sep 25, 2008 at 4:23

Re: [R] foruntes candidate?? WAS:Re: Bug in is ?

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles C. Berry Sent: Thursday, September 25, 2008 4:31 PM To: Douglas Bates Cc: Wacek Kusnierczyk; Achim Zeileis; R help Subject: [R] foruntes candidate?? WAS:Re: Bug in is ? Douglas Bates

Re: [R] Fix for nls bug???

On Fri, 8 Aug 2008, Keith Jewell wrote: Dear Prof. Ripley, Thank you for your helpful reply. I will download and try R-patched ASAP. I take your point, I should have tried the latest version (R-patched) before posting. With respect to R-patched, would you recommend its use routinely, or only

Re: [R] Fix for nls bug??? [already fixed in R-patched]

Dear Prof. Ripley, Thanks for that. Just to wrap up the thread, I confirm that my problem is fully fixed in R-patched. Best regards, Keith Jewell --- Prof Brian Ripley [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] On Fri, 8 Aug 2008, Keith Jewell wrote: Dear Prof.

Re: [R] Fix for nls bug???

Your example works in R-patched, as a consequence of investigations of a different problem. (See the comments in the posting guide about updating your R and trying the very latest versions.) Windows binaries for R-patched are available on CRAN. On Tue, 5 Aug 2008, Keith Jewell wrote: Hi

[R] Fix for nls bug???

Hi All, I've hit a problem using nls. I think it may be a restriction in the applicability of nls and I may have found a fix, but I've been wrong before. This example is simplified to the essentials. My real application is much more complicated. Take a function of matrix 'x' with additional

[R] is this a bug (apply and class) ?

Hello R users, I run this code under windows XP and R 2.7.1 : head(esoph) agegp alcgptobgp ncases ncontrols 1 25-34 0-39g/day 0-9g/day 040 2 25-34 0-39g/day10-19 010 3 25-34 0-39g/day20-29 0 6 4 25-34 0-39g/day 30+ 0 5 5

Re: [R] is this a bug (apply and class) ?

On 8/1/2008 4:49 AM, David Hajage wrote: Hello R users, I run this code under windows XP and R 2.7.1 : head(esoph) agegp alcgptobgp ncases ncontrols 1 25-34 0-39g/day 0-9g/day 040 2 25-34 0-39g/day10-19 010 3 25-34 0-39g/day20-29 0 6 4

Re: [R] is this a bug (apply and class) ?

Please do read ?apply (see the posting guide) If 'X' is not an array but has a dimension attribute, 'apply' attempts to coerce it to an array via 'as.matrix' if it is two-dimensional (e.g., data frames) or via 'as.array'. and note sapply(esoph, class) $agegp [1] ordered factor

[R] Odp: FW: RES: bug in axis.Date? was (Re: newbie needs help plottingtimeseries)

- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leandro Marino Sent: Wednesday, July 02, 2008 5:47 PM To: Petr PIKAL; Kathi Cc: [EMAIL PROTECTED] Subject: [R] RES: bug in axis.Date? was (Re: newbie needs help plottingtimeseries) You can do this plot saying to R that your

Re: [R] is this a bug? [was Re: again with polr]

On 15/03/08 - 15:21, Luca Braglia wrote: Hello everybody as I said, i'm not a ordered probit guru, but what happened seems to me a little strange. Here I put my dataset http://bragliozzo.altervista.org/asd.dta my fault: i forgot the new antileech system on altervista

[R] source(echo=TRUE) bug (was: source() behavior I don't understand)

name ttt is not echoed when sourced from a file. It is echoed when sourced from a character string. The name is echoed in both situations when it begins with a letter other than t. Specifically I have tested tt and ttt. Looks like a bug in a regular expression. R doesn't echo lines containing

Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand)

Thanks Duncan, While there, can you give a new optional argument that will permit the echo of blanks and comments? Rich __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide

Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand)

On 09/03/2008 10:40 PM, Richard M. Heiberger wrote: Thanks Duncan, While there, can you give a new optional argument that will permit the echo of blanks and comments? Comments are already echoed, leading blank lines are not (but blanks in comments are). For example: temp.ttt - ttt -

Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand)

, or by surrounding them with blank lines and using C-c C-c. Rich -Original Message- From: Duncan Murdoch [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2008 10:52 PM To: Richard M. Heiberger Cc: r-help@r-project.org Subject: Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand

Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand)

: Duncan Murdoch [mailto:[EMAIL PROTECTED] Sent: Sunday, March 09, 2008 10:52 PM To: Richard M. Heiberger Cc: r-help@r-project.org Subject: Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand) On 09/03/2008 10:40 PM, Richard M. Heiberger wrote: Thanks Duncan, While

Re: [R] source(echo=TRUE) bug (was: source() behavior I don't understand)

Ok, I'll write something and try it out. Rich -Original Message- From: Duncan Murdoch [mailto:[EMAIL PROTECTED] source() is pure R code, so if you want a function that behaves differently, you can do it fairly easily yourself. __

  1   2   >