Displaying 20 results from an estimated 21 matches for "mcb".
Did you mean:
mb
2002 Aug 14
0
: use of Error() for repeated measures with more than 2 factors
...Notes on the use of R for psychology experiments and
questionnaires" by Jonathan Baron and Yuelin Li (see the example of Hay's)
I have found that there seems to be a limit, in the number of factors in
Error() . For example, the following worked :
aov(CV ~(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb+Mom0b+Mom1b+Mom2b+Mom3b)^3 +
Error(Batch /
(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb)),simulation.6batches.aovdata)
but not:
aov(CV ~(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb+Mom0b+Mom1b+Mom2b+Mom3b)^3 +
Error(Batch /
(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb+Mom0b+Mom1b)),simulation.6batches.aovdata)
which I suppo...
2002 Aug 19
0
: Bug in Error() and the use of Error() for repeated measures with more than 2 fa ctors
...39;s)
>>
>>>>>
>>>>> I have found that there seems to be a limit, in the number of
>>>>> factors in
>>>>> Error() . For example, the following worked :
>>>>>
>>>>> aov(CV ~(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb+Mom0b+Mom1b+Mom2b+Mom3b)3 +
>>>>> Error(Batch /
>>>>> (Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb)),simulation.6batches.aovdata)
>>>>>
>>>>> but not:
>>>>>
>>>>> aov(CV ~(Twb+Plb+Psb+tinsb+tseedb+Tmb+Mcb+Mom0b+Mom1b+Mom...
2010 Nov 13
2
interpretation of coefficients in survreg AND obtaining the hazard function for an individual given a set of predictors
...or me, from ?survreg.objects how to.
Here is an example of the codes that points out my problem:
- data is stc1
- the factor is dichotomous with 'low' and 'high' categories
slr <- Surv(stc1$ti_lr, stc1$ev_lr==1)
mca <- coxph(slr~as.factor(grade2=='high'), data=stc1)
mcb <- coxph(slr~as.factor(grade2), data=stc1)
mwa <- survreg(slr~as.factor(grade2=='high'), data=stc1, dist='weibull',
scale=0)
mwb <- survreg(slr~as.factor(grade2), data=stc1, dist='weibull', scale=0)
> summary(mca)$coef...
2010 Nov 15
1
interpretation of coefficients in survreg AND obtaining the hazard function
...or me, from ?survreg.objects how
to.
Here is an example of the codes that points out my problem:
- data is stc1
- the factor is dichotomous with 'low' and 'high' categories
slr <- Surv(stc1$ti_lr, stc1$ev_lr==1)
mca <- coxph(slr~as.factor(grade2=='high'), data=stc1)
mcb <- coxph(slr~as.factor(grade2), data=stc1)
mwa <- survreg(slr~as.factor(grade2=='high'), data=stc1,
dist='weibull',
scale=0)
mwb <- survreg(slr~as.factor(grade2), data=stc1, dist='weibull',
scale=0)
> summary(mca)$coef
coef
exp(coef) se(coef)...
2010 Nov 16
1
Re : interpretation of coefficients in survreg AND obtaining the hazard function for an individual given a set of predictors
...> Here is an example of the codes that points out my problem:
> - data is stc1
> - the factor is dichotomous with 'low' and 'high' categories
>
> slr <- Surv(stc1$ti_lr, stc1$ev_lr==1)
>
> mca <- coxph(slr~as.factor(grade2=='high'), data=stc1)
> mcb <- coxph(slr~as.factor(grade2), data=stc1)
> mwa <- survreg(slr~as.factor(grade2=='high'), data=stc1, dist='weibull',
> scale=0)
> mwb <- survreg(slr~as.factor(grade2), data=stc1, dist='weibull', scale=0)
>
>> summary(mca)$coef
>...
wine errors out (non-game) with err:int:EMS_Ioctl_Handler int21: unknown/not implemented parameters:
2007 Jan 23
1
wine errors out (non-game) with err:int:EMS_Ioctl_Handler int21: unknown/not implemented parameters:
Using wine-0.9.29 with paradox 3.5, I receive the following errors:
c:\pdox35>paradox
Warning: unprotecting memory to allow real-mode calls.
NULL pointer accesses will no longer be caught.
err:dosmem:DOSMEM_FreeBlock MCB invalid
Cannot load PARADOXR.EXE
err:dosmem:DOSMEM_FreeBlock MCB invalid
Running paradoxr.exe, I get:
c:\pdox35>paradoxr
Warning: unprotecting memory to allow real-mode calls.
NULL pointer accesses will no longer be caught.
err:int:EMS_Ioctl_Handler int21: unknown/not implemented par...
2001 Apr 06
0
./configure can't find zlib
...ocal/openssh
--with-ssl-dir=/usr/local/ssl/lib \
--with-lastlog=/usr/var/adm/lastlog
Somehow, my understanding of the desired syntax is off - What am I doing
wrong?
Thanx for any help you
can give,
S. McB.
2003 May 06
0
supply electric appliances
...-577-88776861 or 88776862
E-mail:qunze@mail.wzptt.zj.cn chnze@mail.wzptt.zj.cn
http://www.chnze.com; http://www.electricbase.com
Dear Sir,
We are pleased to introduce ourselves as leading manufacturers and
exporters in Electrical Items and Accessories. Our Products include:
1. Circuit breaker (MCB,ELCB,MCCB)
2. Ac contactor, Magnetic starter
3. Relays (Mini relay, time relay, thermal relay)
4. Meters(panel meter, water meter, watthour meters)
5. Fuses link and fuse base
6. Stablizer, UPS(uninterruptible power supply)
7. Energy saving lamps
8. Nylon cable tie, Cable clips,terminal block
9. Mi...
2003 Nov 13
1
Authentication against AD
...vel = 3
debug level = 1
wins server = <Our wins-servers>
dns proxy = no
I want a www-share something like this:
[www]
comment = Webfiles
path = /www
public = no
writeable = yes
browseable = yes
force user = www
force group = www
valid users = uib\mcb, uib\nkjmb, student\st01654
But it doesn't work, and I suspect it's the valid users that doesn't
understand the domain\ part.
Any ideas on how I can accomplish what I want?
Some info:
The server is a part of the KJ-domain, which is under the UIB-domain
in AD. The users are in the UI...
2009 Oct 23
7
cryptic vdev name from fmdump
This morning we got a fault management message from one of our production servers stating that a fault in one of our pools had been detected and fixed. Looking into the error using fmdump gives:
fmdump -v -u 90ea244e-1ea9-4bd6-d2be-e4e7a021f006
TIME UUID SUNW-MSG-ID
Oct 22 09:29:05.3448 90ea244e-1ea9-4bd6-d2be-e4e7a021f006 FMD-8000-4M Repaired
2016 Apr 29
2
Backtrace:dovecot/imap
...ized out>, mbox=0x7f572c12b840)
at imapc-mailbox.c:473
msgmap = 0x7f572c146ed0
lseq = 739349904
uid = 51497
rseq = 126
#3 0x00007f5729a77632 in imapc_storage_client_untagged_cb (
reply=0x7ffdc857e400, context=0x7f572c0f7080) at imapc-storage.c:204
mcb__foreach_end = 0x7f572c12bf98
client = 0x7f572c0f7080
mbox = 0x7f572c12b840
cb = <optimized out>
mcb = 0x7f572c12bf78
#4 0x00007f5729a7d90a in imapc_connection_input_untagged (
conn=conn at entry=0x7f572c119590) at imapc-connection.c:1144
imap_args...
2016 Apr 29
4
Recent update causes segfault in proxy mode
I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian.
The recent upgrade to 2.2.24 cause the follwoing error to appear:
I can log in to a mailbox via dovecot
I can delete emails
Upon expunge, dovecot crashes:
Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142514, msgid=, size=10086
Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX,
2014 Jul 26
0
[RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
...si/Kconfig
create mode 100644 drivers/msi/Makefile
create mode 100644 drivers/msi/msi.c
diff --git a/drivers/Kconfig b/drivers/Kconfig
index 0e87a34..4d05749 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -176,4 +176,5 @@ source "drivers/powercap/Kconfig"
source "drivers/mcb/Kconfig"
+source "drivers/msi/Kconfig"
endmenu
diff --git a/drivers/Makefile b/drivers/Makefile
index f98b50d..47ae3d1 100644
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -158,3 +158,4 @@ obj-$(CONFIG_NTB) += ntb/
obj-$(CONFIG_FMC) += fmc/
obj-$(CONFIG_POWERCAP) += powerc...
2012 Jun 15
3
doveadm backup panic
using latest auto build didn't help.
this happens only with a specific account.
# doveadm -o imapc_user=----- at domain.com -o imapc_password=---- backup
-u =----- at domain.com -R imapc:
dsync(---- at domain.com): Panic: pool_data_stack_realloc(): stack frame
changed
dsync(---- at domain.com): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x4209a) [0xb762b09a] ->
2010 Nov 06
10
Apparent SAS HBA failure-- now what?
My setup: A SuperMicro 24-drive chassis with Intel dual-processor
motherboard, three LSI SAS3081E controllers, and 24 SATA 2TB hard drives,
divided into three pools with each pool a single eight-disk RAID-Z2. (Boot
is an SSD connected to motherboard SATA.)
This morning I got a cheerful email from my monitoring script: "Zchecker has
discovered a problem on bigdawg." The full output is
2014 Aug 20
1
[RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
...akefile
> create mode 100644 drivers/msi/msi.c
>
> diff --git a/drivers/Kconfig b/drivers/Kconfig
> index 0e87a34..4d05749 100644
> --- a/drivers/Kconfig
> +++ b/drivers/Kconfig
> @@ -176,4 +176,5 @@ source "drivers/powercap/Kconfig"
>
> source "drivers/mcb/Kconfig"
>
> +source "drivers/msi/Kconfig"
> endmenu
> diff --git a/drivers/Makefile b/drivers/Makefile
> index f98b50d..47ae3d1 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -158,3 +158,4 @@ obj-$(CONFIG_NTB) += ntb/
> obj-$(CONFIG_FMC)...
2014 Aug 20
1
[RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
...akefile
> create mode 100644 drivers/msi/msi.c
>
> diff --git a/drivers/Kconfig b/drivers/Kconfig
> index 0e87a34..4d05749 100644
> --- a/drivers/Kconfig
> +++ b/drivers/Kconfig
> @@ -176,4 +176,5 @@ source "drivers/powercap/Kconfig"
>
> source "drivers/mcb/Kconfig"
>
> +source "drivers/msi/Kconfig"
> endmenu
> diff --git a/drivers/Makefile b/drivers/Makefile
> index f98b50d..47ae3d1 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -158,3 +158,4 @@ obj-$(CONFIG_NTB) += ntb/
> obj-$(CONFIG_FMC)...
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use
2014 Jul 26
20
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
Hi all,
The series is a draft of generic MSI driver that supports PCI
and Non-PCI device which have MSI capability. If you're not interested
it, sorry for the noise.
The series is based on Linux-3.16-rc1.
MSI was introduced in PCI Spec 2.2. Currently, kernel MSI
driver codes are bonding with PCI device. Because MSI has a lot
advantages in design. More and more non-PCI devices want to
use
2019 Jul 05
0
parse() drops parse data when encountering `` (bug?)
Hi,
I've noticed that partial parse data from parse() is irretrivable when it
errors due to encountering '``' - two backticks in sequence. The print
output also looks more limited than a regular parser error which leads me
to suspect this is a bug. If this is the case could someone with the
authority please add it to R's bug tracker?
My reprex follows.
Thanks,
Miles
``` r