similar to: Labeling matrix data

Dear r helpers I run the following code for nested logit and got a message that Error in optim(c(0, 0, 0, 0, 0.1, -2, -0.2), fr, hessian = TRUE, method = "BFGS") : initial value in 'vmmin' is not finite What does this mean? and how can I correct it? Thank you June > yogurt = read.table("yogurtnp.csv", header=F,sep=",")> attach(yogurt)>

Dear Rhelpers I have the problem with initial values, could you please tell me how to solve it? Thank you June > p = summary(maxLik(fr,start=c(0,0,0,1,0,-25,-0.2))) Error in maxRoutine(fn = logLik, grad = grad, hess = hess, start = start, : NA in the initial gradient > p = summary(maxLik(fr,start=c(0,0,0,1,0,-25,-0.2),method="BFGS")) Error in optim(start, func, gr =

Hi, folks, Please first look at the codes: plan_a=c('apple','orange','apple','apple','pear','bread') plan_b=c('bread','bread','orange','bread','bread','yogurt') value=1:6 data=data.frame(plan_a,plan_b,value) library(plyr) library(reshape) mm=melt(data, id=c('plan_a','plan_b'))

Hi All, I've been having a little trouble with creating a loop that will run a a series of t.tests for inspection, Below is the code i've tried, and some checks i've looked at. I've used the get(paste()) idea as i was told previously that the use of the eval should try and be avoided. I've run a single syntax to check that my systax is correct and works without any problems

Recent SUP. Installed on Dell PowerEdge 4600. Getting tons of: Sep 30 12:23:16 zige /kernel: bge0: gigabit link up Sep 30 12:23:46 zige last message repeated 98 times Also getting some TCP retransmits. This causes noticable delays in pretty much everything I do now. Not a problem prior to the SUP. I was on 4.8-STABLE before. When pulling/replacing cables, it went into a mode where it would

On Fri, Feb 27, 2015 at 2:59 PM, Chris Murphy <lists at colorremedies.com> wrote: > On Fri, Feb 27, 2015 at 1:53 PM, Robert Arkiletian <robark at gmail.com> > wrote: > > Still have good quality older sata hardware raid cards that require 512 > > bytes/sector. As far as I know HD manufacturers are not making native 512 > > bytes/sector drives any more. > >