Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Find a Community

- Home
- /
- Analytics
- /
- Stat Procs
- /
- c-Index for GLIMMIX model

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

01-11-2014 06:56 PM

Looking for ideas on how to calculate a c-index for a mixed GLIMMIX model--binary outcome with random effects.

The best I've found so far was to use a weighted average of c-indices from each level of the random variable. Any other leads?

Thanks,

Haris

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

01-13-2014 09:57 AM

This is an area where the literature isn't really settled yet. The weighted average at least overcomes the non-additivity of c (at least for the most part). Are you applying the same number of bins to each level of the random variable? If not, then the weight should also reflect that unequal replication.

Steve Denham

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

01-13-2014 10:55 AM

Here's at least something published on the matter: http://www.statistics.gov.hk/wsc/CPS031-P5-S.pdf.

I am not sure what you mean by "bins to each level of the random variable," can you elaborate? The outcome is binary so there are only two bins at each level (as long as there are some events and non-events). Otherwise, the predictors are all the same.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content

01-13-2014 11:10 AM

Maybe I mis-interpreted what you meant by c-index. I was thinking of c as the area under the ROC, and for that, you need to vary the cutpoint to generate values, and then add them up via the trapezoidal rule (if you are doing it the SAS way). The key is that if you calculate the within cluster ROC values (as per Rahman et al.), you need to be sure that the same number of cutpoints are applied. This is a real problem if the number of 'events' is small within a cluster, and worse if the total number of instances is much smaller in some clusters than in others, so that estimation of the ROC and its associated std error are inexact (see comments on page 5 of Rahman et al.).

Steve Denham