similar to: mChoice prb in rms

Displaying 20 results from an estimated 700 matches similar to: "mChoice prb in rms"

2010 Apr 09
0
Trouble with mChoice() in the Hmisc package.
Hi All:-- I've started using the the Hmisc reporting facilities recently, mostly successfully. I'm having some trouble with mChoice() multiple-choice objects, though. Here's some example code and output from R-help a couple of years ago: library(Hmisc) Symptom1 <- c("Headache", "Headache", NA) Symptom2 <- c(NA, "Anxiety", NA) Symptoms <-
2010 Aug 29
2
glm prb (Error in `contrasts<-`(`*tmp*`, value = "contr.treatment") : )
glm(A~B+C+D+E+F,family = binomial(link = "logit"),data=tre,na.action=na.omit) Error in `contrasts<-`(`*tmp*`, value = "contr.treatment") : contrasts can be applied only to factors with 2 or more levels however, glm(A~B+C+D+E,family = binomial(link = "logit"),data=tre,na.action=na.omit) runs fine glm(A~B+C+D+F,family = binomial(link =
2010 Aug 31
1
summary in Hmisc and Latex
Dear all, With the latest update of Hmisc I no longer have any problems with latex. However using the ctable option produces latex code that at least on both the miktex distribution at work and mactex distribution at home refuses to run due to an extra blank line inserted between the multicolumn lines in the latex code... It runs fine if the line is deleted or if the ctable option is left out.
2016 Apr 19
0
mount cifs
Found some more info: mount.cifs to mount shares from my DCs (samba 4.2.11) works mount.cifs to mount shares from smbserver (also 4.2.11) does NOT work. Here is the debug log it produces: > root at epo:/proc/fs/cifs# mount.cifs //smbserver.domain.com/share /mnt -o username=username,domain=WRKGRP,sec=ntlmsspi > Password: > Apr 19 15:19:58 epo kernel: [74522.479080]
2016 Apr 19
3
mount cifs
On 04/19/2016 8:39 AM, lists wrote: > Found some more info: > > mount.cifs to mount shares from my DCs (samba 4.2.11) works > mount.cifs to mount shares from smbserver (also 4.2.11) does NOT work. > > Here is the debug log it produces: > >> root at epo:/proc/fs/cifs# mount.cifs //smbserver.domain.com/share /mnt >> -o username=username,domain=WRKGRP,sec=ntlmsspi
2017 Mar 14
0
AD replication issue
On 3/14/2017 10:29 AM, Arthur Ramsey wrote: > Changes replicate to it, but not from it. > > vsc\VSC-DC02 > DSA Options: 0x00000001 > DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb > DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 > > ==== INBOUND NEIGHBORS ==== > > DC=DomainDnsZones,DC=mediture,DC=dom > vsc\DC01 via RPC >
2017 Mar 14
2
AD replication issue
Changes replicate to it, but not from it. vsc\VSC-DC02 DSA Options: 0x00000001 DSA object GUID: fe066b13-6f9e-4f3c-beb4-37df1292b8cb DSA invocationId: 8a2b1405-07b1-4d92-89dd-1d993e59e378 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom vsc\DC01 via RPC DSA object GUID: da9bb168-47a0-4368-aff3-bf06d1b869d2 Last attempt @ Tue Mar 14
2017 Mar 13
0
AD replication issue
Upgraded to 4.6.0 on all nodes. Still seeing the same issue. If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't replicate. If I create it on vsc-dc01 (PDC emulator) then it does replicate. On 03/13/2017 12:13 PM, Arthur Ramsey wrote: > > I believe the problem is a lack of outbound replication for non PDC > emulator DCs. You'll notice isn't even
2017 Mar 13
0
AD replication issue
That bug is reported? Do you have a link? You're saying it is just an issue with the logging or am I correct that this indicates an outbound replication isn't trying. On 03/13/2017 01:45 PM, lingpanda101 via samba wrote: > On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: >> Upgraded to 4.6.0 on all nodes. Still seeing the same issue. >> >> If I create an
2014 Jul 23
1
sssd problems after dc1 is no longer online
Hi all, I hope that this request for help will be the last one, for a while to come. Today, sernet support helped my sort out our DC mess, and they did a great job. However, sssd no longer works, and I hope someone here can help out. We used to have DC1, DC2 and DC3. DC1 was the classic-upgraded, first, 'original' DC, and had to be shutdown, unfortunately. So only DC2 and DC3
2017 Mar 13
3
AD replication issue
On 3/13/2017 2:15 PM, Arthur Ramsey via samba wrote: > Upgraded to 4.6.0 on all nodes. Still seeing the same issue. > > If I create an object on vsc-dc02, epo-dc01 or aws-dc01 DCs it doesn't > replicate. If I create it on vsc-dc01 (PDC emulator) then it does > replicate. > > On 03/13/2017 12:13 PM, Arthur Ramsey wrote: >> >> I believe the problem is a lack
2017 Mar 13
2
AD replication issue
I believe the problem is a lack of outbound replication for non PDC emulator DCs. You'll notice isn't even trying because last successful was epoch (never) yet there are no errors. Inbound replication for this DC seems fine. [root at vsc-dc02 ~]# samba-tool drs showrepl [...]==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=mediture,DC=dom aws\AWS-DC01 via RPC DSA object GUID:
2007 Apr 25
2
Coercing data types for use in model.frame
In the Hmisc package there is a new data class 'mChoice' for multiple choice variables. There are format and as.numeric methods (the latter creates a matrix of dummy variables). mChoice variables are not allowed by model.frame. Is there a way to specify a conversion function that model.frame will use automatically? I would use as.factor here. model.frame does not seem to use
2007 Apr 25
2
Coercing data types for use in model.frame
In the Hmisc package there is a new data class 'mChoice' for multiple choice variables. There are format and as.numeric methods (the latter creates a matrix of dummy variables). mChoice variables are not allowed by model.frame. Is there a way to specify a conversion function that model.frame will use automatically? I would use as.factor here. model.frame does not seem to use
2008 Oct 08
1
NA's in multiple choice summary table in Hmisc
Hi, I have a set of 30 binary variables measuring side effects after drug treatment. Since each subject can have multiple side effects, I want to display these side effects in a multiple choice table. I'm using the summary and mChoice functions of the Hmisc package, because it produces nicely formatted latex tables. My problem is, that table includes a category for people who have at
2010 Jun 18
1
Latex problem in Hmisc (3.8-1) and Mac Os X with R 2.11.1
Dear all, I did post this more or less identical mail in a follow up to another question I posted, but under another heading. I try again, but now under the correct header. upon running this code (from the Hmisc library-latex function) I believe the call to summary.formula is allright and produces wonderful tables, but the latex command results in a correct formatted table but where all the
2011 Apr 27
1
ctree and survival problem
Dear all, I was intrigued by the ctree command and wanted to check it out. I first ran the demo with example(ctree) and did get the survival graphs in the end. Upon doing this with my own data and yielding a "Invalid operation on a survival time" I tried to rerun example(ctree) and now I also get "Invalid operation on a survival time" after the example runs plot(GBSG2ct)...
2024 Oct 25
0
Could not find a suitable mechtype in NEG_TOKEN_INIT error in libsmbclient 4.19.4
> >> Looking at the packet captures, when its working on libsmbclient 4.10, >> it first sends a SMB1 negotiate protocol request, to which server >> sends back a SMB2 response. Then there is a SMB2 negotiate protocol >> request/response again. >> >> In 4.19, there is a SMB2 client negotiate protocol request >> straightaway and to which the server
2017 Mar 13
5
AD replication issue
I forgot to associate inter-site links (all using default), which fixed a lot though I'm still having an issue. * vsc site o vsc-dc01 o vsc-dc02 * aws site o aws-dc01 * epo site o epo-dc01 * vsc-dc01 => anywhere: OK * vsc-dc02 => anywhere: not replicating * aws-dc01 => anywhere: OK * epo-dc01 => anywhere: OK I've tried with samba_kcc =
2012 Mar 08
18
some fixes, improvements, and new features (EPO and DYING) for NUT
Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by