search for: r_loess_raw

Displaying 7 results from an estimated 7 matches for "r_loess_raw".

2006 Oct 09
1
[Mac OS X 10.4] object R_loess_raw not found
...Type '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...
2006 Oct 09
1
[Mac OS X 10.4] object R_loess_raw not found (reason found)
Well... this may be a red herring after all, but it's an interesting one! It turns out I have got DYLD_LIBRARY_PATH set. This gets exported to R (or rather, affects the loader that loads the R process?), and somehow mixes up the way symbols are exported. Something that applies to launching R from the command line (/usr/bin/R) AND via LaunchServices (open -a R). Once I noticed that invoking
2006 Jul 02
1
prefix 'R_' when calling external code
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
2008 Jul 08
1
R crash with ATLAS precompiled Rblas.dll on Windows XP Core2 Duo
...RAN and couldn't find any information related to possible crash causes. I've used the ATLAS BLAS for about 6 months on this machine (it's a new machine) with R 2.6.2. Using debug(stats:::simpleLoess), I've found that the crash occurs on the first iteration of the line: z <- .C(R_loess_raw, as.double(y), as.double(x), as.double(weights), as.double(robust), as.integer(D), as.integer(N), as.double(span), as.integer(degree), as.integer(nonparametric), as.integer(order.drop.sqr), as.integer(sum.drop.sqr), as.double(span...
2011 Jun 16
0
Update: Is there an implementation of loess with more than 3 parametric predictors or a trick to a similar effect?
...t;interpolate" && statistics == "approximate") statistics <- if(trace.hat == "exact") "1.approx" else "2.approx" # trace.hat == "approximate" surf.stat <- paste(surface, statistics, sep="/") z <- .C(R_loess_raw, # ../src/loessc.c as.double(y), as.double(x), as.double(weights), as.double(robust), as.integer(D), as.integer(N), as.double(span), as.integer(degree), as.integer(nonparametric), as.integer(order.drop.sqr), as.integer(sum.drop.sqr), as.double(span*cell), as.character(surf...
2010 May 05
0
A question regarding the loess function
...1070 158.478596 14.276745 160.787420 157.644046 15.373103 168.555670 161.076443 15.647664 152.426580 161.123333 18.560536 221.707020 225.721022 18.586635 222.690400 226.986782 18.757281 243.188280 235.647504 If you are still reading, thanks! I have tried poking around in the R source code for the R_loess_raw (loessc.c) method, but I find it quite dense and hard to follow... if anyone has some debugging ideas, they would be greatly appreciated. Thank you for your attention, Scott [[alternative HTML version deleted]]
2010 May 05
0
R-help Digest, Vol 87, Issue 5
...1070 158.478596 14.276745 160.787420 157.644046 15.373103 168.555670 161.076443 15.647664 152.426580 161.123333 18.560536 221.707020 225.721022 18.586635 222.690400 226.986782 18.757281 243.188280 235.647504 If you are still reading, thanks! I have tried poking around in the R source code for the R_loess_raw (loessc.c) method, but I find it quite dense and hard to follow... if anyone has some debugging ideas, they would be greatly appreciated. Thank you for your attention, Scott [[alternative HTML version deleted]] ------------------------------ Message: 136 Date: Wed, 5 May 2010 01:14:01 -0700...