search for: xtemp

...17 18 19 20 3> 22 24 26 28 30 32 34 36 38 40 42 44 46 48 50 52 54 56 58 4> 650.0 650.5 651.0 651.5 652.0 652.5 653.0 653.5 654.0 5> 654.5 655.0 655.5 656.0 656.5 657.0 657.5 658.0 658.5 ... 7> 1599.5 1600.0 8> 9> 1 1 0 10> Xtemp.wf 11> 2 12> Xtemp.noise 13> 4 14> Xtemp.Sa --- Line 1 contains 2 numbers (nx, ny) which can easily be read using scan. If nx>0 then there are nx values to be read next (i.e. lines 2 and 3 have 39 values). Likewise, with ny>0, lines 4-7 give 1901 values. However, if nx or ny ar...

Sorry, that's a cut and paste error. It should be either tempx or xtemp throughout. Terry T On 06/11/2015 12:59 PM, John Nolan wrote: > Is there a misprint in your example? The first line of code uses tempx, but the rest uses a different variable xtemp? > > John > > -----"R-devel" <r-devel-bounces at r-project.org> wrote: ----- > To:...

...r --slave ######################################## ######################################## #tnp2.r - contents of tnp2.r script file are below print(R.Version()$version.string) #generate some data x <- rep(c(1:12),3) y <- 1:length(x)+rnorm(length(x)) print(x) print(y) #this bit works OK xtemp <- lm(y ~ x ) print(xtemp) print("got to here (without factor part)") monthfac <- as.factor(x) print(monthfac) #this line below causes probs in R v2.10.1 when run from Rscript..... xtemp2 <- lm(y ~ monthfac) print(xtemp2) stop("stopped on purpose",call.=F) #end of f...

...f the "optimization outside atomic" section ... However, LLVM is not allowed to transform the former to the latter: it could introduce undefined behavior if another thread can access x at the same time. ... Is the ``undefined behavior'' introduced by the addition write "x = xtemp"? For example, if a[i] is always false in the original program, there is no the write. But I don't think "int xtemp = x;" can introduce undefined behavior, if LLVM does not take load/store race as undefined. Am I correct? > >> * a store/load data race does not result in...

Hi All, I want to take a matrix (or data frame) and winsorize each variable. So I can, for example, correlate the winsorized variables. The code below will winsorize a single vector, but when applied to several vectors, each ends up sorted independently in ascending order so that a given observation is no longer on the same row for each vector. So I need to winsorize the variable but

The following code snippet taken from plot.survfit now gives me a surprising result: tempx <- c(0, 400, 0, 0) ytemp <- c(.0657, .98, 1, 0) plot(range(xtemp), range(ytemp), log='y', type='n') In that the max value for the x axis is now 10. The 0 on the end of ytemp was actually a mistake and shouldn't be there, if you remove it then the upper limit is sensible. plot(range(xtemp), range(ytemp[1:3]), log='y', type='n...

Dear all, What is the cumulative distribution (with parameterization) used within survreg with respect to the log-logistic distribution? That is, how are the parameters linked to the survivor function? Best regards, Mario [[alternative HTML version deleted]]

configure fails with : configure: error: Unsupported off_t type I am not too sure what off_t is needed but this is a pretty standard thing. My configure line : ./configure --build=i386-pc-solaris2.10 --host=i386-pc-solaris2.10 --prefix=/opt/csw --with-zlib --with-ssl=openssl --with-storages=mbox,maildir --with-libiconv-prefix=/opt/csw Yes, the openssl libs are in /opt/csw/lib Not sure what

On Mon, Aug 22, 2011 at 11:17 AM, Jianzhou Zhao <jianzhou at seas.upenn.edu> wrote: > On Mon, Aug 22, 2011 at 1:02 PM, Eli Friedman <eli.friedman at gmail.com> wrote: >> On Mon, Aug 22, 2011 at 9:55 AM, Jianzhou Zhao <jianzhou at seas.upenn.edu> wrote: >>> In the definition of 'monotonic' ordering, >>> ... "If an address is written