About Reeza

Reeza · ‎08-02-2011

From the SAS DOCs : FORMAT statements are not allowed when the INMODEL= data set is specified; variables in the DATA= and PRIOR= data sets in the SCORE statement should be formatted within the data sets.

Reeza · ‎08-02-2011

Where does that estimates dataset come from? I see the data set XXX and predict have x1 and x2, but the estimates dataset kinda pops up outta nowhere, or is that just a typo for the demo here? Your also missing a semi-colon after the run statement (with the proc sort).

Reeza · ‎07-28-2011

So did you get to give yourself points?

Reeza · ‎07-28-2011

I've noticed that as well about the hazard ratios...it irritates me, I'm sure there's probably a way to change this in the options but I want the CI for the default options, seems obvious enough to me!

Reeza · ‎07-27-2011

Okay, in the 1st regression you're treating your variable as CONTINUOUS when it sounds like its not. This is more valid for variables such as age. The interpretation of the hazard ratio is sometimes hard when its less than 1, but it means for every 1 unit increase in 'group' there is a 0.58 times probability of dying. You can flip the ratio to 1/0.58 and then say for every 1 unit decrease in group there is a 1.7 times increased probability of dying. In the second regression you are treating your variable as CATEGORICAL and comparing one to 2 and 1 to 3. Then the interpretations are between groups rather than per unit increase. If your variables are age groups, ie group 1 is <20 and group 2 is 21 to 40 then this is the type of analysis you should be using. You chose between 1 and 2 depending on the context of your variable, but if you only have 3 levels then I'm guessing its the second method. Why the third doesn't agree, did you use the class variable for it still? Are you missing information for some observation that get included in one and not in another (ie are you sample sizes the same). without more info I can't answer that one. HTH, Reeza

Reeza · ‎07-27-2011

I think you might need to look up PROC SURVEYSELECT, guessing you'll need to code this though, not use the GUI Look up a paper called "Don't be Loopy" on lexjansen.com for sample code.

Reeza · ‎07-27-2011

My concern with this is for someone coming behind you and using your code and understanding it...the additional documentation required seems like a lot more text than a few parameters to the intnx function.

Reeza · ‎07-26-2011

There are so many factors that influence how a SQL proc or datastep runs that I find the quickest way to test it is try and see which affects the running time by commenting out parts and comparing the differences. This isn't 100% by far, but it works pretty well. Another possibility is the two distinct options in the code, they have to require a sort of some kind on the back end...

Reeza · ‎07-26-2011

Thanks, the paper had the examples I needed!

Reeza · ‎07-26-2011

Post your log, where you're using the mprint option.

Reeza · ‎07-26-2011

To convert a datetime to date use the datepart function. You might want to look up the intck function which calculates some date difference and you can also customize the alignment in that function to 'end' of the month/year which seems what you're looking for.

Reeza · ‎07-26-2011

Similar to a logistic regression with multiple categories, the hazard ratio is for the different levels compared. That is, everything else held constant, 2 vs 1 and 3 vs 1 -- assuming 1 is your reference level. You can set what you want the reference level in your CLASS statement. class group (param=REF REF='1'); This sets the reference level to 1. You can change that to 3 if you'd like. I suggest using the HAZARDRATIO line to get the specific hazardratios you need: hazardratio group; You cannot get hazard ratios from PROC LIFETEST because it is not part of the model. PROC LIFETEST by default uses a KM method of estimating survival, which is non-parameteric and has no assumptions, ie proportional hazards. Comparison of the two groups is done via the LOG-RANK test instead.

Reeza · ‎07-25-2011

Can't seem to find an example that similar to what I need, or blanking because its the end of the day... I have a dataset that I'm outputting to excel with ods excelxp via proc report but one line is actually percentages. I'm trying to format this row red and have the values show up as percentages. I think i need to be using a tagattr but having a hard time figuring out how/where to specificy for a row specific format. Any pointers appreciated. Thanks!

Reeza · ‎07-22-2011

Thanks, it still has to be set by the original poster then...that's what I was wondering.

Reeza · ‎07-21-2011

Ok...could you post the code you used? You can also reference this paper: www2.sas.com/proceedings/sugi29/106-29.pdf specifically on how to load tables into Oracle, its old, but perhaps some of those methods would work for you. I usually use a libname statement with an odbc connection and it works fine...