SAS Macros

These are components that can be used within your own SAS programs. Headings at the top of each file describe how to call or use them, and examples are provided. See below for guidelines on calling these from within your programs.

• Logistic Regression
• Linear Regression
• Logistic Regression with a Random Intercept (e.g., for clustered data)
• Generalized Linear Regression for Count Data
• Summarize continuous and categorical variables (Table 1 Macro)
• Effect Size
• Categorize Groups variables into discrete, continous and Dates
• Pearson and Spearman Correlations
• Partial Least Squares
• CrossPlots
• False Discovery Rate
• Least Squares Mean Plot for Mixed Models
• Least Squares Mean Plot for GEE Models
• Finding cutpoint for a continous predictor using ROC
• Utilities

(For more biostatistical SAS tools see sasCommunity.org.)

Calling macros

To use one of these macros in your program, or within another macro you create to post here, put statements like the following before you call the macro:

/* filename lreg URL "http://CTSpedia.org/do/viewfile/CTSpedia/LogisticRegressionMacro?filename=Logistic.sas;rev=4"; */
filename lreg URL "http://ctspedia.org/twiki/pub/CTSpedia/LogisticRegressionMacro/Logistic.sas";
%include lreg;

These statments make the main logistic regression macro available. The fileref "lreg" in the above is just a word that you can make up, but it should be no more than 8 characters long. (Note that you should be able to copy and paste, rather than type in, the URLs: Here's how).

It will usually be best to use this form, which uses the most current version of the file even if it changes since you first wrote your program. This will incorporate any subsequent error or problem corrections. The commented out statement above it instead finds the specific version of the macro that was current when you wrote your program. You may need this if a later updated version is not called the same way or does not produce the same output as assumed in your program. Switching which statement is commented out will then permit your program to run as originally intended without updating it to work with the later version of the macro it calls.

Possible Enhancements

Investigate use of the SvnPlugIn to track versions of tools.
Develop a convention for noting errors found and corrected in earlier versions, so that users of the tools know that they should update any old programs to use the newer versions.

Need Checklist for Corr Macro :completed Barbara/Peter July 2009