search for: loessc

...7 -fpic -g -O2 -c backlo.f -o backlo.o g77 -fpic -g -O2 -c bsplvd.f -o bsplvd.o g77 -fpic -g -O2 -c bvalue.f -o bvalue.o g77 -fpic -g -O2 -c bvalus.f -o bvalus.o g77 -fpic -g -O2 -c linear.f -o linear.o gcc -I/usr/share/R/include -I/usr/share/R/include -fpic -g -O2 -std=gnu99 -c loessc.c -o loessc.o g77 -fpic -g -O2 -c loessf.f -o loessf.o g77 -fpic -g -O2 -c lo.f -o lo.o g77 -fpic -g -O2 -c qsbart.f -o qsbart.o gcc -I/usr/share/R/include -I/usr/share/R/include -fpic -g -O2 -std=gnu99 -c sbart.c -o sbart.o g77 -fpic -g -O2 -c sgram.f -o sgram.o g77 -fpic -g -O...

...t a different one.delta. No other aspect of the fit is affected, just the computed value of s (I've run extensive testing with all.equal() to make sure). Issuing a garbage collection before doing a loess fit appears to "solve" the problem, which makes me think this is not a problem in loessc.c or loessf.f. My point is that a few loess fits in one session should not cause the estimated standard error computation go awry with no warning. y<-rnorm(50) x<-seq(0,1,length=50) my.test<-function(){ counter<-0 go<-0 new.s<-0 while(go<2){ counter<-counter+1 old.s<-new...

...vd.f -o bsplvd.o g77 -O2 -fpic -c bvalue.f -o bvalue.o g77 -O2 -fpic -c bvalus.f -o bvalus.o g77 -O2 -fpic -c dpbfa.f -o dpbfa.o g77 -O2 -fpic -c dpbsl.f -o dpbsl.o gcc -ieee_with_inexact -g -O2 -I../../../../include -c ksmooth.c -o ksmooth.o gcc -ieee_with_inexact -g -O2 -I../../../../include -c loessc.c -o loessc.o g77 -O2 -fpic -c loessf.f -o loessf.o g77 -O2 -fpic -c ppr.f -o ppr.o g77 -O2 -fpic -c qsbart.f -o qsbart.o g77 -O2 -fpic -c sbart.f -o sbart.o g77 -O2 -fpic -c sgram.f -o sgram.o g77 -O2 -fpic -c sinerp.f -o sinerp.o g77 -O2 -fpic -c sslvrg.f -o sslvrg.o g77 -O2 -fpic -c stxwx.f -o s...

.../src/library/modreg/src' f77 -c bsplvd.f -o bsplvd.o f77 -c bvalue.f -o bvalue.o f77 -c bvalus.f -o bvalus.o f77 -c dpbfa.f -o dpbfa.o f77 -c dpbsl.f -o dpbsl.o cc -ieee_with_inexact -g -I../../../../include -c ksmooth.c -o ksmooth.o cc -ieee_with_inexact -g -I../../../../include -c loessc.c -o loessc.o f77 -c loessf.f -o loessf.o f77 -c ppr.f -o ppr.o f77 -c qsbart.f -o qsbart.o f77 -c sbart.f -o sbart.o fort: Info: sbart.f, line 164: No path to this statement 23012 continue ^ f77 -c sgram.f -o sgram.o f77 -c sinerp.f -o sinerp.o f77 -c sslvrg.f -o sslvrg.o f77 -c st...

...with gmake. A small transcript follows. If i make a link from gmake to make as under linux, then it works. This problem exists in all versions of R. g77 -O2 -fPIC -c sslvrg.f -o sslvrg.o g77 -O2 -fPIC -c stxwx.f -o stxwx.o ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o bvalus.o ksmooth.o loessc.o loessf.o ppr.o qsbart.o sbart.o sgram.o sinerp.o sslvrg.o stxwx.o Usage : make [ -f makefile ][ -K statefile ]... [ -d ][ -dd ][ -D ][ -DD ] [ -e ][ -i ][ -k ][ -n ][ -p ][ -P ][ -q ][ -r ][ -s ][ -S ][ -t ] [ -V ][ target... ][ macro=value... ] make: Fatal error: Unknow...

...nclude -c portsrc.f -o portsrc.o cc -xtarget=generic64 -G -L/mounts/devel/SUNWspro/lib/amd64 -L/usr/sfw/lib/amd64 -L/mounts/devel/GNU/repoz/readline43/lib/amd64 -o stats.so init.o kmeans.o ansari.o bandwidths.o chisqsim.o d2x2xk.o fexact.o kendall.o ks.o line.o smooth.o prho.o swilk.o ksmooth.o loessc.o isoreg.o Srunmed.o Trunmed.o dblcen.o distance.o hclust-utils.o nls.o HoltWinters.o PPsum.o arima.o burg.o filter.o mAR.o pacf.o starma.o port.o family.o bsplvd.o bvalue.o bvalus.o loessf.o ppr.o qsbart.o sbart.o sgram.o sinerp.o sslvrg.o stxwx.o hclust.o kmns.o eureka.o stl.o portsrc.o -x...

...and Gnu make 3.76-1. On several occasions, the make process aborted when trying to build the shared object file for the modreg package (its first attempt at such a beast). In all attempts, the error message is as follows: ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o bvalus.o ksmooth.o loessc.o loessf.o ppr.o qsbart.o sbart.o sgram.o sinerp.o sslvrg.o stxwx.o make: Fatal error: Unknown option `-w' gmake[4]: *** [modreg.so] Error 1 gmake[4]: Leaving directory `/tmp/R-0.64.1/src/library/modreg/src' In addition, I got the following error messages in this directory on the latest a...

...or compiling the latest version of R so that I can avoid these errors? configure make ... ... ... f90: CODE: 0 WORDS, DATA: 0 WORDS gcc -G -L/usr/local/lib -o stats.so init.o kmeans.o ansari.o bandwidths.o chisq sim.o d2x2xk.o fexact.o kendall.o ks.o line.o smooth.o prho.o swilk.o ksmooth .o loessc.o isoreg.o Srunmed.o Trunmed.o dblcen.o distance.o hclust-utils.o nl s.o HoltWinters.o PPsum.o arima.o burg.o filter.o mAR.o pacf.o starma.o port.o family.o sbart.o bsplvd.o bvalue.o bvalus.o loessf.o ppr.o qsbart.o sgram.o si nerp.o sslvrg.o stxwx.o hclust.o kmns.o eureka.o stl.o portsrc.o...

...ng: set address range perms: large range [0x5fb43040, 0xf8c8e130) (defined) ==30841== Invalid write of size 4 ==30841== at 0xCD719F0: ehg139_ (loessf.f:1444) ==30841== by 0xCD72E0C: ehg131_ (loessf.f:467) ==30841== by 0xCD73A5A: lowesb_ (loessf.f:1530) ==30841== by 0xCD2C774: loess_ise (loessc.c:219) ==30841== by 0x486C7F: do_dotCode (dotcode.c:1744) ==30841== by 0x4AB040: bcEval (eval.c:4544) ==30841== by 0x4B6B3F: Rf_eval (eval.c:498) ==30841== by 0x4BAD87: Rf_applyClosure (eval.c:960) ==30841== by 0x4B6D5E: Rf_eval (eval.c:611) ==30841== by 0x4B7A1E: do_eval (eval.c:...

...on it stops with an error, which says that the R/src/library/modreg/src/bsplvd.f isn't a valid Fortran77-File. Then, I installed f2c. But the compilation fails again with the message: gcc: unrecognized option `-PIC' ./../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o bvalus.o ksmooth.o loessc.o loessf.o ppr.o qsbart.o sbart.o sgram.o sinerp.o sslvrg.o stxwx.o Usage : make [ -f makefile ]... [ -d ][ -dd ][ -D ][ -DD ][ -e ][ -i ][ -k ] [ -K statefile ][ -n ][ -p ][ -P ][ -q ][ -r ][ -s ][ -S ][ -t ] [ -V ][ target ... ][ macro=value... ] make: Fatal error: Unkno...

...e archive. c) one example - stats.so currently the command to make stats.so is: gcc -Wl,-bnoquiet -std=gnu99 -shared -Wl,-brtl -Wl,-G -Wl,-bexpall -Wl,-bnoentry -o stats.so init.o kmeans.o ansari.o bandwidth s.o chisqsim.o d2x2xk.o fexact.o kendall.o ks.o line.o smooth.o prho.o swilk.o ksmooth.o loessc.o monoSpl.o isoreg.o Srunmed.o d blcen.o distance.o hclust-utils.o nls.o rWishart.o HoltWinters.o PPsum.o arima.o burg.o filter.o mAR.o pacf.o starma.o port.o fa mily.o sbart.o approx.o loglin.o lowess.o massdist.o splines.o lm.o complete_cases.o cov.o deriv.o fft.o fourier.o model.o optim .o optim...

On 2015-10-15 15:02, Prof Brian Ripley wrote: > On 15/10/2015 13:32, Michael Felt wrote: >> Hi. >> >> Just wanted to let you know I am getting close to packaging R for AIX in rephrase - would like to be active in keeping R binaries current for AIX. My interest in not in R per se (rather a colleague who has a project that uses R, so I hope to assist him, and others like him).

...ul, the tail end of make follows. Does anyone have any experience with that? Thanks a lot in advance for any suggestions. gcc -std=gnu99 -shared -L/usr/local/lib -o stats.so init.o kmeans.o ansari.o bandwidths.o chisqsim.o d2x2xk.o fexact.o kendall.o ks.o line.o smooth.o prho.o swilk.o ksmooth.o loessc.o isoreg.o Srunmed.o Trunmed.o dblcen.o distance.o hclust-utils.o nls.o HoltWinters.o PPsum.o arima.o burg.o filter.o mAR.o pacf.o starma.o port.o family.o sbart.o approx.o loglin.o lowess.o massdist.o splines.o bsplvd.o bvalue.o bvalus.o loessf.o ppr.o qsbart.o sgram.o sinerp.o sslvrg.o stxwx.o hc...

...it goes I am trying to find Loess. I could not find it on the windows version. Is there one in either Unix version of R or some C program somewhere? I tried one from http://netlib.bell-labs.com/netlib/a/, but I cannot get it to compile due to problem with missing lib (I think): cc -o gas.x gas.o loessc.o loess.o predict.o misc.o loessf.o -llinpack -lcor -lm -lF77 ld: fatal: library -llinpack: not found ld: fatal: library -lcor: not found ld: fatal: File processing errors. No output written to gas.x *** Error code 1 make: Fatal error: Command failed for target `gas.x' In addition, I cannot...

Recent sensible changes to the dynload mechanism have made an old problem resurface: how should we deal with packages which contain Fortran code and may need to be linked against additional libraries such as -lf2c? The current consensus is that extra Fortran libraries maybe needed are handled via the make variable FLIBS, and that `-lf2c' or `-lg2c' are added by default if g77 is used.

...96 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]]

Hello All, In some package I use a c-routine which calls a fortran routine which expects a char-string as input. As per the writing R-extensions manual, the Fortran routine is declared in C as: void F77_NAME (setoptions) (char **option); and then it is calles as follows: char **option; option = new char*[1]; option[0] = new char[256]; option[0] = strcpy(option[0],"Iteration

...and Gnu make 3.76-1. On several occasions, the make process aborted when trying to build the shared object file for the modreg package (its first attempt at such a beast). In all attempts, the error message is as follows: ../../../../bin/R SHLIB -o modreg.so bsplvd.o bvalue.o bvalus.o ksmooth.o loessc.o loessf.o ppr.o qsbart.o sbart.o sgram.o sinerp.o sslvrg.o stxwx.o make: Fatal error: Unknown option `-w' gmake[4]: *** [modreg.so] Error 1 gmake[4]: Leaving directory `/tmp/R-0.64.1/src/library/modreg/src' In addition, I got the following error messages in this directory on the latest a...

...ariables used from the R engine. The current scheme is to assume that all exposed variables are intended to be imported. (Can f1 and f2 in approx.c be declared static?) (2) Problems mixing Fortran and C. > > The messages are then not very clear, because loessf.f passes strings > > to loessc.c to call the warning/stop routines, and in Windows (but not > > Unix) those strings seem to be missing a '\0' terminator. So you gets of > > the next string, .... That will need rather more extensive changes to fix. The problem here is that the loess code (not mine!) assumes t...

...vd.o f77 -g -fpe3 -fpic -c bvalue.f -o bvalue.o f77 -g -fpe3 -fpic -c bvalus.f -o bvalus.o f77 -g -fpe3 -fpic -c dpbfa.f -o dpbfa.o f77 -g -fpe3 -fpic -c dpbsl.f -o dpbsl.o gcc -ieee_with_inexact -g -I../../../../include -c ksmooth.c -o ksmooth.o gcc -ieee_with_inexact -g -I../../../../include -c loessc.c -o loessc.o f77 -g -fpe3 -fpic -c loessf.f -o loessf.o f77 -g -fpe3 -fpic -c ppr.f -o ppr.o f77 -g -fpe3 -fpic -c qsbart.f -o qsbart.o f77 -g -fpe3 -fpic -c sbart.f -o sbart.o fort: Info: sbart.f, line 164: No path to this statement 23012 continue ^ f77 -g -fpe3 -fpic -c sgram.f -o sgram.o f77 -g...