search for: fp2

Dear all, I have the following problem with the uniroot function. I want to find roots for the fucntion "Fp2" which is defined as below. Fz <- function(z){0.8*pnorm(z)+p1*pnorm(z-u1)+(0.2-p1)*pnorm(z-u2)} Fp <- function(t){(1-Fz(abs(qnorm(1-(t/2)))))+(Fz(-abs(qnorm(1-(t/2)))))} Fp2 <- function(t) {Fp(t)-0.8*t/alpha} th <- uniroot(Fp2, lower =0, upper =1, tol = 0.0001)...

...a new dataframe that contains only these. These observations are not numerical, so I can't use the subset() function (at least this is the response I get from R). Suppose the dataframe looks like this:   ParticipID    ERP   Electrode 1         s1  0.0370       FP1 2         s2 35.0654       FP2 3         s3 -3.3852        F4 4         s4  2.6119        P3 5         s5  0.1224        P4 6         s6 -5.3153        O1 I want to create a subset of the dataframe with only the FP1, FP2, F4 levels of Electrode, how do I do? (actually the levels I have to filter are much more than these three...

Hi Chandler, this seems sound to me. For example, consider running function passes. Currently it works like this: if you schedule two function passes in succession, FP1 and FP2, then for each function F, FP1 is run on F then FP2 is run on F. In your new scheme, if you schedule FP1 followed by FP2, then each will act as a module pass and thus: for each function F, FP1 is run on F. Once this is done, then for each function F, FP2 is run on F. Two get the previous schedul...

...; effect is not as good as usual. > > int main() > { >     int err; >     SpeexResamplerState *speex_resampler; >     speex_resampler = speex_resampler_init(1, 16000, 48000, 10, &err); >     FILE *fp = fopen("/data/zhou.wav", "rb+"); >     FILE *fp2 = fopen("/data/zhou2.wav", "ab+"); >     spx_int16_t inbuff[640] = {0}; >     spx_int16_t outbuff[1920] = {0}; >     spx_uint32_t inlen = 640; >     spx_uint32_t outlen = 1920; >     while (1) >     { >         speex_resampler_reset_mem(speex_resample...

...napshots are inefficient. If you update only modified blocks, snapshots on COW filesystem takes far less space. I tested with an ugly program I wrote that does that, and it works well. #include <stdio.h> #include <stdlib.h> int main(int argc, char *argv[]) { FILE *fp1; FILE *fp2; char *oldfile = argv[1]; char *newfile = argv[2]; fp1 = fopen(oldfile, "rb+"); if(fp1 == NULL) { perror("failed to open 1"); return EXIT_FAILURE; } fp2 = fopen(newfile, "rb"); if(fp2 == NULL) { perror("failed...

...(result,z) auc<-performance(rocpreds,"auc")@y.values sentiv<-performance(rocpreds,"sens")@y.values sentiv<-slot(fp,"y.values")[[1]] sentiv<-sentiv[2] sentiv specs<-performance(rocpreds,"spec")@y.values specs<-slot(fp2,"y.values")[[1]] specs<-specs[2] specs output<-c(int,slope,.5,accuracy,auc,sentiv,specs) names(output)<-c("Intercept","Slope","CutPoint","Accuracy","AUC","Sentivity",Specificity") return(output) }...

Greetings folks! In working on a new optimization pass (splitting cold regions into separate functions based on branch probabilities) I've run into some limitations of the current pass manager infrastructure. After chatting about this with Nick, it seems that there are some pretty systematic weaknesses of the current design and implementation (but not with the fundamental concepts or

...= 1.0)) Error in nlme.formula(weight ~ SSlogis(Time, Asym, xmid, scal), data = Soybean, : Maximum number of iterations reached without convergence Execution halted I presume that `R CMD check MASS' fails for some similar reason. The final output in MASS-Ex.Rout is: > library(nlme) > fp2 <- deriv(~ 0.5 + 0.5/(1 + exp(-(x-L75)/2)), + "L75", function(x,L75) NULL) > OMEi.nls <- nlsList(Correct/Trials ~ fp2(Loud, L75) | UIDn, + data = OMEi, start=list(L75=45), control = list(maxiter=100)) Error in nls(formula = formula, data = data, start = start, con...

...a general load and general store. Also, on the so-called "Book E" embedded PPC cores, the sync instruction is called msync (same opcode, different name). I'm not sure what the best way of doing a predicate-base asm name is. I'm just about done with a patch to add support for the FP2 (aka Double Hummer) v2f64 vector instruction set, but I figured that it would be good to make that a separate patch. Thanks in advance, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory -------------- next part -------------- A non-text attachment...

Hi, people. I met a little problem for which someone might have a solution. Let's say I have an executable file (named "pp.R") with this contents: #!/usr/bin/Rscript options(echo=TRUE) a <- 1 Sys.sleep(3) a <- 2 If I execute "./pp.R" at the shell prompt, the output shows the timely progress of the script as expected. If I use "./pp.R | tee

...nc instruction > is called msync (same opcode, different name). I'm not sure what the > best way of doing a predicate-base asm name is. I am not sure how to do that. X86 has alternative syntaxes, but that is way overkill. > I'm just about done with a patch to add support for the FP2 (aka Double > Hummer) v2f64 vector instruction set, but I figured that it would be > good to make that a separate patch. Definitely. /jakob

...; expected - the callee now indeed saved/restored all the xmm regs I >> added, however the calling code did not change at all... > > Look in X86InstrControl.td. The call instructions are all prefixed > by: > > let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, > FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, > XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, > XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], > > This is the fixed list of call-clobbered registers. It should really > be controlled by...

...incorrectly? please help confirm? > > int main() > { >     SpeexResamplerState *speex_resampler; >     int err; >     speex_resampler = speex_resampler_init(1, 16000, 48000, 10, &err); >     FILE *fp = fopen("/data/zhou.wav", "rb+"); >     FILE *fp2 = fopen("/data/zhou2.wav", "ab+"); >     spx_int16_t inbuff[640] = {0}; >     spx_int16_t outbuff[1920] = {0}; >     spx_uint32_t inlen = 640; >     spx_uint32_t outlen = 1920; >     speex_resampler_skip_zeros(speex_resampler); >     while (1) >     {...

Hi, How do I create function pointers in LLVM? Is it possible to assign a function to a function pointer? Thanks

On Oct 20, 2010, at 7:46 AM, Roland Scheidegger wrote: > On 20.10.2010 05:00, Jakob Stoklund Olesen wrote: >> Look in X86InstrControl.td. The call instructions are all prefixed >> by: >> >> let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, >> FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, >> XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, >> XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], >> >> This is the fixed list of call-clobbered registers. It should really &g...

I have a puppet master on Centos 6.3 connected and working properly with other Centos 6.3 agent. I installed puppet agent via gems on a RED HAT 4 node. This is what happens when I try to sign certificate for the new node: AGENT [root@FP2 ~]$ puppet agent -t Info: Creating a new SSL key for fp2 Info: Caching certificate for ca Info: Creating a new SSL certificate request for fp2 Info: Certificate Request fingerprint (SHA1): 35:51:A0:12:CF:2E:F7:73:22:C3:5E:51:DC:03:AF:4C:FC:54:5C:10 Exiting; no certificate found and waitforcert...

...0, 2010, at 7:46 AM, Roland Scheidegger wrote: > >> On 20.10.2010 05:00, Jakob Stoklund Olesen wrote: >>> Look in X86InstrControl.td. The call instructions are all prefixed >>> by: >>> >>> let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, >>> FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, >>> XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, >>> XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], >>> >>> This is the fixed list of call-clobbered registers....

...9;t what I > expected - the callee now indeed saved/restored all the xmm regs I > added, however the calling code did not change at all... Look in X86InstrControl.td. The call instructions are all prefixed by: let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], This is the fixed list of call-clobbered registers. It should really be co...

Thanks for giving it a look! On 19.10.2010 23:21, Jakob Stoklund Olesen wrote: > On Oct 19, 2010, at 11:40 AM, Roland Scheidegger wrote: > >> So I saw that the code is doing lots of register >> spilling/reloading. Now I understand that due to calling >> conventions, there's not really a way to avoid this - I tried using >> coldcc but apparently the backend

...;, %AL<kill>, %RAX<imp-def>, %RCX<imp-def,dead>, %RDX<imp-def,dead>, %RSI<imp-def,dead>, %RDI<imp-def,dead>, %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp-def,dead>, %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, %FP6<imp-def,dead>, %ST0<imp-def,dead>, %ST1<imp-def,dead>, %MM0<imp-def,dead>, %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, %MM4<imp-def,de...