Yes you are right, that will do the same ... View more

"Note that the y-axis tick mark label "13" may be a bit misleading because it is rounded up from 12.5 due to the insufficient width of the format specification"   Well spotted!  I didn't expect that would happen (and yes, the format should be wider). ... View more

Hi Folks!,   I hope this helps!.   This can be done using SAS arrays easily. Below code works fine to find the header of lowest value in  a list.   ... View more

Thank you very much! this was exactly what I needed!!! ... View more

Regarding getting confidence intervals for Cohen's d (and the unbiased version, called Hedges' g), I recommend the following articles and the references within: Cohen's D statistic in SAS - The DO Loop Confidence intervals for Cohen's d statistic in SAS - The DO Loop ... View more

The data step always loops until something stops it.   So I would restate the question as:   How does SAS know when to STOP looping through the data?  What normally stops a data step is when it reads past the end of its inputs.   In your example when the INPUT statement finds there are no more lines to read from Pumpkin.dat.   In the case of a data step that reads in SAS datasets (with SET or MERGE statement for example) it normally stops when the SET or MERGE finds no more observations to read.   Other ways to stop a data step are :  the STOP statement.  a step that has no inputs knows it does not need to loop. A step that does have inputs but because of conditional logic fails to read from any of them in a pass through the implied loop will write a note and stop.   ... View more

Hi @SASPreK ,your requirement should be done in several steps using different techniques, it would not be able to achieve in a single step through a single technique (e.g., I tried many times with retain and if.first /if.last techniques but failed and almost give up this question and then switched to other techniques). The steps basically include the follows: (a) produce the final results column according to your requirements, this can be done with proc transpose and array, and (b) output the last id and year row together with the final results column, this can be done though if.last  within a data step and then a sql join. The code and results are as follows. data have; input id $ dt:yymmdd10. year test $ result $; format dt date11.; datalines; ABCDE 20100429 2010 T1 N ABCDE 20100712 2010 T1 N ABCDE 20101025 2010 T1 Y ABCDE 20110509 2011 T1 Y ABCDE 20110909 2011 T1 Y ABCUK 20150301 2015 T2 Y ABCUK 20150801 2015 T1 N ABCUK 20150914 2015 T1 N ABCGH 20190613 2019 T1 N ABCGH 20190815 2019 T2 N ABCPK 20130409 2013 T1 N ABCPK 20131021 2013 T1 N ; run; proc print data=have;run; /*produce final results column according to requirements, using transpose and array*/ proc sort data=have out=have1; by id dt; run; proc print data=have1;run; proc transpose data=have1 out=have2; by id; var result; run; proc print data=have2;run; data have3; set have2; array rst[5] $ col1-col5; do i=1 to 5; if rst[i]='Y' then result='Y'; end; run; proc print data=have3;run; /*output the last id and year row together with the final results, using if.last in a data step and sql join*/ data have4; set have1; by id year; if last.year; drop result; run; proc print data=have4;run; proc sql; select h4.*, h3.result from have4 as h4 left join have3 as h3 on h4.id=h3.id; quit;   ... View more

Hello @alepage,   @alepage wrote: (...) if not missing(writtenUnit_HyFi_sas) and not missing(writtenUnit_harmony) then do; if writtenUnit_HyFi_sas eq 0 then wp_diff_pct = 0.0000; else wp_diff_pct = round((writtenPremium_harmony / writtenPremium_HyFi_sas) - 1,0.00001); end; run; It is good practice to check for missing values and zero denominators before dividing two numbers. Your code above has all the necessary IF-THEN/ELSE statements for those checks, but then surprisingly divides the values of two variables which were not checked in the IF conditions.   The code would look much more consistent -- and, most importantly, avoid the "division by zero" problem -- with either writtenUnit_harmony / writtenUnit_HyFi_sas in the division or writtenPremium_harmony and writtenPremium_HyFi_sas, respectively, in the IF conditions. ... View more

Hello @bmcohen36,   @bmcohen36 wrote: ... using 4 data points: -53.8, -41.2, -27.0, and -26.5.  I would have expected the box would extend from the 2nd value to the 3rd value (...) With only 4 values, I would expect the median would divide the box evenly. In addition to the five quantile definitions offered by SAS there are (at least) four more available in other common statistical software packages. Of course, they can be implemented in SAS by programming: see Rick Wicklin's blog article "Sample quantiles: A comparison of 9 definitions" and the accompanying PROC IML code.   However, none of those nine definitions matches your expectations, even though defining the first, second and third quartile of your example data as x 0.25 =-41.2, x 0.5 =(-41.2-27.0)/2 and x 0.75 =-27.0, respectively, would satisfy the criterion at least 100p percent of the sample values are less than or equal to x p and at least 100(1-p) percent of the sample values are greater than or equal to x p which is sometimes used to characterize sample p-quantiles x p  (0<p<1). Note that, by this characterization, all values in the interval [-53.8, -41.2] qualify as a first quartile and similarly all values in [-41.2, -27.0] as a median and all values in [-27.0, -26.5] as a third quartile. Hence, your definition would pick the upper interval endpoint for the first quartile, the midpoint of the interval for the median and the lower interval endpoint for the third quartile to make the definition unique. The default quantile definition in SAS, however, consistently uses the interval midpoints in these cases. ... View more

Hello @JohnKeighley,   Alternatively, you can compute the p-values in a DATA step as shown below using the formulas from the PROC FREQ documentation. (I assume that you want to specify individual null hypothesis proportions for each BY group; see variable p0 below.)   Example: /* Create sample data for demonstration */ data have; length byvar $1; set sashelp.heart; byvar=smoking_status; run; proc sort data=have; by byvar; run; data nullprop; input byvar :$1. p0; cards; . 0.45 H 0.55 L 0.75 M 0.60 N 0.65 V 0.50 ; /* Perform two-sided binomial tests with individual null hypothesis proportions of status='Alive' per BY group */ data want(keep=byvar pval); merge have nullprop; by byvar; n+1; n1+status='Alive'; if last.byvar then do; se=sqrt(p0*(1-p0)/n); z=(n1/n-p0)/se; pval=2*sdf('normal',abs(z)); output; call missing(n, n1); end; format pval pvalue.; run; ... View more

Are you using Display Manager in SAS 9.4? Are you running on Windows?  If so you can use the "Enhanced" Editor and it does have some tools for that.   If you are not running on Windows (or just not using that editor) then you might try programming a KEY. https://support.sas.com/documentation/onlinedoc/sasc/doc700/html/tw5201/z1116812.htm And you can always write a command macro.  For example I have a macro I have been using for 30 years to allow me to paste the list of variables from a dataset into the editor. %macro gks(data,alias)/cmd; /*------------------------------------------------------------------- Generate KEEP statement (or SQL SELECT statement) To generate a SELECT statement, set ALIAS to the table alias or to . for no alias. ... View more

Why did you write it as two separate macros?  If you made the macro variables inside the same macro that used them you could instead make them LOCAL and not have to worry about deleting them since they would disappear when the macro finished. ... View more

Thank you all for your help! In fact, @Cynthia_sas , by applying your solution, I’m not able to get the data to display in the SAS interface the way I want. However, when I generate the results for export (which is what really matters to me now), I do get what I need. Thank you, @PaigeMiller , for pointing out the correct code for the EN DASH. What would be the best way to have the EN DASH display correctly in my SAS interface? Would changing the encoding to UTF-8 be the solution? ... View more