If you're running v9.2, then you should be able to use unicode characters, such as the ones in the "albany amt" font we ship with sas, in the title as follows... title "Here is the mu character: " font="albany amt/unicode" '03bc'x; proc gplot data=sashelp.class; plot height*weight; run; (With the caveat that it might depend on what graphical proc you're running, and whether you're using "gtitles", and what output device you're using.) Message was edited by: Robert Allison @ SAS ... View more

If it's a simple 1-character superscript that happens to have a character in the font you're using, you can specify the hex-code for that character, like this: axis1 label=(font="arial" "Squared" 'b2'x); proc gplot data=sashelp.class; plot height*weight / vaxis=axis1; run; ... View more

Hmm ... perhaps you're mixing-and-matching some options that don't work well together. Try using the code below, and make sure the gplot comes out looking right - if it doesn't look right, maybe something in your autoexec.sas, etc, isn't "playing well" with these options. Once you get it looking right, then swap your graphics proc for this 'proc gplot'. filename odsout '.'; goptions device=gif; goptions xpixels=400 ypixels=400; ODS LISTING CLOSE; ODS HTML path=odsout body="foo.htm"; proc gplot data=sashelp.class; plot height*weight / name="foo"; run; quit; ODS HTML CLOSE; ODS LISTING; ... View more

For my ods html sas/graph output, I use goptions xpixels & ypixels. I find that xpixels/ypixels let me specify *any* desired size, whereas (iirc) hsize & vsize were "constrained" by the limits set in the device files, or something like that. ... View more

Which proc are you using? I assume something GTL-based? (proc sgplot? a SAS/STAT proc with "ods graphics on"?) ... View more

Just glancing at the code you use to create your annotate data set, it looks like you're using the correct things to control the annotated text size ... hsys='3'; says that the number specified in the 'size' variable is % of screen size=3 and size=3.5 seem "reasonable" numbers. So, does the size= have no effect on the graph, if you change it? Try this with dev=gif ... perhaps this is one of the things that dev=activex only "partially supports"(?) ... View more

Which proc are you using, which output device are you using (gif, activex, etc), and which version of SAS are you using? ... View more

Not sure which wizard you're using (EG?), so I'm not sure how to get it to re-run your gchart code to produce the chart (which should now contain the annotated %'s). Maybe provide some more details on which wizard you're using, and somebody can give you some tips on that part. [Sorry, but I'm not familiar with any of the wizard interfaces - just the graph code!] ... View more

Hmm ... it's a little tricky to try to add this to code without some data, so I've retro-fitted your code to use sashelp.revhub2 (sample data) - should be simple for you to switch back to your own data, since I kept all the names the same! My code/changes are in lower-case, so they should be easy to find. Basically, I create a temporary data set in which I sum up the data so I can calculate the % (right now I'm calculating each bar segment as the % of that bar ... to calculate as the % of all the bars instead, just remove the "group by f1"). I make this temporary data set into an annotate data set, and then specify it in the anno= in the gchart ... ------------------------------------------------------------------------------------------------- PROC SQL; CREATE VIEW WORK.SORTTempTableSorted AS SELECT unique T.hub as F1, T.source as F3, sum(T.revenue) as F2 FROM sashelp.revhub2 as T group by hub, source ; create table my_anno as select unique *, sum(f2) as sum from WORK.SORTTempTableSorted group by f1; /* remove the 'group by f1' to calculate % of whole chart */ QUIT; data my_anno; set my_anno; when='a'; xsys='2'; ysys='2'; hsys='3'; function='label'; style='"arial/bold"'; size=2; position='5'; xc=f1; subgroup=f3; text=trim(left(put(f2/sum,percent7.0))); run; PATTERN1 COLOR=MAROON; PATTERN2 COLOR=CXFF6600; PATTERN3 COLOR=OLIVE; PATTERN4 COLOR=CXFFFFCC; PATTERN5 COLOR=BLUE; PATTERN6 COLOR=GRAY; PATTERN7 COLOR=RED; PATTERN8 COLOR = _STYLE_; PATTERN9 COLOR = _STYLE_; PATTERN10 COLOR = _STYLE_; PATTERN11 COLOR = _STYLE_; PATTERN12 COLOR = _STYLE_; Legend1 FRAME LABEL=(FONT='Microsoft Sans Serif' HEIGHT=8pt JUSTIFY=LEFT ) ; Axis1 STYLE=1 WIDTH=1 MINOR=NONE ; Axis2 STYLE=1 WIDTH=1 ; TITLE; TITLE1 "Support and Revenue"; FOOTNOTE; PROC GCHART DATA=WORK.SORTTempTableSorted anno=my_anno; VBAR3D F1 / SUMVAR=F2 SUBGROUP=F3 SHAPE=HEXAGON FRAME TYPE=SUM NOZERO LEGEND=LEGEND1 COUTLINE=BLACK RAXIS=AXIS1 MAXIS=AXIS2 ; LABEL F1="Year" F3="Name" F2="Dollar"; run; ... View more

If your response values really are percentages, then you can use "inside=sum". Here is an example: data foo; format value percent7.0; name='Bill'; value=.20; output; value=.50; output; value=.30; output; run; axis1 label=none; proc gchart data=foo; vbar name / type=sum sumvar=value subgroup=value inside=sum raxis=axis1 width=12; run; If your bar values are something other than percentages, and you want to print the percentages in the bar chart segments, you could calculate the percentages in another variable, and then annotate that value into the bar segments. Those are the first 2 techniques that come to mind - there might be others... ... View more

The plot and plot2 axes should display the values using whatever format is assigned in the data set, or you can specify a format in the 'proc gplot' to over-ride that. Here is an example of the latter: symbol1 v=dot i=join color=red; symbol2 v=none i=needle color=blue; proc gplot data=sashelp.stocks (where=(stock='IBM')); format close dollar5.0; format volume z10.; plot close*date=1; plot2 volume*date=2; run; (of course, with the limitation that device=java and device=activex might not support all the SAS formats, if you're using one of those devices) ... View more

Hmm ... I see 2 other alternatives (there might be other alternatives using GTL or sgplot, etc, that I don't know about). 1 - Use proc boxplot (or other sas analytics procs) to generate a data set containing the values describing the boxplot, and then use annotate to actually draw the boxplot geometry onto an empty gplot set of axes. This would take a bit of work, but it *could* be done this way (I've done something similar in a special dashboard before). 2 - Use dev=activex to draw the SAS/GRAPH gplot bar chart, and then have your QA person view the graph in a browser, and hover their mouse over the boxes to see the actual box values. This is still a bit manual/interactive, but at least you get to see the actual/exact numeric values used in the boxplot (median, low, high, 25th percentile, 75th percentile). Below is some code: %let name=plt036; filename odsout '.'; GOPTIONS DEVICE=activex; ODS LISTING CLOSE; ODS HTML path=odsout body="&name..htm"; symbol1 interpol=BOX25 color=black width=1 bwidth=4 mode=include; title "Activex boxplot: hover over boxes to see values"; proc gplot data=sashelp.cars; plot msrp * type; run; quit; ODS HTML CLOSE; ODS LISTING; ... View more

If knowing the exact numbers used in the boxplot is important, you might want to try "proc boxplot" (part of SAS/STAT, rather than SAS/GRAPH) - it has an "outbox=" option that will let you create a data set containing the actual numbers. http://support.sas.com/documentation/cdl/en/statug/63033/HTML/default/statug_boxplot_sect015.htm ... View more

I've never tried mailing sas/graph device=java output, but here's how I think it would go ... The person receiving the email & wanting to view the dev=java sas/graph output file would need to have the sas/graph jar file(s), and those files would need to be saved in the exact location that the "codebase" in the html file is pointing to. (And there might be some caveats that the html file and jar file have to be on the same 'web server' ... which could maybe be the local machine 'web server' looking at the local c: filesystem). In the past, you only needed a single jar file (such as graphapp.jar, mapapp.jar, or treeview.jar) to view the corresponding graph in the html file ... but in more recent versions I believe these jar files were split up (so that they could all use shared code), and therefore now you must have several jar files rather than just one. I haven't used the java graphs in this particular way (emailing them), and am not a java expert, so maybe one of the java-savvy folks can chime in and correct me if I'm wrong, and/or fill in any details I might have left out (or correct my terminology). 🙂 Typically, with the dev=java sas/graphs, I see people put the html files & jar files on a web server, and then email people a url/link to the html file (rather than trying to email everything). ... View more

Dan - In my experience, it would be very difficult to use ods htmlpanel to create a complex dashboard that looks similar to the Stephen Few one (I know this because I have tried! 🙂 Ods htmlpanel is fine for paneling several simple graphs on the same page, but when it comes to complex layouts, especially of differing sized & proportioned graphs, it gets very difficult to determine how to write your code to lay out the panels (not to mention, I often use overlapping panels in my dashboards!) Also, ods htmlpanel tends to put borders around each panel, and all those borders become very distracting & take up a lot of real estate on a densely-packed dashboard. And, as the user has recently mentioned that he's interested in a single-file approach so he can easily email the dashboard, without having to provide special directions for viewing it ... the dev=activex or dev=java graphs in ods htmlpanel output are probably not a good solution (because the email recipient would have to install the activex control, or have the sas/graph java jars set up properly to match the codebase, to view the graphs). ... View more