About Kazzie

Kazzie · ‎02-12-2019

As already pointed out, this is probably a data issue. I encountered the same warning and for me the problem was so-called perfect separation (a lot can be found by simply googling this term). Loosely explained, this means that for a certain categorical variable, one or more categories / groups only have data for either your success or non-success group. For example: Variable color that can take on Blue, red, yellow. Y = 1 (success): Blue 100, red 50, yellow 50 Y = 0 (fail / non-success): Blue = 50, red = 100, yellow = 0 For the Yellow group, there are only successes. HTH

Kazzie · ‎01-09-2019

Thanks for the code and your advice. I indeed accepted the solution from @Astounding Yours however is very useful for my overall understanding!

Kazzie · ‎01-09-2019

Dear experts, First, I am on version 7.1. The following simple example, I would like to make it more flexible / dynamic: PROC SQL; SELECT MAX(Var1) , MAX(Var2) , Max(Var3) FROM My_Table ; QUIT; To make it more dynamic: %LET Variable_List = Var1 Var2 Var3; PROC SQL; SELECT MAX(&Variable_List) FROM My_Table ; QUIT; This however doesn't work, but I'd like it to function as the first manually written statement. And it should also be flexible in the way that if I give in 4 or 5 variables (var4 var5), that it will still work. This can probably be solved by using a %Do loop, but I haven't been able to make it work. Could you give me some advice on how to do this? Thank you!

Online Status	Offline
Date Last Visited	‎02-14-2019 05:57 AM

Re: Ridging has failed to improve likelihood function: Proc Logistics

Re: Dynamically coding using PROC SQL to select dynamic number of colu...

Dynamically coding using PROC SQL to select dynamic number of columns

Re: Ridging has failed to improve likelihood function: Proc Logistics

Re: Dynamically coding using PROC SQL to select dynamic number of colu...

Dynamically coding using PROC SQL to select dynamic number of columns