You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Within concordancefit(), the "Special trickery for matched case-control data" involves changing the y to create disjoint time intervals, but then the ymax argument (and presumably also ymin) do not have the intended effect.
For example, in all the following ymax > max(dfr$ptime) so expect same result as without setting ymax, but the correct result is returned only when keepstrata = TRUE (and the "special trickery" is not used).
Good catch. I hadn't thought about ymax/ymin when doing the 'trickery' code.
In my defense, I can't think of a case where I would want to use ymin or ymax in case-control data. Could you give some context, just for my education? (It's still a bug.)
Within
concordancefit()
, the "Special trickery for matched case-control data" involves changing they
to create disjoint time intervals, but then theymax
argument (and presumably alsoymin
) do not have the intended effect.For example, in all the following
ymax > max(dfr$ptime)
so expect same result as without settingymax
, but the correct result is returned only whenkeepstrata = TRUE
(and the "special trickery" is not used).The text was updated successfully, but these errors were encountered: