UACR/TI 90days - continuous N=1 - error

[romainkp]

UACR/TI 90days - continuous N=1 - error

[osofr]

Have you tried non-h20 glm? It appears that the glm call is resulting in the error, which is what being captured by "try-error". Most likely explanation is due to 0 observations for some bins.

[romainkp]

You are correct. Glm works and shows that there are no events under any of
the rules and that is because we filled in the last N before an even with
0 artificially. I will instead fill it with 1.

We might want to add a check that the outcome in the final regression is
not constant at any given value and stop the program elegantly in such
cases. Not a priority

NOTICE TO RECIPIENT: If you are not the intended recipient of this
e-mail, you are prohibited from sharing, copying, or otherwise using or
disclosing its contents. If you have received this e-mail in error,
please notify the sender immediately by reply e-mail and permanently
delete this e-mail and any attachments without reading, forwarding or
saving them. Thank you.

From: Oleg Sofrygin [email protected]
To: osofr/stremr [email protected]
Cc: Romain S Neugebauer/CA/KAIPERM@KAIPERM, Author
[email protected]
Date: 06/24/2016 10:59 AM
Subject: Re: [osofr/stremr] UACR/TI 90days - continuous N=1 - error
(#12)

Caution: This email came from outside Kaiser Permanente. Do not open
attachments or click on links if you do not recognize the sender.

Have you tried non-h20 glm? It appears that the glm call is resulting in
the error, which what being captured. Most likely explanation is due to 0
observations for some bins.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.