Replacing Manual Coding of Customer Survey Comments with Text Mining: A Story of Discovery with Textual Data in the Public Sector Paper 100-2013: Janardhana Punuru, SAS ; Lane Surratt, SAS ; Russell Albright, SAS Relate, Retain, and Remodel: Creating and Using Context-Sensitive Linguistic Featur...
One thing I’ve learned about SAS programmers over the years: they have definite feelings about how to format their code for readability. Some of the hot debates include: Use proper case (My_Variable_Name) instead of camel case (myVariableName) for variable names. Put TITLE statements in op...
There are no Z or G matrices for this model, and R is assumed to equal 2I, where I is an 18 18 identity matrix. The RUN statement completes the specification. The coding is precisely the same as with the GLM proce- dure. However, much of the output from PROC MIXED is different ...
With additional coding, you can "fix" this result in another pass using DATA step. Or, if you're willing to add the RANGE option with the Excel notation for the specific cell ranges, you can read it properly in the first pass: proc importdatafile="/myprojects/middle.xlsx"out=mid dbms=...
ODS EXCEL doesn't perform well with large detailed output. That is, if I use ODS EXCEL and PROC PRINT a data set with lots of columns and many thousands of rows, it's going to be slow -- and might hit a wall with memory usage. For that use case, PROC EXPORT DBMS=XLSX wor...
Since the program name is the only thing that is different, a macro variable can be used to simplify the coding. Here is the updated example. %let intrnet = http://myserver/cgi-bin/ broker.exe?_SERVICE=default&_PROGRAM=sugi; PROC FORMAT; VALUE $link 'P' = "&intrnet.pecanpie.sas"...