search for: constrait

I''m looking for a R function which can maximise this logliklihood function, under the constraits a>0 e b>0 f<-function(param){ a<-param[1] b <-param[2] log(prod)-(a*s2)-(b*s)-n*log(1-((0.5*b/sqrt(a))*(exp((b^2)/(4*a)))*((sqrt(pi ))*(1-pnorm(-b/(2*sqrt(a)), mean=0, sd=1)))))} I''ve tried maxlik constrOptim e donlp2 but without success. Thanks so much!!...

...ood to know also. Any pointer or advice would be useful. Thank you! Stu ****Original posting***** by <http://www.nabble.com/user/UserProfile.jtp?user=802522> livia Jan 15, 2008; 05:58am Hello everyone, I would like to maximize the following function fqp with linear constraits and the codes are as following: a= c(0.2,0.3,0.4) vcov=matrix(c(1,2,3,4,5,6,7,8,9),3,3) fqp <- function(b) {t(b)%*%a-0.5*((t(b)%*%vcov)%*%b)} constrOptim(c(b1,b2,b3), fqp,NULL,ui=?, ci=?, control=list(fnscale=-1)) The linear constrait is like abs(b1)+ abs(b2)+abs(b3) <= 1.5. How can I...

...his replaces isTwoAddress (according to svn logs), which I gather > > is how > > two-address instructions used to be marked for X86. > > You're right. This is the same as isTwoAddress, just more flexible. Ok, but what are the implications for the rest of llvm? What does this constrait say to later phases? Is it a requirement that all two-address instructions have this constraint or does it just enable more optimization? That is, is functional correctness tied to using this constraint? > > Except isTwoAddress is still used in X86InstInfo.td. > > Because I haven'...

Can someone explain the Constraints system in X86*.td? For example: let Constraints = "$src1 = $dst" This replaces isTwoAddress (according to svn logs), which I gather is how two-address instructions used to be marked for X86. Except isTwoAddress is still used in X86InstInfo.td. So what gives? What do these two properties actually do?

On Jun 17, 2008, at 1:36 PM, David Greene wrote: > Can someone explain the Constraints system in X86*.td? > > For example: > > let Constraints = "$src1 = $dst" > > This replaces isTwoAddress (according to svn logs), which I gather > is how > two-address instructions used to be marked for X86. You're right. This is the same as isTwoAddress, just more