search for: loess_raw

I noticed that in https://svn.r-project.org/R/trunk/src/library/stats/R/loess.R that we are now calling R_loess_raw, R_lowesw, R_lowesp, etc. I'm interested to know what is the benefit/reason for the 'R_', as I am unfamiliar with this prefix and do not see it mentioned in 'Writing R Extensions.' Thanks, Ben

...ype 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. [Previously saved workspace restored] > example(loess) loess> cars.lo <- loess(dist ~ speed, cars) Error: object "R_loess_raw" not found I saw this first with a self-built 2.3.1 version, that worked fine under 10.3 . Hoping that a Tiger build would solve matters, I installed the fresh 2.4.0 from the downloaded disk image. As you can see, the error message persists. Curiously, the ppc/stats.so file somewhere deep i...

...e a few package maintainers. A good selection of the reports will be available at http://www.stats.ox.ac.uk/pub/bdr/Rvg for the next week or so. Valgrind is not infallible and sometimes gets confused by highly optimized code (and these tests were run with -O2): I reckon this is the case for the loess_raw reports. `Writing R Extensions' in 2.0.1 will have a section on `writing portable packages' covering this, and R-devel has a R CMD check --use-valgrind option to run all the examples/tests/vignettes under valgrind -- beware that is typically 20x slower. Another problem area is running...

Full_Name: Benjamin Tyner Version: 2.1.0, 4/18/2005 OS: i686-redhat-linux-gnu Submission from: (NULL) (4.64.8.220) # Just run my.test() below in a newly opened R session. Once too many models have been fit (~20 on my system), the computed standard error jumps to a different value. This is (superficially) due to a different residual sum of squares, not a different one.delta. No other aspect of