similar to: R-beta: acepack with 0.50-a1

Displaying 20 results from an estimated 200 matches similar to: "R-beta: acepack with 0.50-a1"

2000 Mar 27
1
R port of acepack
To whom should bug reports of the R port of acepack be directed? On a SPARC/Solaris 2.6 or 2.7 (SunOS 5.6 or 5.7) system running R-1.0.0 the avas example fails > library(acepack) > example(avas) avas> TWOPI <- 8 * atan(1) avas> x <- runif(200, 0, TWOPI) avas> y <- exp(sin(x) + rnorm(200)/2) avas> a <- avas(x, y) Process R bus error (core dumped) at Mon
2010 Jun 03
1
Memory leak using Rgraphviz
I'm running an Ubuntu 10.04 system and installed R 2.10.1 through the package manger. I then installed Rgraphviz 1.24 and graph 1.26 through R. I'm trying to understand why a complex function my team wrote causes R's memory footprint viewed through top to increase every time it's run. I traced the increase in memory usage to layoutGraph() and wrote the following short function
1997 Aug 04
1
R-alpha: Re: your mail
>>>>> Thomas Lumley writes: > On Fri, 1 Aug 1997, Kurt Hornik wrote: >> Thomas, >> >> Could you add the "-lf2c" at the end of the line >> @$(LD) $(SHLIBLDFLAGS) -o $(LIBNAME).so $(OBJS) >> in acepack's src-c/Makefile? >> >> I ran across an identical pow_dd problem recently with another package. >> Did we always need
1997 Aug 05
3
R-alpha: Version 0.50-a1 patches
A set of patches for R-0.50-a1 is now available as ftp://stat.auckland.ac.nz/pub/R/R-0.50-a1.patch1.gz The patches mainly fix problems reported since R-0.50-a1 but some older problems are also fixed. Here is the list of changes. Ross o Many subsetting and mutation problems with the new "expression" type have now been fixed. o When ask=T is set in par() the user is instructed
2015 Jul 29
0
[LLVMdev] [3.7.0] Two late issues with cross compilation to mips
I believe I've identified the problem with almabench but I haven't found the root cause in the compiler yet. The problem is that a caller saved register ($f14) is being moved across a call and this call sometimes clobbers the value. As a result, the value of the TWOPI constant used in the fmod() calls isn't always 2*PI. According to -print-after-all, the pass that moves the
2015 Jul 30
2
[LLVMdev] [3.7.0] Two late issues with cross compilation to mips
To reduce memory consumption clobbered registers are handled with RegisterMask machine operands which contain a bitset of all registers clobbered. - Matthias > On Jul 29, 2015, at 3:00 PM, Daniel Sanders <daniel.sanders at imgtec.com> wrote: > > I believe I've identified the problem with almabench but I haven't found the root cause in the compiler yet. > > The
2013 Dec 17
3
In-string variable/symbol substitution: What formats/syntax is out there?
Hi, I'm try to collect a list of methods/packages available in R for doing in-string variable/symbol substitution, e.g. someFcn("pi=${pi}"), anotherFcn("pi=@pi@") and so on becomes "pi=3.141593". I am aware of the following: ** gsubfn() in the 'gsubfn' package, e.g. > gsubfn( , , "pi = $pi, 2pi = `2*pi`") [1] "pi = 3.14159265358979,
1998 May 20
2
libraries; Fortran / -lf2c / Slackware woes
Jim, you should ask questions like these on R-devel. There are more proficient Linux gurus on there than me [that's why I CC:]. >>>>> "Jim" == Jim Lindsey <jlindsey@luc.ac.be> writes: Jim> Martin, Here is an additional problem with my libraries: the Jim> Kalman filtering, written in Fortran, uses complex arithmetic. Jim> On my Red Hat 5,
1997 Jul 28
0
R-alpha: R 0.50.a1 problems with lm/glm methods
Thanks for fixing formula() and update(). Here are some open problems. * effects: ** There is no help available for effects() ** The lm() help page has effects(lm.obj), but from the code it is clear that the one-arg version cannot work. Shouldn't it simply return z$effects? ** The two-arg version only works for factors (?) ... otherwise, z$model.frame[factors & pattern != 0] gives
1997 Jul 28
0
R-alpha: R 0.50.a1 S_alloc BUG, priority = URGENT
The current version of S_alloc in src/main/memory.c is char *S_alloc(long nelem, int eltsize) { unsigned int i, size; char *p = R_alloc(nelem, eltsize); for(i=0 ; i<size; i++) p[i] = 0; return p; } which segfaults because `size' is not initialized. I am not what the right fix is, adding size = nelem * eltsize; before the loop seems to work. As an aside ... I think the seed*
1997 Jul 28
0
R-alpha: R 0.50.a1 unlist() problems
Two things. TASKS has TASK: Naming with Numeric Values and "unlist" STATUS: Open FROM: <hornik@ci.tuwien.ac.at> R> l <- list("11" = 1:5) R> l $11 [1] 1 2 3 4 5 R> unlist(l) 111 112 113 114 115 1 2 3 4 5 [ Bug or feature ? ] This seems to be a feature (at least, SPLUS does the same), so please close that task. *** However, please add
1997 Jul 28
1
R-alpha: R 0.50.a1 problem
Here's something really strange. ******************************************************** R> x <- 1:5 R> x [1] 1 2 3 4 5 R> test1 function (x) { structure(x, call = sys.call()) } R> test1(x) [1] 1 2 3 4 5 attr(,"call") test1(x) R> test2 function (x) { attr(x, "call") <- sys.call() x } R> test2(x) Error: stack overflow
1997 Jul 28
0
R-alpha: R 0.50.a1: small patches for graphics and image demo
Applying the following patches closes the following task (part 1 was already taken care of). TASK: New Problems STATUS: Open FROM: <Kurt.Hornik@ci.tuwien.ac.at> New minor remarks: * The documentation for `image' still has the old order z, x, y. * Perhaps one should add `par(ask = T)' in the image demo? * Perhaps one should save the original value
1997 Aug 01
0
R-alpha: R 0.50.a1 graphics
Here are some misc comments on graphics. * I am not sure whether `adj' works correctly. When using e.g. title(sub = "SUBTITLE", adj = 0) shouldn't the subtitle appear on the very left? It seems that justification is done off the middle of the plot window. * S barplot has argument `horiz', R does not. * More importantly, the barplot() argument `space' is treated
1997 Aug 04
0
R-alpha: 0.50-a1 -- "more lost comments"
In CHANGES, it says ------------------------------------------------------------ >> BUG FIXES ........ >> o Comments are handled better in functions. The rule is that they >> are shifted to just before their statements. Comments after the >> last statement of a function are lost. ------------------------------------------------------------ I think we could
1997 Jul 28
0
R-alpha: R 0.50.a1: patch for NChisquare documentation
The patch below fixes the NChisquare documentation problem that I've been mentioning for some time now. NOTE: There is one DEQN where the LaTeX part contains real LaTeX code, because I did not see how to get a sum sign (and a roman math font) otherwise. Seems to work, though ... MARTIN? -k ********************************************************************** ***
1997 Sep 24
1
R-beta: R-0.50-a4 library problem (survival4)
I have built R-0.50-a4 on HP9000/C160-hpux10.2 with gcc (cc for libs). When I try library(survival4) Error in pos.to.env(pos) : invalid "pos" argument And it does not load. Other libs seem to work. I tested integrate (has f2c translated c), polynomial. Is this a problem with my system only??? TIA osman =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
1997 Aug 08
4
R-alpha: Second patch for 0.50-a1
A second patch for R-0.50-a1 is available from ftp://stat.auckland.ac.nz/pub/R The patch produces the following changes o cpoly problem with pow_di fixed. o legend had a call to "text" with an incorrect argument tag. Changed "text" to "labels". o The variable "dup" was uninitialised in the function "naoktrim" in
2015 Jul 30
0
[LLVMdev] [3.7.0] Two late issues with cross compilation to mips
Thanks. This is making a lot more sense now and it's looking like this issue isn't Mips specific. Here's the IR dump before simple register coalescing (note: I've patched the IR printer to print the contents of the regmask): 4480B %vreg260<def> = LDC1 %vreg253, <cp#3>[TF=6]; mem:LD8[ConstantPool] AFGR64:%vreg260 GPR32:%vreg253 4496B %vreg261<def> = FMUL_D32
1997 Jul 29
2
R-alpha: Bugs in R-0.50-a1.
Problems in R but not in S: --------------------------- 1) 'unlist' seems to have several other problems than the ones reported up to now. For instance, 'unlist' can be used on almost any object in S without much trouble. Eg.: S> unlist(c(2)) [1] 2 S> --- R> unlist(c(2)) Segmentation fault (core dumped) This occurs in R-0.49 and in R-0.50-a1. 2) Problem with the