similar to: Thick stripes in the barplot() function

Hi. I have a problem with the default behavior of seq(), which gives the argument "from" when the argument length.out = 1. This behavior is annoying when the number of value determine in length.out is not predictable. Would it be possible to add an argument that propose the median/mean, i.e. (from + to) / 2 when length.out = 1 ? Examples: > seq(from = 1, to = 11, length.out=1) #

Regardless of the value of the other arguments, the first element in the output of seq() is _always_ `from`. Hadley On Mon, Jun 15, 2015 at 9:56 AM, Millot Gael <Gael.Millot at curie.fr> wrote: > Thanks for your answer. > > The rational behind my proposal is why taking "from" when length.out=1, more than "to" or "NA", or " integer(0) " ?

Millot, I think the problem with that is that what you propose isn't a sequence starting at from in any meaningful way, and thus does not satisfy the contract of the seq function. Best, ~G On Jun 15, 2015 7:12 AM, "Millot Gael" <Gael.Millot at curie.fr> wrote: > Hi. > > I have a problem with the default behavior of seq(), which gives the > argument

Hi. I have a problem with the default behavior of sample(), which performs sample(1:x) when x is a single value. This behavior is well explained in ?sample. However, this behavior is annoying when the number of value is not predictable. Would it be possible to add an argument that desactivates this and perform the sampling on a single value ? Examples: > sample(10, size = 1, replace = FALSE)

Thanks for your answer. The rational behind my proposal is why taking "from" when length.out=1, more than "to" or "NA", or " integer(0) " ? This question seems basic. But is is not in certain situations, like when length.out = unpredictable positive integer. And I haven't found in ?seq() the particular behavior of this function when length.out = 1.

Am .06.2015, 14:55 Uhr, schrieb Millot Gael <Gael.Millot at curie.fr>: > Hi. > > I have a problem with the default behavior of sample(), which performs > sample(1:x) when x is a single value. > This behavior is well explained in ?sample. > However, this behavior is annoying when the number of value is not > predictable. Would it be possible to add an argument >

Full_Name: Gael Millot Version: 2.2.0. OS: XP Submission from: (NULL) (195.220.102.20) Hello. I sent an Email in r-help without answer for the moment. I am wondering if it could have a mistake in the code of the ansari.test function. For me, it seems that the function do not recover the p value at the correct side of the normal law N(0, 1) when it use the normal approximation (presence of

Millot, On Mon, Jun 15, 2015 at 9:19 AM, Hadley Wickham <h.wickham at gmail.com> wrote: > Regardless of the value of the other arguments, the first element in > the output of seq() is _always_ `from`. > Indeed, as Hadley says, the output of seq must always start with* from*. It is a sequence starting at *from* and ending wherever the other arguments cause it to end. A sequence

Hello. I am probably wrong... I am wondering if it could have a mistake in the code of the ansari.test function. For me, it seems that the function do not recover the p value at the correct side of the normal law N(0, 1) when it use the normal approximation (presence of ties) in a one tailed test. Exemple : quanti<-c(197, 205, 228, 234, 237, 195, 233, 226, 244, 227, 259, 185, 198, 253, 207,

Hi, Special behavior of sample(x, ...) when length(x) is 1 is of course a bad feature. I think it pre-dates sample.int() which is what people should use these days if they want the behavior of sample(x, ...) when length(x) is 1. And because we now have sample.int(), this feature could in theory be removed from sample(). Unfortunately this would break a lot of existing code so a warning or some

On 6/16/2015 1:32 PM, Peter Meissner wrote: > Am .06.2015, 14:55 Uhr, schrieb Millot Gael <Gael.Millot at curie.fr>: > >> Hi. >> >> I have a problem with the default behavior of sample(), which performs >> sample(1:x) when x is a single value. >> This behavior is well explained in ?sample. >> However, this behavior is annoying when the number of

I am running R 2.0.0, GOstats 1.1.1 and GO 1.7.0, and when I use the function GOHyperG, I have the following error: w1<-as.list(hgu95av2LOCUSID) w2<-unique(unlist(w1)) set.seed(123) myLL<-sample(w2,100) xx <- GOHyperG(myLL) Error in mget(x, env = GOTERM, ifnotfound = NA) : recursive default argument reference In fact first I tried this function with my locusId ' list (with

I am running R 2.0.0 on a SunOs 5.9 machine and using Oracle 8i.1.7.0.0 (enterprise edition) and when I try to load ROracle I receive the following error: "require(ROracle) Loading required package: ROracle Loading required package: DBI Error in dyn.load(x, as.logical(local), as.logical(now)) : unable to load shared library

Dear all, May I suggest to add an example in the help page of the colors() function ? The following code could be useful to easily choose any color from colors() : ## Millot G. (2011), p.71. ## Figure displaying all the 657 built-in color names of colors(). palette(colors()) tempo<-NULL for(i in 14:1){tempo<-c(tempo, rep(i,50))} windows(width=10) # replace by quartz(width=10) for MacOS and

Dear All: I'm new to R, though I've used S+ on Windows. Since now I'm working on a SGI, I would like to switch to R. I'm trying to install R v.0.64.1 on a Silicon Graphics R5000 under IRIX 6.3, 180 MHz, 128 Mb RAM, but ran into some problems. When I do the ./configure everything goes well, but when I do the make I get the following error: ld: ERROR 33: Unresolved text symbol

Hi, the function makeARIMA(), designed to construct some state space representation of an ARIMA model, uses a C function called getQ0, which can be found at the end of arima.c in R source files (library stats). getQ0 takes two arguments, phi and theta, and returns the covariance matrix of the state prediction error at time zero. The reference for getQ0 (cited by help(arima)) is:

Hi there. Any problems to use 2 NVMe joined together via lvm, and than on top of that, great a Gluster volume? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20241121/f425ff85/attachment.html>

On 2024-11-21 16:19, Gilberto Ferreira wrote: > Hi?there. > > Any problems to use 2 NVMe joined together via lvm, and than on top of > that, great a Gluster volume? > > Cheers > As a general rule this is ok. We have several gluster volumes built on? top of an LVM underlying structure. -- Alvin Starr || land: (647)478-6285 Netvel Inc.

Hi Allan! Thanks for your feedback. Cheers Em sex., 22 de nov. de 2024 ?s 00:49, Alvin Starr <alvin at netvel.net> escreveu: > On 2024-11-21 16:19, Gilberto Ferreira wrote: > > Hi there. > > Any problems to use 2 NVMe joined together via lvm, and than on top of > that, great a Gluster volume? > > Cheers > > As a general rule this is ok. > We have

I am afraid of lvm going to disk failure. So if I have 2 disk and one crashes, I thing all LVM goes bad! So, I have decided to used individual disk. Thanks Em sex., 22 de nov. de 2024 ?s 13:39, Gilberto Ferreira < gilberto.nunes32 at gmail.com> escreveu: > Hi Allan! > > Thanks for your feedback. > > Cheers > > > > > > > > Em sex., 22 de nov. de