search for: fb2

Dear All, I am analysing some data for a colleague (not my data, gotta be published so I cannot divulge). My response variable is the number of matings observed per day for some fruitlies. My factors are: Day: the observations were taken on 9 days Regime: 3 selection regimes Line: 3 replicates per selection regime. I have 81 observations in total The lines are coded A to I, so I do not need

I'm scoping out HA for a relatively simple Office/Call Center PBX. Current setup uses a TE412P with 4 PRI our telco with SIP hard/soft phones for users. Some outbound also goes to a SIP provider. Active/Active looks to be too much hassle for an installation this size, so we're looking at adding an extra * in an active/passive configuration with Linux-HA in between them. Does anyone

...in 1:r){ int1<-function(x1){ int_1<- (1/p+log(x1/lamda))^2 * j * choose(n,j) * (pweibull(x1,shape=p,scale=lamda))^(j-1) * (1 - pweibull(x1,shape=p,scale=lamda))^(n-j) * dweibull(x1,shape=p,scale=lamda) int_1 } v1[j]<-integrate(int1,lower=0,upper=t)$value } sum(v1) } #calculation for t2 fb2<-function(t,r){ v2<-numeric(0) for(j in 1:r){ int2<-function(x2){ int_2<- (1/p+log(x2/lamda))*(-p/lamda) * j * choose(n,j) * (pweibull(x2,shape=p,scale=lamda))^(j-1) * (1 - pweibull(x2,shape=p,scale=lamda))^(n-j) * dweibull(x2,shape=p,scale=lamda) int_2 } v2[j]<-integrate(int2,lower...

...ect$xlevels) : variable lengths differ (found for 'fGRAZE') In addition: Warning message: 'newdata' had 13 rows but variable(s) found have 56 rows I hope anyone has an idea. Thank you in advance. Heike -- Heike Schmitz- Diaspero Population Ecology and Evolutionary Ecology Lab, FB2 University of Bremen Leobener Strasse, Nw2, Room B4050 D-28359 Bremen Germany fon ++49-421-218-62937 email: heike.schmitz at uni-bremen.de http://www.popecol.uni-bremen.de

I have only verified the fix on Debian 7. The Debian 6 guest doesn't appear to boot, I'm not sure why. The second patch contains a test suite. Rich.

In thinking about this we could use a Mutex::tryacquire(...) (non-recursive), around JIT::runJITOnFunctionUnlocked(...)'s while loop, and use your JITEmitter:: getLazyFunctionStub(...) suggestion in place of forceEmitFunctionStub(...). Is the lock attempt too heavy, even if it is implemented with atomics? I'll implement this when I have time. Garrison On Feb 17, 2010, at 15:42, Garrison

Hi all, yesterday we had a drive failure on a fc-al jbod with 14 drives. Suddenly the zpool using that jbod stopped to respond to I/O requests and we get tons of the following messages on /var/adm/messages: Sep 3 15:20:10 fb2 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk at g20000004cfd81b9f (sd52): Sep 3 15:20:10 fb2 SCSI transport failed: reason ''timeout'': giving up "cfgadm -al" or "devfsadm -C" didn''t solve the problem. After a reboot ZFS recognized the...

Hi Olivier, Thanks for responding! I get to learn this way. On Feb 17, 2010, at 12:50, Olivier Meurant wrote: > Hi Garrison, > > I am not a specialist of the code but here is my 2 cents: > > - I like the idea that in lazy-mode the call (in module or not) is treated by a stub (like every calls). If we go further with this, I'll have to add test cases for lazy mode. I kind

https://bugs.freedesktop.org/show_bug.cgi?id=70388 Priority: medium Bug ID: 70388 Assignee: nouveau at lists.freedesktop.org Summary: [NV34] failed to idle channel 0xcccc0000 Severity: critical Classification: Unclassified OS: Linux (All) Reporter: rosti.bsd at gmail.com Hardware: x86 (IA32)