Since VIP is not unique, it can vary by a scaling constant, comparing to an absolute value doesn't make sense. I compare VIP of a variable to the VIPs of the other variables, with "biggest" VIPs being the ones I concentrate on.   it would be helpful to understand how SAS performs the scaling   I gave you a link with code. @Rick_SAS explained how SAS calculates this. ... View more

@dxiao2017 wrote:   Therefore, if I want to use a macro (either use a %let statement or a %let and a %put statement) to calculate the mean of several numbers and get a result in a format of xx.xx% (5 digits including two decimal places, in percent), the best steps (and it looks like the correct percent format is percent8.2, not percent7.2) are 1) use a %let and %eval to calculate the number, and 2) use %sysfunc(putn(&number/100,percent8.2)) in the %put statement to display the number in a percent8.2 format. I disagree with the above. Do the math in a DATA step. Don't do this type of math using macro variables. ... View more

Which brings up the question: WHY?   Are you just trying to learn macro functions? Or do you actually have a use for doing artihmetic and storing these decimal values in a macro variable? Usually, arithmetic like this and decimal values like this ought to be created and stored in a SAS data set, not in a macro variable.   Also, please from now on post the code and log as text, not as screen captures.   ... View more

Also ... if your title is a good description of what you want to do, you really want a macro variable formatted at percent7.2 (not 7.2), please understand a few things   The percent format multiplies the number by 100 and places a percent sign after the number, so you would get 6700% Creating text in macro variables that contains a percent sign, although it can be handled properly, is more difficult to use in a program than the same number without the percent sign. Putting a percent sign in a macro variable is something you should avoid if at all possible — don't make decisions that make your programming more difficult.   %let num=%sysfunc(putn(%eval((60+75)/2),percent7.2)); %put &=num;   or   %let num=%eval((60+75)/2); %put %sysfunc(putn(&num,percent7.2)); ... View more

For those of us who don't know, please explain what is the "Bulk download problem"?   Please provide the links to posts from 2021 that address this problem. ... View more

The result is supposed to be 67, and the result is not 67.5. This has nothing to do with formatting. Why? Because %eval() does integer arithmetic. It doesn't know about fractions or decimals.   If you want to do floating point arithmetic with macro variables, and you in this case you want the answer to be 67.5, use %sysevalf() ... View more

The VIP scores are computed via the formula in the code here https://support.sas.com/kb/25/009.html Specifically, you should look at the code for the %GET_VIP macro, the scaling there looks pretty standard. (UPDATE: the scaling is exactly what @Rick_SAS says) You are claiming "the xweight difference doesn't affect the coefficient or R-squared value, but it does make the VIP scores slightly different". I would like to see an example that isn't just a difference in scaling.     ... View more

The problem caused by the letter T is easy to fix, just replace the letter T with a space (use the TRANSLATE function).   The other problems caused by just having a year, or just having an hour, require you to write your own code to deal with those. Example:   if length(datestr)=4 and notdigit(datestr)=0 then dateval=mdy(1,1,input(datestr,4.));   ... View more

unfortunately am not getting it Explain what is wrong. Show us screen captures of these plots. Explain what you would like to see.   Please provide data as working SAS data step code (examples and instructions). Please do not provide data as copy and paste from Excel or similar. Please do not provide data as Excel files. ... View more

@coolbeans : If you absolutely have to have text in each cell like "count  (%missing)", and if you absolutely have to have redundant titles over the columns, then your programming will be more complicated and hard, as shown by @ChrisNZ .   If instead you can produce a table that looks something like this (which contains the same information and in my opinion is easier to read)     then this is a lot easier to produce via PROC REPORT or PROC TABULATE without the complicated SQL. Please provide the information requested by @Ksharp so that we can provide example code.   ... View more