What happens if you set DESCRIPTION=" " on the SGRENDER procedure statement? ... View more

You can work around this limitation by calculating the N and MEAN externally and using an AXISTABLE to display the values. Here is an example:   proc summary data=sashelp.heart nway; class weight_status bp_status sex; var cholesterol; output out=table mean=mean n=n; run; data merged; set sashelp.heart table; run; proc sgpanel data=merged; panelby weight_status / novarname; vbox cholesterol / category=bp_status group=sex; colaxistable n mean / class=sex classdisplay=cluster colorgroup=sex; run; ... View more

Sorry, I realized that for #2, I accidentally put the SGPLOT option for positioning the legend. For GTL, you should use HALIGN=RIGHT and VALIGN=TOP. Thanks! ... View more

1. The axis label is getting pushed out because the length of the AXISTABLE labels at the bottom. Some options to fix the issue include the following: disable the labels and rely on the color coding Shorten the label using a user-defined format (this might not be possible, as you are probably sharing the group variable with the plot) Disable the Y-axis label and use a DRAWTEXT statement to put the axis label closer to the axis (this is probably your best option) 2. The DISCRETELEGEND need to be inside your LAYOUT OVERLAY, and set the POSITION to be TOPRIGHT.   Hope this helps! ... View more

Th key here is having only one legend positioned at the top left. To include everything in the legend, remove the NOAUTOLEGEND option and just have one KEY:EGEND statement to telling it move to the top left. If you want only the SERIES plots in the legend, you should do as @FreelanceReinh mentioned and use the NAME option on the SERIES plots and list the names on the KEYLEGEND statement.   It's also important to note that a KEYLEGEND statement with no names listed is how you normally control the AUTOLEGEND, but that legend was disabled by the NOAUTOLEGEND option. Normally, the position of a KEYLEGEND statement does not matter, but I'm thinking that a "positional" AUTOLEGEND was created due to these mix of options. As a rule, use "no name" KEYLEGEND statements for only AUTOLEGENDS; otherwise, names should be specified.  ... View more

On the TEXT statement, try add these two options: STRIP -- this option strips extra spaces from the text. I think that is why you are getting a difference between the LEFT and RIGHT positioned text PAD=10px -- This will pad out the text by 10 px. You can adjust this to taste. ... View more

Sorry, I missed the cross-hatched part of your request. Assuming you're using a bar-type HIGHLOW for this, I would split the data based on this variable and overlay two HIGHLOW plots, with one of them having FILLPATTERNS enabled. You should be able to use the attrmap for coloring both overlays. Would that work for you? ... View more

You can put all of your maps in the same data set using different IDs:   data attrmap; length ID $ 9 linecolor markercolor fillcolor $ 10; input id $ value $10-30 linecolor $ markercolor $ fillcolor $; show='ATTRMAP'; datalines; status Complete response darkred darkred gray status Partial response blue blue gray stage Stage 1 darkred darkred green stage Stage 2 black black yellow stage Stage 3 black black orange stage Stage 4 black black red ; run; Then, use the ATTRID option from each plot overlay to use the correct ID value.   Hope this helps! ... View more

Another option would be to use your existing data structure, but add a TEXT plot so that you can control the label positions from your data. The code would look something like the following.  proc sgplot data=SurvivalPlot noborder; series x=Time y=Survival / lineattrs=(pattern=solid) Group=Stratum Name='S'; scatter x=Time y=Quartiles / markerattrs=(symbol=circle size=7) name='Q'; text x=Time y=Survival text=years / group=stratum textattrs=(size=10) position=PositionVar; keylegend 'Q' / location=inside position=right Valueattrs=(Size=10); yaxis label="Survival Probability" grid values=(0 to 1 by 0.10); xaxis label="Years" grid values=(0 to 20 by 2); run; You would just need to add a PositionVar to your data specifying where you want the each label (LEFT, RIGHT, TOPRIGHT, BOTTOMLEFT, etc.). Hope this helps! ... View more

Given that goal, I would use a two overlaid VLINEs instead of overlayed VBARs, and I would drop the TTF group. That way, you can clearly see the transition you described. Just use the default STAT of SUM. I would also use the MARKERS option so you will see the markers at each year. ... View more

One alternative would be to transpose your data so that your GroupA and GroupB responses are folded together with a GROUP column containing the values "GroupA" and "GroupB". Then, you could something like the following with PROC SGPANEL:   proc sgpanel data=sashelp.prdsale; panelby year / layout=rowlattice novarname; vbar month / response=actual group=product; run; ... View more

Sorry, you were talking about the tick values, not the axis label. Would you be opposed to having these plot in one display? That way, the axes have the ability to auto-align themselves based on the content of each plot. ... View more