My problem is, that i can't change the column variables that SAS has assigned automatically.   I would have to disagree. You can name these columns anything you want. Example:   proc import datafile="example1.xlsx" out=a(rename=(_in_bn___=billion_dollars)); run;   ... View more

This is the fitted predicted value from PROC GENMOD (screenshot above). I'm trying to dichotomize it, with the intent to answer questions such as, these levels of factor X (used as a predictor in my model) have a higher predicted value than other levels of factor X.   The slopes of the model coefficients will tell you if higher X produces bigger predicted values or not.  ... View more

What does the log say? Turn on the macro debugging options first by running this command   options mprint;   and then run the macro again. That should help you debug it. If you still can't figure it out, please copy and paste the log as text into the window that appears when you click on the </> icon. We need to see the entire log for the calls to the macro, not selected parts of the log. ... View more

@shl007 wrote: I am using PROC GENMOD as follows for a binomial logistic regression. I'm trying to find the best way to present the end results to the users. Any suggestions? One approach I tried was to dichotomize my predicted variable based on the rate of the actual y-variable (e.g., if the actual y-variable rate is, say, 10%, then I would dichotomize my predicted variable for any values above 0.10 to be "yes" else "no"). Doing so results in a far higher predicted rate than my actual. Changing the data and refitting the model doesn't particularly strike me as a good way to present the results.   Exactly what part of the output are you struggling with? What message do you want to get across? What question is this analysis trying to answer?   Can you show us the output as a screen capture? (Please use the Insert Photos icon; do not attach files)  ... View more

@dxiao2017 wrote: Thanks a lot for your comments, I think it's a very good point that use macro (or any other advanced and complex procs and steps) only when it is necessary. However, I really do NOT think that question (as well as the solution) in the lesson was poorly designed, as 1) the learning material was to cover a lot of important contents of macro, and it was also designed for test preparation and had to include all the knowledge and techniques in the exam content guide, and therefore 2) while design the material, (I guess) the course developer was intended to integrate as much as possible contents in one question, and this makes the solution code complicated, and 3) besides the macro part of the built-in base 9.4 guide (SAS 9.4 macro language reference), as a new learner I think Macro1:Essential is the good official learning material I can find now.   For that question in my post, what made the solution code complex was the %let i=%eval(&i+1); statement, which now I guess was perhaps exactly what the material developer wanted learners to comprehend (which is not easy, e.g. how the two repeated %let i=; and %let yr=; statements work) , because that statement is used in a lot of scenarios when there is a do loop inside a macro. A person who takes this macro course then goes out and has a real problem which is similar to the one presented, the person needs means by different years. And the person says "I learned how to do that in my class! I'll write a macro!" And I contend this is the wrong thing to do, and the person has learned the wrong lesson.   If I was going to design a macro class, I would not include using macros to replace other built-in tools in SAS. If the developer of the class wants to teach %let i=%eval(&i+1); there are plenty of ways to teach this without re-creating a BY statement with macro code. ... View more

Splitting a table like you describe is not a good idea, in most situations. So the easiest thing to do is to NOT split it.   Can you explain why you want to split this table? What can you do with the split table that you can't do without splitting the table? ... View more

@dxiao2017 wrote: The question asks to produce means statistics for a list of number of years for the input dataset, and suggests using a %do %until statement and a %scan function inside a macro to do it. The solution offered is as follows: For me, this solution is a little bit confusing and complicated because of 1) the %do %until statement is written in a not so frequently used way, i.e., without the i=xxx to xxx part and 2) the logic behind the repeated %let i= and %let yr= is difficult to understand. I think my solution(below) is simpler and easier (without the %do %until and use a %sysfunc(countw) instead) to produce reports or statistics for a list of years (or any other lists of things, as a macro variable). %macro storms(list); %let count=%sysfunc(countw(&list)); %do i=1 %to &count; %let yr=%scan(&list,&i); title "&yr Storms"; proc means data=mc1.storm_final n min mean max maxdec=0; var MaxWindMPH MinPressure; where season=&yr; run; %end; %mend storms; %storms(2011 2012 2014);     The problem here is that although the course is about using macros, this is a problem that doesn't need to be solved by macros, and you would be much better off simply producing the results with PROC MEANS and a BY statement. So it is teaching you to use macros when macros are not needed, in my opinion, this is the wrong lesson to learn. I have said this many times: an important piece of learning to use macros is learning when NOT to use macros.   Example using SASHELP.CARS data set   proc sort data=sashelp.cars out=cars; by origin; run; proc means data=cars n min mean max maxdec=0; where origin='Asia' or origin='Europe'; by origin; var msrp invoice; run;   ... View more

Wow, I have no idea what the ODS Output gotchas represent in real life, I have never run across any sort of ODS Output "gotcha". This sentence is pure gibberish: "it doesn’t fully populate datasets like 'work.val_fit' in memory the way it shows in logs or external files".   ANOVA as a workhorse — more gibberish. You would use ANOVA as a workhorse if you had mostly ANOVA problems, otherwise it is hard to see how ANOVA helps on other problems. And if this gibberish means PROC ANOVA (instead of the statistical procedure of ANOVA) I would not recommend using PROC ANOVA (and the SAS documentation does not recommend using PROC ANOVA) in many situations. ... View more

In my terminology, you want to get a predicted value (not an estimate) for the case where valence is solely negative and blackness is low. So, I can explain how you get predicted values from the fitted model. I hope you will write back and make it clear if my understanding is wrong and you don't want predicted values.   How do you get these predictions? I will let @Rick_SAS explain in his blog: https://blogs.sas.com/content/iml/2014/02/19/scoring-a-regression-model-in-sas.html ... View more

data want; merge have1 have2; by id; run; ... View more

@Dimax wrote: regex 8 is defined as numeric because prxparse(pattern); return pattern id NOTE: Numeric values have been converted to character values at the places given by: (Line):(Column). 7:11 this is because file path contains numbers Show us the ENTIRE log for this macro. Showing us tiny little bits of the log really isn't helpful. Please click on the </> icon and paste the log into the window that appears. ... View more

Please provide the sample data in a usable form, as shown in these instructions and examples, and as @Ksharp showed in your last thread. We shouldn't have to do this for you. Screen captures or copy and paste from Excel are not acceptable. ... View more

Why group a continuous variable at all? Especially if you are concerned about trend ... ... View more

You have switched from numeric variables to character variables. In that case, PROC SUMMARY will not get the job done. Please provide a realistic data set that illustrates the problem, and also show us the desired output. ... View more