Cancer Deaths Averted

cancer_mortalitySignificant progress in reduction of Cancer mortality is shown in a graph that I noticed recently on the Cancer Network web site.  This graph showed the actual and projected cancer mortality by year for males.  The graph is shown on the right.

The graph plots the projected and actual numbers by year, and highlights the difference using the hatched pattern.  The total number of Cancer Deaths Averted is shown.

The graph on the right includes a Y axis data range all the way down to zero, where it is really not necessary.  But, we can use this space that is otherwise wasted to display more information.

Creating the graph is easy, using the following SGPLOT code.  Some options are trimmed to fit the space.  See full code in link at bottom for the details.

title 'Cancer Deaths';
proc sgplot data=mortality nocycleattrs nowall noborder;
  styleattrs datalinepatterns=(solid);
  highlow x=year low=actual high=projected / type=line;
  series x=year y=projected / name='b' legendlabel='Projected';
  series x=year y=actual / name='a' legendlabel='Actual';
  keylegend 'a' 'b' / location=inside position=topleft linelength=20;
  xaxis values=(1975 to 2010 by 5) grid;
  yaxis values=(0 to  450000 by 50000) grid;

Mortality_Diff_2The graph is shown on the right is created by the code shown above.  The data is "eye-balled" from the original graph and includes the columns of Year, Actual, Predicted and Diff.  The total number of deaths averted is saved in a macro, and also inserted into the label to be displayed.

Two SERIES plots are used to plot the actual and predicted curves.  A HIGHLOW plot is used to draw the vertical hatch marks showing the reduction in the cancer deaths since 1990.  A legend is added to indicate the actual and predicted curves.


For the graph shown below on the right, a Band plot is added to display the reduction in cancer deaths by year explicitly.   Also, we have used a TEXT plot statement to display the inset indicating the number of deaths averted.



There some benefits of this addition.  The empty area at the bottom of the graph is utilized.  The actual deaths averted are drawn from a common baseline, thus removing the distortions in the hatched area due the varying baseline.  An an explicit inset shows the estimated number of deaths averted.

The TEXT plot is a SAS 9.4M2 feature, but one could use an INSET or a SCATTER with MarkerChar to do something similar.

Full SAS code:  CancerDeaths

Post a Comment

Displaying Unicode Symbols in Legend

Including special Unicode symbols into the graph is getting more popular.  In general, SG procedures support Unicode strings in places where these strings are coded into the syntax such as TITLE, FOOTNOTE.  These support Unicode characters and also the  special {SUP} and {SUB} commands.  This is because these statements are rendered by the graph using Java string API.

Curve Labels and Axis Labels that are assigned in the procedure syntax can also support Unicode, but not the {SUP} and {SUB} commands.  This is because these items are passed to the graph rendering engine which cannot handle the {SUP} and {SUB} commands.  However, most of the popular numeric sub and super scripts are available in the Unicode fonts, so much of the need is covered.

Recently, a user chimed in on the Communities page, wanting to include Unicode values in the Legend.  The group variable values include Unicode strings like "Less than or equals", and the journal preferred usage of the Unicode <= symbol, not the "<=" sequence of characters.

Data_GroupsWith all the releases of SAS till date, the SGPLOT procedure cannot support Unicode from data or formats into the graph legends or axis.  However there is a way to do this  by restructuring the grouped data into a multi-column format.

A few observations of the original data are shown on the right.  I have added a column based on the level of the Systolic Blood Pressure called "Status".

We could plot a Graph of Weight by Height by Status, and get a scatter plot of the data, with the "Status" values displayed in the legend as "GE160" and so on.  However that is not what user wants, and rather have the numeric values with the "<=" symbols.

Data_ColumnsThe transformed data set is shown on the right.  Here, I have created four new columns, each containing the appropriate value for weight based on the Status.  So, this result in some missing values in the new columns.

Now, instead of using one scatter plot with the GROUP option, we will plot these four columns using four scatter plots as shown below.  All of the scatter plot are without any group variable, and I have used the LEGENDLABEL option to provide the label for each scatter plot.  These labels include Unicode characters.

ods escapechar '~';
title 'Blood Pressure by Weight by Height';
proc sgplot data=heart_cols;
  scatter x=height y=ge160 / legendlabel="160 ~{Unicode '2264'x} Systolic ";
  scatter x=height y=ge140 / legendlabel="140 ~{Unicode '2264'x} Systolic &lt; 160";
  scatter x=height y=ge120 / legendlabel="120 ~{Unicode '2264'x} Systolic &lt; 140";
  scatter x=height y=lt120 / legendlabel="Systolic &lt; 120";
  keylegend / title='' location=inside position=topleft across=1;


Click on the graph for a higher resolution view.  Note the legend on the top left contains the ranges for the Systolic blood pressure, using the appropriate Unicode symbols.  Each scatter plot in the graph is represented in the legend by the LEGENDLABEL.  The legend label can be assigned Unicode values as shown above.

Now, the legend in the graph can be improved if we can position all the "Systolic" labels in the legend vertically aligned.  To do this, one might want to add some blanks to the front of the text string in the Legend label for the fourth scatter plot.  However, this will not work, as all leading blanks are automatically stripped.  But, the system can be tricked to not strip the leading blanks by first adding a non-breaking space character 'A0'x in the label string followed by the required number of blanks. This is shown in the code and graph below.

ods escapechar '~';
title 'Blood Pressure by Weight by Height';
proc sgplot data=heart_cols;
  scatter x=height y=ge160 / legendlabel="160 ~{Unicode '2264'x} Systolic ";
  scatter x=height y=ge140 / legendlabel="140 ~{Unicode '2264'x} Systolic &lt; 160";
  scatter x=height y=ge120 / legendlabel="120 ~{Unicode '2264'x} Systolic &lt; 140";
  scatter x=height y=lt120 / legendlabel="~{Unicode '00a0'x}         Systolic &lt; 120";
  keylegend / title='' location=inside position=topleft across=1;


In the legend for the graph above, all the "Systolic" terms are correctly aligned, making the legend a bit easier to read.  Note, this process needs custom handling.  Full code is provided in the link below.

The good news is that support for Unicode in the graphs will be included with SAS 9.40M3 release using User Defined Formats.  With this approach, you will be able to format any data value into a string that can include Unicode symbols.  Thus group values or axis tick values can be customized programmatically.

Full SAS 9.3 Code:  LegendSymbols_930







Post a Comment

Marker Symbols

There has been much discussion on the SAS Communities page on usage of different symbols in a graph.  The solutioin can vary based on the SAS release.  New features have been added at SAS 9.4 releases to SG Procedures and GTL that make this very easy.  With SAS 9.4M1, almost any combination is possible.

Symbols_ColorOnlyThe user has a relative simple scatter plot with two class levels.  The graph on the right is easily created using a scatter plot with a group role.  The code is shown below.

Note, starting with SAS 9.3, ODS HTML is the default open destination, using the HTMLBlue style.  This is a "Color" priority style, where each group gets only a color change till all Style Elements are used.  So, you do not see varying marker symbols in the graph on the right.

title 'Mileage by Horsepower by Make'; 
proc sgplot data=cars;
  scatter x=horsepower y=mpg_city / group=make;
  keylegend / location=inside position=topright;
  yaxis grid integer;
  xaxis grid;

Symbols_ColorSymbolYou can run the same graph with a style like LISTING, or set ATTRPRIORITY=none in the ODS Graphics statement to get the graph on the right.  Now, each group gets a different color and a different marker symbol.  These come from the style GraphData1-12 elements.

 ods graphics / reset attrpriority=none;

The user wanted to use the symbols "X" and "Y" instead of the "circle" and "plus" symbols that are the default first two symbols in the GraphData1-12 elements list.  This in itself is very easy, since the "X" and "Y" symbols are included in the list of built-in symbols supported by these procedures.  All you need to do is change the default symbols in the GraphData1-12 elements.

Symbols_BuiltIn_94With SAS 9.4, it is very easy to change the group attributes by using the STYLEATTRS statement in SGPLOT.  This feature provides a simple in-line way to modify the list of color, contrast color, symbols and line patterns used for the group values, as shown in the code snippet below.

The list of values provided REPLACE the default group list as if this came from the style.  So, now the group cycling uses only the two symbols "X" and "Y" provided in the list.

proc sgplot data=cars;
  styleattrs datasymbols=(X Y);
  scatter x=horsepower y=mpg_city / group=make;

But what if you want to use some special symbols that are not provided in the built-in list of symbols?  You can do that with SAS9.4M1 using the new statements SYBMOLCHAR and SYMBOLIMAGE.  SymbolChar statement supports the ability to use any character from any font as a symbol.  Using a Unicode font allows you thousands of symbols that can be used.

Symbols_Others_94Say you want to use the greek symbols  for "Alpha" and "Beta" as the marker symbols.  You can define a new symbol name using the SYMBOLCHAR statement and then include that in the list of group symbols to be used using the STYLEATTRS statement.  The code snippet is shown below, and the resulting graph is shown on the right.  Click on graph for a higher resolution view.

proc sgplot data=cars;
  symbolchar name=Alpha char='03b1'x / scale=1.8;
  symbolchar name=Beta char='03b2'x  / scale=1.8;
  styleattrs datasymbols=(Alpha Beta);
  scatter x=horsepower y=mpg_city / group=make markerattrs=(size=9);

Note the use of the SCALE option above.  Most font glyphs do not occupy all the pixels in the glyph.  So, these symbols may appear small.  The scale options allows us to scale them up.

Symbols_Image_94And now, the "pièce de résistance".  In many cases, such as the case here, we can use symbols that not only distinguish between the group values, but by themselves provide information on what they represent.

The SYMBOLIMAGE statement allows you to define new symbols from images.  These can then be used for group values using the STYLEATTRS statement, just like shown above.  Here is a graph using image symbols.  Note, I have removed the legend just to make this point.  The markers do not require any legend to explain what they stand for (for most users).

It helps to make the images have a transparent background, so the shape of the icon is visible, and does not block other markers.  The images must be available on the local file system.

proc sgplot data=cars noautolegend;
  symbolimage name=BMW image="C:\BMWTrans.png";
  symbolimage name=Porsche image="C:\PorscheTrans.png";
  styleattrs datasymbols=(BMW Porsche);
  scatter x=horsepower y=mpg_city / group=make;

Full SAS 9.4 Code:  Symbol

Post a Comment

Custom Labels

Over the Christmas Holidays I saw an graph of agricultural exports to Russia in 2013.  The part that caught my eye was the upper part of the graph, showing the breakdown of the trade with Russia as a horizontal stacked bar with custom labels.

TopThe value for each region / country is labeled individually along the top and bottom of the bar for each segment, as shown on the right.  Each label is at a custom location along the bar with some on top, some at the bottom.  Most labels include the name of the region and the amount, but others have the name in the label, but the amount in the bar (European Union).

Russia_LegendMaking this graph as a regular stacked horizontal bar with a legend is very simple and also scalable and extensible to other data.  I used the colors from the graph above, but then added a few other colors to distinguish the segments so they can be identified in the legend.  Click on the graph for a more detailed view.

proc sgplot data=russia noborder nocycleattrs;
  styleattrs datacolors=(%rgbhex(207, 49, 36) %rgbhex(225, 100, 50) 
             gold yellow lightgreen);
  hbarparm  category=cat response=value / group=label groupdisplay=stack 
            baselineattrs=(thickness=0) barwidth=0.5 grouporder=data;
  keylegend / title='' noborder location=inside position=top;
  yaxis display=none  colorbands=odd offsetmin=0.3;
  xaxis display=none;

The main reason the original graph is interesting is the attempt to "move"  the  legend entries closer to the bar itself.   The benefit of this  is that the values can be read directly and easily and the graph is easier to decode.  In the legend case, one has to move the eye between the legend and the graph.  First, identify the color of the segment in the bar, then find its value from the legend.  Also, the small green segment for Australia could be missed.

Direct labeling is often useful for decoding a graph, especially where the graph is not too complicated.  But, direct labeling in this case also requires custom code, either annotation or something else.  So, there is a balance to be achieved between the two.

Russia_Labels_4Since I try to avoid annotation as much as possible, first I tried to create this graph using other means with SAS 9.4M2.  Here is what I was able to do with some coding.  My goal is to break up the legend and move each individual value closer to the bar segment itself.  I kept the color swatches to avoid the need the call-out line to each bar segment.

Clearly, the coding is more elaborate, as I have to place each color marker and the text close to where it needs to go, switching between above and below the bar as shown in the code below.  Some appearance options are trimmed to fit.  See full code in the link below.

proc sgplot data=russia_labels noborder noautolegend nocycleattrs;
  styleattrs datacolors=(%rgbhex(207, 49, 36) %rgbhex(225, 100, 50) 
             gold yellow lightgreen)
             datacontrastcolors=(%rgbhex(207, 49, 36) %rgbhex(225, 100, 50) 
             gold yellow lightgreen)
  hbarparm  category=cat response=value / group=label groupdisplay=stack 
            baselineattrs=(thickness=0) barwidth=0.5 grouporder=data;
  scatter x=xlbl1 y=cat / discreteoffset=-0.35 group=label;
  text x=tlbl1 y=cat text=label / discreteoffset=-0.35 position=left 
       contributeoffsets=none splitpolicy=splitalways splitchar='=';
  scatter x=xlbl2 y=cat / discreteoffset= 0.35 group=label;
  text x=tlbl2 y=cat text=label / discreteoffset= 0.35 position=left 
       contributeoffsets=none splitpolicy=splitalways splitchar='=';
  yaxis display=none  colorbands=odd;
  xaxis display=none;

Note, the code is longer because there are 2 pairs of scatter and text plot statements, one for the labels along the top and one for those at the bottom, because of the different values of DiscreteOffset.  The positions for the markers and the text are computed for each value in the code.  Now, each label and value are effectively moved close to the segment, making the graph easier to decode.

In this exercise, I have used the new TEXT plot statement added with SAS 9.4M2.  This statement is customized to draw text strings in the graph, and has many features for handling text.  We did not want to overload the scatter plot (with MarkerChar).  Going forward, you would be better off using the TEXT plot in place of cases where you used MarkerChar.  For earlier releases, you could use the scatter with MarkerChar or DataLabel to do something similar. This exercise is left to the motivated reader.

Alternatively, one could exactly duplicate the original graph by using SG Annotate to do the labeling, including the call out lines from the text to the segment.  In both cases, the code is heavily customized, and not easily scalable to other data.

I have presented my opinion on the pros and cons of each method.   I would love to hear your opinion too.

SAS 9.4M2 Code:  Russia_3


Post a Comment

Scatter Plot with Stacked Histograms

scatter_and_hist_borderLast week a user expressed the need to create a graph like the one shown on the right using SAS.   This seems eminently doable using GTL and I thought I would undertake making this graph using SAS 9.3.

The source data required to create this graph is only the X-Y information in the scatter plot.   Not having access to the original data in this graph, I simulated some data using random functions in three DO loop, one each for the three groups, in a DATA STEP.   The groups are 'A', 'B' and 'C', in place of the values like 'Center = 0.29' and so on.  See the full program in the link at the bottom.

The graph on the right can be constructed as a LATTICE of four cells with the following contents.

  • The cell on the bottom left is a regular X-Y scatter plot by group.
  • The cell at the top left is a stacked vertical histogram of counts for the x-bins by group.
  • The cell at the bottom right a stacked horizontal histogram of counts for the y-bins by group.
  • The cell at the top right contains the legend.

SAS 9.3 SGPLOT or GTL does not have a statement to draw a stacked histogram by group.  So, we have to find another way to do this.   We will us the HighLowPlot plot statement, which shows the group segments where we place them, and also supports a numeric x axis.  We now have to build the data set appropriate for the plot.

The good new is that we can leverage the SGPLOT Histogram statement to generate the bins and counts we need for X and BY=group as follows:

ods _all_ close;
ods output sgplot=xa;
proc sgplot data=scatter(where=(x le 5));
  by grp;
  histogram x / scale=count binstart=0 binwidth=0.25; 

xBinsThis program will bin the data by X, with BinStart and BinWidth set as needed.  The output is written the the 'XA' data set.  The SGPLOT generates the required bins and count columns using variable names that are based on the original variables.  You can turned off all destinations, so no graph is actually created but the data set is written out.  You can view the data set to find these new variables.

After this step I cleaned up this data set to create a data set of the xBins and the Counts by Group.  A snippet of the data set is shown on the right.

data xBins;
  set xa(where=(Bin_X_Scale_count_Binstart_0___Y ne .));
  drop x;
  rename Bin_X_Scale_count_Binstart_0___Y=count
proc sort data=xBins out=xBinsByBin;
  by xBin;

xBinsHighLowNow we have the bins and the counts by group.  We need to stack the values so we can use the HighLowPlot to draw the stacked bins.  The data step shown below does just that, but creating the Low and High values for each group in a bin as stacked on the previous value.

The final data set is shown on the right.  We can plot it using the HighLow plot statement in SGPLOT to create just the horizontal stacked Histogram, to see if we have the right data.  I will save that step for later.

data HighLowX;
  drop count;
  retain Low High;
  set xBinsbyBin;
  by xBin;
  if first.xBin then Low=0;
  High=Low+Count; output;

We go through the same steps above for creating the binned data for the Y axis.  then, I merge the original X-Y data with the X and Y bin data sets to get the final data set ready for plotting.   I can plot each graph separately form this merged data set to ensure everything is working correctly.  The xBin, Low and High values are in a block of the data where other columns are missing, and so on.  Here is the graph for just the horizontal stacked histogram.


The next step is to create a GTL template with a 2x2 layout of cells and common uniform axes.  See the program link at the bottom for the full code.  Here is the layout of the template.

proc template;
  define statgraph Scatter_Layout;
      entrytitle 'Distribution by Group';
      /*--Outermost Lattice Container--*/
      layout lattice / rows=2 columns=2 rowweights=(0.3 0.7) columnweights=(0.7 0.3)
                       columndatarange=union rowdatarange=union
                       rowgutter=5 columngutter=5;
	/*--Common Row axes--*/
	  rowaxis / offsetmin=0 display=(ticks tickvalues) griddisplay=on;
	  rowaxis / label='Mean of Full Rho' griddisplay=on 
                    linearopts=(tickvaluesequence=(start=0 increment=0.5 end=3.5));
	/*--Common Column axes--*/
	  columnaxis / label='Ratio of Full Rho' griddisplay=on);
	  columnaxis / offsetmin=0 display=(ticks tickvalues) griddisplay=on);
	/*--Upper Left cell with Stacked X Bins counts by group--*/
        layout overlay;
          highlowplot x=xBin low=low high=high / group=grp type=bar;
	/*--Upper Right cell with Legend--*/
        layout overlay;
          discretelegend 'a';
	/*--Lower Left cell with SX-Y Scatter Plot--*/
        layout overlay;
          scatterplot x=x y=y / group=grp markerattrs=(symbol=circlefilled size=5) 
	/*--Lower Right cell with Stacked Y Bins counts by group--*/
        layout overlay;
          highlowplot y=yBin low=low high=high / group=grp type=bar;

Here is the Graph.  You can adjust the font sizing for the axes if needed.  Click on graph for a high resolution image.  Note, we are using common external Row and Column axes since these are uniform and should not be repeated.


Full SAS 9.3 code:  Scatter_Layout

Post a Comment

Dual Response Axis Graphs

Often we need graphs that display two or more responses by the same category values.  In many cases it is useful to plot both responses on the same response (Y) axis.  This can be helpful to understand the data and compare the magnitudes side by side.  This works when the scales of both the response values are comparable and consistent.

ElectricPlot_SGHowever, the scales for the two responses may not be similar or consistent.  One common use case is when we are visualizing the actual and % changes for some categories as shown in the graph on the right.

For this example, I have run the MEANS procedure to compute the revenues by year for all the customers by year, and selected only the "Residential" customer for the graph.  I have also computed the change in the values for subsequent years from the first year (1994).

In the graph above, I have  plotted the actual revenues in Billions of $ for Residential customers as a bar chart on the default Y (left) axis.  The "Change" values with a PERCENT format are plotted as a Series plot on the Y2 (right) axis .  I have colored the Y axis ticks and label using a color consistent with the bars and the Y2 axis ticks and label using color consistent with the line.  This graph displays all the data correctly, in a way that is easy to comprehend.  Note:  I am actually using HIGHLOW instead of VBAR as it allows me to use a linear axis.

title 'Revenues and Growth over Time for Residential Customer';
proc sgplot data=ElecRevChange(where=(customer='Residential'));
  styleattrs datacolors=(orange orange) datacontrastcolors=(cx8f3f00 darkgreen);
  highlow x=year low=zero high=revenue / name='a' legendlabel='Revenue' type=bar 
          nooutline fillattrs=graphdata1 dataskin=pressed;
  series x=year y=change /  name='b' lineattrs=graphdata2(thickness=5) y2axis;
  xaxis integer display=(nolabel);
  yaxis offsetmin=0 min=0 valueattrs=graphdata1 labelattrs=graphdata1 grid;
  y2axis offsetmin=0 min=0 values=(0 .30 .60 .90 1.20 1.50) valueattrs=graphdata2 
  keylegend / linelength=20px;

DataAs we can see in the data table on the right, while the "Change" values are shown with a % format, the values themselves are fractional between 1.0 - 2.0.   The Percent format converts the fractional values into a % number.  So, mixing values with Percent and non-Percent format on the same axis can result in a bad graph.

The axis format is determined by the "Primary" plot, usually the first plot in the list.  In this case, the revenues are plotted first using a bars on the default Y axis.  So, the default format for the Y axis comes from the bar.  If the series plot is also plotted on the same axis, those fractional values will be displayed with a non-percent format, and will not be visible in comparison with the revenue values as shown in the graph below on the right.

ElectricPlot_SGIn the graph on the right, the green line showing change is way down near the baseline.  This is because the response values are all fractional numbers between 1-2, and are plotted on the same axis as the revenues with an axis range of 100.

Things get even worse if the plot with the % format is primary, causing the axis format to be %.  Plotting data having a n0n-percent format on the same axis,will cause those values to be scaled by 100.

proc sgplot data=ElecRevChange(where=(customer='Residential'));
styleattrs datacolors=(orange orange) datacontrastcolors=(cx8f3f00 darkgreen);
  highlow x=year low=zero high=revenue / name='a' legendlabel='Revenue' type=bar 
          nooutline fillattrs=graphdata1 dataskin=pressed;
  series x=year y=change /  name='b' lineattrs=graphdata2(thickness=5);
  xaxis integer display=(nolabel);
  yaxis offsetmin=0 min=0 valueattrs=graphdata1 labelattrs=graphdata1 grid;
  keylegend / linelength=20px;

In such cases, it is best to use a graph with two independent response axes, as shown in the graph at the top of this article.  Now, each axis has data with consistent formats, and life is good.  Note, each axis has its own data range.  In order to have nice grid lines, one has to ensure each axis has equal number of ticks so the grid lines from one axis can work for both.  Else, you will have two sets of grid lines.

ElectricPanel_GTLSo far so good.  But now let us take the next step.  We want to plot the graph for all customers, Commercial, Industrial and Residential in a panel.  We still want to see both revenues and change as a panel shown on the right.

One would think this would be a simple matter of changing from using a SGPLOT to SGPANEL, using "customer" as the panel variable.  In general, you would be right, except here we have crossed the 80-20 feature balance between SG and GTL. Supporting dual response axes for SGPANEL is a much harder task, and something not frequently requested by users. So, what do we do, and how did make the graph on the right?

Well, here is where we have to step out of the comfort zone of SG Procedures and move into the domain of GTL.  Clearly, all of SG features are implemented using GTL programs behind the scenes.  SGPANEL uses the GTL LAYOUT DATAPANEL and LAYOUT DATALATTICE to create the panels.  GTL does support dual response (and category) axes for panels.  So, now I have used the Layout DataPanel container in GTL, along with the BarChart and SeriesPLot statements.  The relevant part of the code is shown below, stripping all the options.  As you can see, it is not so hard to follow.  Full code is included in the attached program.

layout datapanel classvars=(customer) / rows=1 headerlabeldisplay=value 
  layout prototype / cycleattrs=true;
    highlowplot x=year low=zero high=revenue / name='a' legendlabel='Revenue' type=bar;
    seriesplot x=year y=change /  name='b' lineattrs=graphdata2(thickness=5) yaxis=y2;

Dual Axis Graphs:   DualAxis



Post a Comment

Graph Table

Table7A common scenario is where we have a table of multiple measures over time. Here we have a simple example of Frequency and Response by Day.  The Response is a linear function of the Frequency, as shown in the table on the left below.

The  shape of the data is not easily seen in the table alone.  Here is where we can benefit from a visual display of the same data as shown in the graph below on the right.


graphThe shape of the data is clearly visible in the graph of Frequency by Day.  The Frequency values are also displayed as bar labels.  The Response values will have the same shape, but displaying more than one bar value will add clutter to the graph.

Here is where a "Graph Table" comes very handy.  Instead of displaying a separate graph, I can display all the data columns and also add a display of the shape of the data all in one display.

With SAS 9.4, the YAxisTable can be used to easily create such a graph.  The code is shown below:

proc sgplot data=data nowall noborder;
  hbar day / response=Frequency filltype=gradient
       fillattrs=graphdata2 nostatlabel
  yaxistable Day Frequency Response / location=inside
       position=left nostatlabel;
  yaxis display=none;
  xaxis display=none grid offsetmin=0.05;

graphTableThe Graph Table display is shown on the right.  Note, all the columns from the table are included, and a HBar is added to display the shape of the response columns.  In this case since the shape of both the columns is the same, I have left out the x axis information.

An additional benefit of this display is that it is scalable.  As the data set gets longer, using a traditional VBAR chart can get cumbersome.  The x axis will need to get longer till the graph will no longer fit a traditional report.  A HBAR however, can grow vertically with the data to as much height as you may want.

For the graph below on the right, I have tied the height of the graph to the number of observations in the data set.  So the graph grows with the table.  See the full program attached at the bottom.

graphTableBigIf the data set gets too long to fit on a page of a document, you can split the graph into smaller sections to fit one on each page.  This can be done by adding a classifier column with page values '1', '2' and so on for every N observations and then use the "BY" statement to produce graphs with a fixed number of observations per page.  The graph axis is automatically scaled uniformly across all pages.  This extension is left to the reader.

A popular use case of the Graph Table is the Forest plot.  Here, you have multiple observations, one per study, with multiple columns of data and an odds ratio graph.  The YAxisTable or its GTL sibling - the AxisTable makes creating such graphs very easy.

SAS 9.4 Code for Graph Tables:  GraphTable

Post a Comment

Fun with Bar Charts

Salary_2As Sheldon Cooper would say, this is the first episode of "Fun with Charts".  I did not find a cool term like "Vexillology" and "Cartography" is taken by map making, so let us go with "Chartology".

Yesterday, I saw a couple of interesting bar charts as shown on the right.  I thought this may provide for some fun creating different appearances with Bar Charts using SAS 9.4M2.

The first graph uses a color gradient from a lighter color at the top to a darker shade at the bottom, though the one in the middle seems to have a reddish tinge.

The second graph on the right uses an interesting way to label the categories.  Let us see what we can do with the new features added to SGPLOT procedure with SAS 9.4M3.

Salary_4The SGPLOT procedure supports new features including the ability to have a gradient fill for bars and histogram bins.  We will use this feature to create these charts.  The VBar statement can be overlaid with itself as long as the category and group classifications are the same.  We can use this feature to create the first chart.

The second graph needs a little more creative construction, using a mixture of plots.  The VBarParm statement can be freely combined with any other basic plot to create more interesting combinations.  We will use that to create the second graph.

Law_GradientThe Bar and Histograms now support a FillType=Gradient option, that fills the bar with the bar color that is fully opaque (or the specified fill transparency) at the top, and gradiates to transparent at the bottom.  Some of the background (wall) color shows through, including anything behind the bar, such as grid lines.

For the graph on the right, I have used a VBAR with groups set to the same as the category to get the bars colored by the category.  I have set FillType=Gradient which results in the nice gradient from saturated color at the top to the transparent at the bottom.  The code is shown below.  Click on the graph for a higher resolution image.

SAS 9.4M3  SGPLOT Code:

proc sgplot data=Law_Salaries nowall noborder noautolegend;
  styleattrs datacolors=(red gold green) datacontrastcolors=(black);
  vbar profession / response=salary group=profession groupdisplay=cluster 
                    filltype=gradient baselineattrs=(thickness=0) 
                    datalabel datalabelattrs=(size=14);
  xaxis discreteorder=data display=(noticks nolabel noline);
  yaxis display=(noticks nolabel noline) grid;

Law_White_GradientNote in the program above, we have set a few wall, border and axis options to get this appearance. GroupDisplay is set to "Cluster" to get the data labels on each bar.  Also note the grid lines are visible through the bar towards the bottom as the transparency increases.  If this is undesirable (as in this case), we can address this by placing a VBar behind it with opaque white bars as shown in the graph on the right.

Only thing remaining to do now is to change the gradient to transition to black instead of white at the bottom.  The way to do this is probably obvious to you.  Instead of an opaque white backing VBar, use black.

Law_Black_Gradient_MatteHere is the final result, with bars gradiating to black and using the "Matte" skin.  Except for the slightly reddish tinge at the bottom of the 2nd bar, this is pretty close, I think.

Now, let us turn to the second example.  This graph is relatively straightforward, except for the interesting way the category values are labeled along the side of each cluster.  Also, the bar values are inside the bar at the top end, rotated vertically.

Pys_Salaries_1We will start by creating a basic cluster grouped bar chart using the VBarParm statement as shown on the right.  We used VBarParm because we know we will need to use other statements to do the special effects, and VBarParm allows us to layer it with other plots.

The graph on the right really gets the information across just fine, with the nice split tick values on the x axis.  This part is all done by the single VBarParm.  We have overlaid on each bar a new TEXT statement to display the bar values at the top of the bar, but inside the bar.  The values are rotated vertically, and aligned such that the right edge of the text is along the top of the bar.  Note the use of "Backlighting" to ensure the text is visible on any background color.

To add the unique category labeling, we use a second text plot.  We offset the bars to the right by using DiscreteOffset=0.2, and ClusterWidth=0.6.  This places the three bars offset to the right.  Then, we overlay a TEXT statement with the following settings:

text x=profession y=zero text=profession /  rotate=90 position=right 
     textattrs=(size=12 color=darkblue) contributeoffsets=none     

Pys_Salaries_3The resulting graph is shown on the right.  In the syntax for the TEXT plot, note the three required parameters, X, Y and Text.  The text from the column is placed at the (x, y) location in the graph.  The plot is offset to the left by 20%, the text is rotated 90 degrees with position of right (meaning, text is on right of the location prior to rotation).  The text color is set to dark blue just to add some interest.

The overlaid bar labels use black text, again with backlight.  Back light works by default, and darkens or lightens the background based on the text color so that the text is clearly visible.

Over the years we have found ourselves using the Scatter with MarkerChar to insert textual information in a graph.  So, it is about time text gets its own statement with options to customize the text.

Note.  Everything is done using plot statements.  No annotation is required.

Full SAS 9.4M3 SGPLOT code:  BarCharts

Post a Comment

Axis Break Appearance Macro

Bar_NoBreak3Often, we have data where most of the observations are clustered within a narrow range, with a few outliers positioned far away.  When all the data is plotted, the axis is scaled to accommodate all the data, thus skewing the scale.  Techniques to handle such data have been addressed earlier in the article Broken Y Axis and Using Log Axes.

Users have previously voiced the need to support axis breaks in the procedures.  This feature can get complicated very quickly, so our plan was to start with the simpler case, and then build based on your feedback.

Bar_Break3Support for axis ranges on one axis at a time is included in SAS 9.4M1.  You can specify one or more breaks by providing the data range(s) that are to be retained.  In the graph on the right, most of my data is between 2 and 3 on the x axis, with one outlier at x > 10.  I use the RANGES option on the x axis to retain the data ranges 1-3.5 and 9.75-11.

SAS 9.4 SGPLOT code:

proc sgplot data=break noautolegend;
  highlow y=y low=zero high=x / group=y lineattrs=(thickness=3);
  xaxis ranges=(1 - 3.5 9.75-11) integer;
  yaxis min=0 max=4;

As you can see in the graph above, only the ranges specified in the RANGES option are displayed on the x axis.  An attempt is made to keep the tick value increments the same in the displayed regions.  A full height break indicator is displayed across the entire height of the data area.  Such breaks are useful when using plots like bars, needles or series.  If the full break was not shown, it would not be obvious at first glance that the blue needle is broken.

X_AxisBreak_Bracket_Wall_ListingHowever, in many cases, such a full height break indicator is not desirable.  When using scatter plots, users have expressed the need for axis break symbols on the axis only, without the display of the full break indicator.  Such an axis break is shown in the graph on the right.  One has to look carefully to see the "Bracket" break indicator shown on the x axis between "3" and "10". Click on the graph for a higher resolution image.

I created the above graph using the SGPLOT procedure, so how did I get this appearance?  Well, the good news is that the procedure does all the hard work needed to draw only the necessary ranges, etc. and position the data correctly  Now, all we have to do is replace the full axis break indicator with the axis break symbol.  This task can be done using annotate.  Since I know exactly the data extent of the break as provided by me in the RANGES option.  I can use this information to erase the break indicator, and draw my own symbol on the axis.

The idea is simple.  Use the POLYGON function to erase the full break using the same color as the wall or background.  I go from the upper edge of the lower range and the lower edge of the upper range.  Each coordinate is correctly transformed to the right location by the procedure.  Then make the polygon the full height of the graph data area.  Using a RECTANGLE function will not work, as we do not know the pixel width of the break.  Note in the attached program, I adjusted the values a bit to allow for the curvy line.  Then, I draw the axis break myself between the Low and High values of the ranges.

I converted the code into a macro to erase the full break and draw axis break symbol for the case of one break:

%AxisBreak (Axis=, Low=, High=, DataOut=, Type=, Back=, Aspect);

Y_AxisBreak_Z_Analysis_WallAxis is X or Y, Low and High are the data values for the break region.  So, in my case for the example above, Low=3.5, High=9.75.  DataOut is the name of the annotation data set generated, Type is the break type.  Back indicated whether or not you include the wall in the display, and Aspect is the aspect of the graph.

The macro generates the necessary annotation data set that erases the full break, and replaces it with a simple axis break of type Bracket or Z.  The graph on the right uses a "Z" break symbol on the Y axis.  Note, the data range of the axis cover -ive and +ive values.

SGPLOT code with Macro:

%AxisBreak (Axis=X, low=3.5, high=9.75, dataout=anno, back=Wall type=Bracket);
proc sgplot data=break noborder sganno=anno;
  scatter x=x y=y;
  xaxis ranges=(1 - 3.5 9.75 - 11) integer;
  yaxis min=0 max=4;

Due to the way axis breaks are implemented in the code, only break symbols of type Bracket and Z can be drawn reliable using this technique.  But at least you now have a way to display simple axis break symbols, instead of the full length or width break indicator.  We plan to include simple axis break symbols in the next release as requested by you.  So, keep your ideas coming.  Till then, you can use the ideas used in this macro.

I have tested the macro for a few different cases with different styles, with or without wall, different dpi, different graph sizes and data ranges.  It seems to handle most cases of one break on one axis, but I have not tested for presence of required variables, etc. or bad data.  It is provided just as a tool.  I am sure the idea can be extended to multiple breaks on one axis if you have such a case.  I'll leave that exercise to the reader.

SAS Code:  Axis_Break_Poly_Macro

Post a Comment

Clinical Graphs

This week I had the opportunity to present a 1/2 day seminar on creating clinical graphs using the SG procedures during an In-House SAS Users' group meeting.  I have presented this seminar quite a few times now, and I always learn something.

The audience was very receptive, with some people familiar with SAS/GRAPH, and others having some knowledge of SG procedures and GTL.  The seminar focused on SG procedures. Often for such seminars, I like to get an idea in advance on the type of graphs the users need to make on a regular basis.  The list of graphs that  were of interest included Kaplan-Meier curves and Forest Plots.

TumorSizeA couple of specific plots mentioned were the Waterfall graph for "Change in Tumor Size by Treatment" and a graph for "Incidence of Injection Site Reaction".

The Waterfall graph displays the range of change in tumor size in the study by treatment.  The (simulated) data consists of the change in tumor size for subjects in a study, displayed in order of increasing reduction grouped by treatment.  Reference lines are drawn at RECIST threshold of -30% and at 20%.

TumorSizeSkinAlternative appearances can be seen on the Web, including grouping by other criteria.  SGPLOT supports skins to alter the visual appearance of the graphs as shown on the right.  Click on the graph for a higher resolution image.

For more information on graphs for Oncology research, see "Plotting Against Cancer: Creating Oncology Graphs using SAS" by Debpriya Sarkar.

SGPLOT code:

title 'Change in Tumor Size';
title2 'ITT Population';
proc sgplot data=TumorSize nowall noborder;
  styleattrs datacolors=(cxbf0000 cx4f4f4f) datacontrastcolors=(black);
  vbar cid / response=change group=group categoryorder=respdesc datalabel=label
           datalabelattrs=(size=5 weight=bold) groupdisplay=cluster clusterwidth=1;
  refline 20 -30 / lineattrs=(pattern=shortdash);
  xaxis display=none;
  yaxis values=(60 to -100 by -20);
  inset ("C="="CR" "R="="PR" "S="="SD" "P="="PD" "N="="NE") / title='BCR' 
        position=bottomleft border textattrs=(size=6 weight=bold);
  keylegend / title='' location=inside position=topright across=1 border;

Note:  GroupDisplay=Cluster is used to be able to display the bar label on top of each bar. So the ClusterWidth option is used to modify the width of the single bar in the cluster.

I have used style colors in the code to set group colors.  However, one can also use the Discrete Attributes Map to ensure the consistent assignment of colors by groups as shown in the paper mentioned above.

Incidence2The other graph of interest was the "Incidence of Injection-Site Reaction by Time and Cohort", as shown in the graph on the right.  The (simulated) data shows the incidence of reaction by time and cohort using a cluster grouped bar chart.

In this case, user wanted bar fill colors and fill patterns.  Fill patterns can be useful when displaying the graph in a gray scale medium.  SGPLOT supports usage of fill patterns for bars, which is enabled by setting the display option.  The easiest way to do this is to set this option in the style.  The Journal3 style shipped with SAS is designed to display both fill colors and fill patterns.  So, I just used that style, and changed the colors to the ones I wanted using the StyleAttrs statement.  You can also do this by deriving a custom style.


ods listing style=journal3;
proc sgplot data=Incidence nowall noborder;
  styleattrs datacolors=(gray pink lightgreen lightblue) datacontrastcolors=(black);
  vbar time / response=incidence group=group groupdisplay=cluster;
  xaxis discreteorder=data;
  yaxis offsetmax=0.2;
  keylegend / title='' location=inside position=top across=2 border;

Full SAS code:  Clinical_Graphs

Post a Comment