The Unicode value for superscript 6 is 0x2076. However, you need to be sure you're using a "full-featured" Unicode font to show it, as most fonts do not contain that glyph. I would using "Arial Unicode MS" for san-serif text and "Times New Roman Uni" for serif text. Setting 10^6 on an axis label (for example) would look something like the following (on the correct axis statement):   label="10(*ESC*){unicode '2076'x}"   The INSET statement and annotation text supports using superscripts and subscript without using the Unicode values. You can use {sup '6'} in those cases.   Hope this helps! Dan ... View more

Here are the changes to the template: proc template; define statgraph barchart; begingraph / datacontrastolors=(white grey lightgrey grey black) datacolors=(white) datafillpatterns=(S L2 S S S) attrpriority=none; layout overlay / xaxisopts=(display=(ticks tickvalues line)) yaxisopts=(griddisplay=on linearopts=(thresholdmax=1)); barchart category=crit response=pct / group=cat Display=all NAME="VBAR" groupdisplay=cluster clusterwidth=0.7 outlineattrs=(color=black); DiscreteLegend "VBAR"/ title="cat" halign=right across=2; endlayout; endgraph; end; run; ... View more

Unfortunately, we do not currently have pattern support in the discrete attribute map functionality. However, the GTL program below should give you what you want, provided that "cat" is in sorted order:   proc template; define statgraph barchart; begingraph / datacontrastolors=(white grey lightgrey grey black) datacolors=(white) datafillpatterns=(S L2 S S S) attrpriority=none; layout overlay / xaxisopts=(display=(ticks tickvalues line)) yaxisopts=(griddisplay=on); barchart category=crit response=pct / group=cat Display=all NAME="VBAR" groupdisplay=cluster clusterwidth=0.7 outlineattrs=(color=black); DiscreteLegend "VBAR"/ title="cat"; endlayout; endgraph; end; run; data have; input visit$ cat$ pct crit ; datalines; visit1 1 15 1 visit1 1 20 2 visit1 1 30 3 visit1 2 14 1 visit1 2 25 2 visit1 2 21 3 visit1 3 41 1 visit1 3 25 2 visit1 3 48 3 visit1 4 14 1 visit1 4 74 2 visit1 4 21 3 visit1 5 78 1 visit1 5 25 2 visit1 5 88 3 ; run; ods graphics on/ width=8 in height=4 in border =off ; ods html; proc sgrender data=have template=barchart; run; ods html close; ... View more

You might have a corrupted template store in your SASUSER area. Check your SASUSER folder. if you see a template.sas7bitm file, either remove it or rename it, and restart your SAS session. Let us know if that clears it up. ... View more

For this display, you will need to control the marker color at a group level using the GROUPMC option. To use this option, you will need to create a fake group variable, as @Rick_SAS was showing. Then, you will need a variable to track which observations are labeled. This will be the variable you use on the GROUPMC option. Also, I used a small attributes map to control the color to use for those observations. See the example below to see the general idea. Let me know if you need further explanation.   Thanks! Dan   set sashelp.class (obs=7); if (name="Alice") then do; dlab=name; labeled=1; end; else do; dlab=""; labeled=0; end; group=1; run; data attrmap; ID="myid"; value="1"; markercolor="gray"; run; proc sgplot data=class noautolegend dattrmap=attrmap; series x=age y=weight / group=group markers mcattrid=myid groupmc=labeled datalabel=dlab; series x=age y=height / group=group markers mcattrid=myid groupmc=labeled datalabel=dlab; run; ... View more

Setting the tick values explicitly does work, but I wanted to make everyone aware of another alternative that might be more flexible if your data changes from run-to-run. The XAXIS for your VLINE chart can be set to be LINEAR, which will cause the numbers to be plotted linearly along the axis, while the plot is calculated discretely. Then, you can just define a user-defined format to turn the numbers into the correct strings. Below is the modification to your code to demonstrate this approach. proc format; value timeline 0 = "Baseline" 1 = "Week 1" 2 = "Week 2" 3 = "Week 3" 4 = "Week 4" 5 = "Week 5" 6 = "Week 6" 7 = "Week 7"; run; proc sgplot data=TEST ; format visitn timeline.; xaxis type=linear; vline VISITn / response = VAL group = TREAT stat = mean limitstat = stddev numstd = 1 markers markerattrs = (symbol=circlefilled) ; run ; Hope this helps! Dan ... View more

I would suggest one modification to this solution: try using the TEXT plot instead of the SERIES plot. That way, you don't have to turn off the plot features just to get the labels.   Put this in place of the SERIES plot statement: text x=make y=dummy text=dlab / position=top;   Hope this helps! Dan ... View more

Before the "Predictions:" entry, just add a " " entry: entry halign=left " "; entry halign=left "Predictions:" / textattrs=GraphLabelText; You can do the same thing before "Species:" if you want a gap between the legend and the global title. ... View more

I get the picture below with the code I gave you. Is there a particular way you want the legends arranged?     ... View more

Did your layout overlay look like this?   layout overlay;     scatterplot x=petallength y=petalwidth / group=speciesname="sp";     ellipse x=petallength y=petalwidth / type=predicted alpha=0.2         name="p80" legendlabel="80%" outlineattrs=graphconfidence;     ellipse x=petallength y=petalwidth / type=predicted alpha=0.05         name="p95" legendlabel="95%" outlineattrs=graphconfidence2;     discretelegend "sp" / title="Species:" location=inside autoalign=(topleft topright bottomleft bottomright);     discretelegend "p80" "p95" / title="Predictions:" location=inside autoalign=(topleft topright bottomleft bottomright); endlayout;   The LAYOUT GLOBALLEGEND block should be removed. ... View more

LAYOUT GLOBALLEGEND is outside of all other layouts by design. You can put both of your DISCRETELEGENDS inside of the LAYOUT OVERLAY and use the AUTOALIGN feature to have the legends position themselves in a way to prevent data collision (if possible). Would that work for you? ... View more