search for: imidiately

...y to set par(), it is in particular setting type='l' I'm interested in. Starting from scratch, the default says: > par()$type [1] "p" and indeed the plot is a point-type plot. I go > par(type='l') > par()$type [1] "l" But doing e.g. > plot(x,1/x) imidiately afterwards still produces a point-type plot. I have to say > plot(x,1/x, type='l') to get a line-type plot. What am I doing wrong? Finally, I get a warning when trying to compile a c-routine (that was provided to me by Brain Ripley to read the abovementioned images off-list), it doesn...

...PKG.Rcheck/PKG/unitTests/report.txt - PKG.Rcheck/PKG/unitTests/report.html R CMD check will say OK also when some unit tests fails, but unit tests are at least issued and one should check above outputs to see the results of unit testing. I use the following in my ~/.Makefile to see these results imidiately NAME := $(shell basename $(PWD)) # Get current map name Rcheck: # Check R package of current map (cd ..; \ R CMD check $(NAME) && \ if [ -d $(NAME)/inst/unitTests ]; then \ cat $(NAME).Rcheck/tests/doRUnit.Rout; \ fi) Then only the following is necesarry to start R CME check and p...

...=seed)) } The first function is called by the latter, and this is where things most often go wrong. Output from the print statements often say something like test lbs lc lct lbl lcl 7 910 909 5312 5313 5312 test hb hc 5 5313 0 Since bl is passed as breaks and ct as counts imidiately after the test=7 print, and test=5 is called just after the object has been returned, hb should here be equal to lbl (which it is, in this case), and lct should be equal to hc, but hc is for some strange reason 0.... Of course, this doesn't happen always, just once in a while, e.g. the previou...