similar to: Suggestion for debug: optional count for `next' command

hi, Just a very simple question: is there an R equivalent to the matlab command find(X) which returns the indices of vector X that store non-zero elements? e.g. > find( [1 0 0 1 0]) ans = 1 4 so, in R, how do I do: ans <- rfind( c(1,0,0,1,0)) so that ans is the vector c(1,4) thanks, stephen -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help

Hi, [System info: R 1.6.1 compiled from source (no args to configure) on Redhat 7.1 Linux i/386] I have some spatial statistics programs that recently (since R 1.6.1) have generated SIGSEGV. These R programs use the splancs library as well as some C code of my own for Voronoi analysis. The program has a big loop to fit various model parameters against a spatial distribution of biological

Full_Name: Stephen Eglen Version: 1.4 OS: Redhat Linux 7.1 Submission from: (NULL) (128.252.204.36) I think the brackets in the levels of cut() are slightly incorrect when include.lowest is TRUE. For example: > table(cut( c(1,4), include.lowest=T, right=F, breaks=c(1,2,3,4))) [1,2) [2,3) [3,4) 1 0 1 I think the last range in this case should be [3,4]. A similar problem

Martin Maechler <maechler@stat.math.ethz.ch> writes: > (from R-help) > PD> Stephen Eglen <stephen@cogsci.ed.ac.uk> writes: > > > > > generated by R into a latex document. Specifically, the latex package > > > > graphicsx allow you to specify the bounding box of the postscript > > > > file, so that you can just show

On Wednesday, 7 December 2016 17:13:08 CET Tomáš Golembiovský wrote: > Added two new optional arguments to nsplit: > > * noempty: if set to false empty elements are not stored in the returned > list. The default is to keep the empty elements > > * count: specifies how many splits to perform; negative count > (the default) means do as many splits as possible > >

On Sunday, 18 December 2016 23:16:31 CET Tomáš Golembiovský wrote: > Added two new optional arguments to nsplit: > > * noempty: if set to false empty elements are not stored in the returned > list. The default is to keep the empty elements > > * count: specifies how many splits to perform; negative count > (the default) means do as many splits as possible > >

On Fri, Dec 09, 2016 at 10:52:23AM +0100, Pino Toscano wrote: > On Wednesday, 7 December 2016 17:13:08 CET Tomáš Golembiovský wrote: > > Added two new optional arguments to nsplit: > > > > * noempty: if set to false empty elements are not stored in the returned > > list. The default is to keep the empty elements > > > > * count: specifies how many splits

Added two new optional arguments to nsplit: * noempty: if set to false empty elements are not stored in the returned list. The default is to keep the empty elements * count: specifies how many splits to perform; negative count (the default) means do as many splits as possible Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- mllib/common_utils.ml | 12 +++++++++---

Full_Name: Stephen Eglen Version: 1.4 OS: Redhat Linux 7.1 Submission from: (NULL) (128.252.204.36) abline() produces a spurious line in addition to the correct line, at least with the X11 driver. The postscript file generated also has nan values in it, which causes an error under ghostscript. xs <- c(0, 150, 300) ys <- c(75, 40, 23) par(mfrow=c(1,2)) plot(xs,ys, log="")

Added two new optional arguments to nsplit: * noempty: if set to false empty elements are not stored in the returned list. The default is to keep the empty elements * count: specifies how many splits to perform; negative count (the default) means do as many splits as possible Added tests for nsplit. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- mllib/common_utils.ml

Added two new optional arguments to nsplit: * keep_empty: if set to false empty elements are not stored in the returned list. The default is to keep the empty elements * count: specifies how many splits to perform; negative count (the default) means do as many splits as possible Added tests for nsplit. Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com> --- mllib/common_utils.ml

Small suggestion for the documentation: Should the = operator for assignments, described on http://developer.r-project.org/equalAssign.html, now be included in the operator table in doc/manual/R-lang.texi? If so, one possibility could be after lines 1096/7: @item @code{<-} @tab Left assignment, binary @item @code{=} @tab Left assignment, binary Also, where is the best place to send

>>>>> "StEgl" == Stephen Eglen <stephen@cogsci.ed.ac.uk> writes: StEgl> Hi, I just upgraded to 1.1.0 from 1.0.1 this morning on my OSF/1 StEgl> machine. I now have problems with the following code: StEgl> %E /tmp 43% R --vanilla StEgl> Version 1.1.0 (June 15, 2000) StEgl> ... >> test2 <- function () {

I recently wrote a vignette, with the following at the top of the .Rnw file: %%\VignetteIndexEntry{How to use look up tables for h() functions} %%\VignetteDepends{sjedmin, spatstat} Using vExplorer() on this function, I got an error from this part of getVigInfo(): lines <- grep("^%[[:space:]]*\\\\Vignette", file) if (length(lines) == 0) stop("File ", vig,

>>>>> "StEgl" == Stephen Eglen <stephen@inf.ed.ac.uk> >>>>> on Fri, 30 Jan 2004 12:56:48 +0000 writes: >> I was trying to use the new debug package from within emacs, I get the >> following error: >> >library(debug) >> Loading required package: mvbutils >> MVBUTILS: no "tasks" vector

Hello, I frequently use stripchart to summarise data. Recently I wished to plot a stripchart on a log scale, so modified stripchart locally. The change is small, just adding log="" to the function call and then changing line 42 of src/library/base/R/stripchart.R from: plot(xlim, ylim, type="n", ann=FALSE, axes=FALSE) to: plot(xlim, ylim, type="n",

Should R/src/library/base/man/Extremes.Rd (where max, min, pmax, pmin are documented) refer to which.min and which.max in the "\seealso" section? e.g. change the \seealso section (line 53) of Extremes.Rd to: \code{\link{range}}, \code{\link{which.min}}, etc.}, [Also, is r-help the right place for suggestions about documentation?] thanks, Stephen Eglen

hi, I've noticed a small problem trying to include postscript plots generated by R into a latex document. Specifically, the latex package graphicsx allow you to specify the bounding box of the postscript file, so that you can just show _part_ of the postscript file if you tell it to also clip the area outside of the bounding box. I've previously used this LaTeX feature without problems

On Wed, 2 Aug 2000 p.dalgaard@biostat.ku.dk wrote: > Martin Maechler <maechler@stat.math.ethz.ch> writes: > > > (from R-help) > > PD> Stephen Eglen <stephen@cogsci.ed.ac.uk> writes: > > > > > > > generated by R into a latex document. Specifically, the latex package > > > > > graphicsx allow you to specify the

Hi, I just upgraded to 1.1.0 from 1.0.1 this morning on my OSF/1 machine. I now have problems with the following code: %E /tmp 43% R --vanilla Version 1.1.0 (June 15, 2000) ... > test2 <- function () { plot(runif(30)) ofile <- "/tmp/newfile.ps" dev.print(file = ofile) } + + + + + > > test2() Error in device(...) : Object "ofile" not found However, if