About snoopy369

snoopy369 · ‎11-19-2013

I get (in wlatin1,) x=Firma Vriend Rollï¿½ The last 3 characters are EFBFBD, which is UTF-8 for "FFFD" - the diamond question mark you see (wlatin1 doesn't parse that properly). That means that you already lost the actual character's value that was there before. You can compress that out individually as a character - try "FFFD"x or "EFBFBD"x, one or the other might work (I don't have a UTF8 version available at the moment, sorry).

snoopy369 · ‎11-19-2013

What version of SAS do you have? Desktop DisplayManager, Enterprise Guide, or Server EG or batch? What default language? If 9.3 or 9.4, did you install as Unicode Server? What does this code show on your SAS session? %put &sysencoding; What shows up when you do; data _null_; x="&testing"; put x= HEX.; run;

snoopy369 · ‎11-19-2013

I think the character is getting automatically converted to "?" (actual question mark character), presumably by your session not being a Unicode session. You can either run in Unicode (how to do so depends on your SAS mode, and may not have been installed by default by your SAS administrator) or you can just remove '?'. You also might be able to remove the specific character in the incoming data feed, depending on where the data is brought in from.

snoopy369 · ‎11-18-2013

I don't have time to check but I'd recommend looking at the style template, probably the TABLE or BODY element has some padding/margin in it. Most of the default elements do have a small amount. You could try running it with TAGSETS.STYLE_POPUP and seeing if it reports that margin coming from a particular element.

snoopy369 · ‎11-18-2013

Sure, but I wanted to use DISPLAY=NONE and kept getting errors I'm just suggesting including it, even if it does nothing, just to avoid people being confused by the inconsistency with most of the other plot types.

snoopy369 · ‎11-18-2013

Thanks. Also, as an aside, AXISTABLE's DISPLAY option is slightly quirky. DISPLAY=NONE is invalid in this context, and while I realize DISPLAY=STANDARD is probably roughly equivalent to that if you require the value labels, it would be nice if NONE was a synonym for that if nothing else - it was confusing to eventually realize I had to use DISPLAY=STANDARD which I basically never use.

snoopy369 · ‎11-18-2013

Hmm, actually a BlockPlot. Starting from Leroy Bessler's example where I saw this first (http://www.mwsug.org/proceedings/2012/DV/MWSUG-2012-DV13.pdf page 35 or so): proc sgplot data=sashelp.stocks tmplout="c:\temp\test.txt"; where date ge '01JAN2005'd; vline date / response=close group=stock markers markerattrs=(size=7 symbol=circlefilled) lineattrs=(thickness=3 pattern=solid) datalabel=close datalabelattrs=(family='Albany AMT/Bold' size=10 PT weight=Bold) datalabelpos=bottom; keylegend / noborder titleattrs=(family='Albany AMT/Bold' size=12 PT) valueattrs=(family='Albany AMT/Bold' size=12 PT); yaxis display=(nolabel noticks noline) grid offsetmin=0.05 /* space between top of datalabel table & bottom of plot area */ valueattrs=(family='Albany AMT/Bold' size=12 PT); xaxis display=(nolabel noticks noline) grid valueattrs=(family='Albany AMT/Bold' size=12 PT) values=(1 to 12 by 1); format close 5.; run; That takes me to this template code: proc template; define statgraph sgplot; dynamic _ticklist_; begingraph /; EntryTitle " " /; layout overlay / xaxisopts=( griddisplay=on display=( tickvalues ) TickValueAttrs=( Size=12pt Family="Albany AMT/Bold") type=discrete discreteopts=( tickValueList=_ticklist_ ) ) yaxisopts=( griddisplay=on display=( tickvalues ) offsetmin=0.05 TickValueAttrs=( Size=12pt Family="Albany AMT/Bold") type=auto ) x2axisopts=(type=Discrete discreteOpts=(tickValueList=_ticklist_)); SeriesPlot X=Date Y=_Sum1_Close_ / primary=true Group=Stock display=(markers) Markerattrs=( Symbol=CIRCLEFILLED Size=7) Lineattrs=( Pattern=1 Thickness=3) LegendLabel="Close (Sum)" NAME="VLINE"; innermargin / align=bottom; blockplot x=Date block=_Sum1_Close_ / class="Stock" display=(label values) valueHalign=center repeatedValues=true valueFitPolicy=shrink LabelAttrs=GraphValueText LabelAttrs=GraphDataText( Family="Albany AMT/Bold" Size=10 Weight=bold ) ValueAttrs=GraphDataText( Family="Albany AMT/Bold" Size=10 Weight=bold ); endinnermargin; DiscreteLegend "VLINE" / Location=Outside TitleAttrs=( Size=12pt Family="Albany AMT/Bold") ValueAttrs=( Size=12pt Family="Albany AMT/Bold") Border=false; endlayout; endgraph; end; run; The blockplot unfortunately doesn't look like it has reverse options either, nor does it reverse with the y-axis reversing.

snoopy369 · ‎11-18-2013

Thanks, Sanjay. That seems to be effectively identical to reversing the Y axis from my point of view, no? (ie, it makes the barchart reverse, rather than the axistable reverse which is my preference). I would look forward to seeing that option in a future release for the axis table Enjoying 9.4 GTL quite a lot, lots of useful new stuff in there. 9.3 used a scatterplot for the axistable, didn't it? Is that something that could be easily used and reordered?

snoopy369 · ‎11-18-2013

Indeed. Vince has it roughly backwards in his explanation - the issue is not that CALL SYMPUT is doing something at the wrong time, but that the use of the macro variable is often not done at the right time. IE, in this data step: data test; set sashelp.class; call symput('age',age); x_&age. = age; run; This doesn't work, not because the call symput runs after the x_&age statement, but because x_&age. needs to be able to set up during the compilation stage; CALL EXECUTE and the actual x_&age. assignment happen in the same timing. On the other hand, data test; set sashelp.class; call symput('age',age); array x_age[20]; x_age[symget('age')] = age; run; This works because you don't need to know the value of &age until execution time.

snoopy369 · ‎11-18-2013

I'm making a 100% Stacked Bar Chart with an axistable below it (to avoid labeling the bars which gets messy). By default, the order of the two are opposing; the bar chart puts the lower number on the bottom while the axistable puts the lower number on top. I was hoping to be able to reorder the axis table by reversing the Y axis for that table, but unfortunately don't seem to be able to (I'm guessing the axistable isn't even using the Y axis, for obvious reasons). I figured out two workarounds, but neither is optimal for my particular usage. One is to reverse the Y axis on the *barchart*, which does make the two match; but I prefer lower numbers on bottom. The second is to sort the dataset by the two variables but descending the second variable; in combination with reversing the Y axis on the barchart, this makes it look correct as long as I have the same categories exactly for each bar, which my data should. However, that sort itself is undesirable for the effects it has on my other charts, and I can't afford to re-sort the data twice for every set of charts as I'm making a few hundred thousand slides in total. Is there a way to reverse the axistable, or am I stuck with one of the workarounds above (or a different/better one?) The below code shows my example and a couple of workarounds. proc template; define statgraph test; dynamic pctval; begingraph/datacolors=(cxFF0000 cx00FF00 cx0000FF cxFFFF00 cxFF00FF cx00FFFF cxBBBBBB cx555555) datacontrastcolors=(cxFF0000 cx00FF00 cx0000FF cxFFFF00 cxFF00FF cx00FFFF cxBBBBBB cx555555); layout lattice/columnweights=preferred rowweights=preferred columndatarange=union columns=1 ; layout overlay/ /*yaxisopts=(reverse=1)*/ xaxisopts=(display=none); *WORKAROUND 1 and 2 - uncomment yaxisopts; barchart x=sex y=pctval/group=age; endlayout; layout overlay / walldisplay=none xaxisopts=( display=none griddisplay=off offsetmin=.1 offsetmax=.1) yaxisopts=(display=(tickvalues) offsetmin=.2 offsetmax=0 reverse=1) ; AxisTable x=sex value=pctval/ class="age" colorGroup=age Display=(Label); endlayout; endlayout; endgraph; end; quit; proc tabulate data=sashelp.class; where age le 15; class sex age; tables sex,age*rowpctn; ods output table=classpct(keep=sex age pct:); run; /* WORKAROUND 2 - uncomment this sort. proc sort data=classpct; by sex descending age ; run; */ proc sgrender data=classpct template=test; dynamic pctval='pctn_10'; run; Thanks!

snoopy369 · ‎11-15-2013

I'm mostly out of my depth here since I don't really know matrices very well (other than 'use IML' of course), but what I'm suggesting is writing MMULT to take as arguments all of the elements you want multiplied for one sim - it's a 2x2 array, right, so take as arguments eight values or whatever (in arrays or just as individual values), get all of those values on 1 row of a dataset, and call the function directly (once per by value, either from a dataset that is 1 record per sim, or at LAST.SIM) rather than trying to read from separate datasets. Most of the time in SAS, any answer that can be done in a normal data step will be superior to any answer that goes off and reads things on its own. I don't know matrices well enough to know what the potential issues are here, but it seems to me the straightforward answer should not be difficult.

snoopy369 · ‎11-15-2013

FYI - the non-c: link to that post is here: Six reasons you should stop using the RANUNI function to generate random numbers - The DO Loop

snoopy369 · ‎11-15-2013

Seems like you could do that in one pass of the data. I don't know CALL MMULT so perhaps you might have to abandon that and just do matrix multiplication directly, but does it really require dynamic arrays? Just use BY group and perform the same operation once per by group on a fixed array.

snoopy369 · ‎11-14-2013

LABEL works like FORMAT, the order doesn't matter except if there are two labels for the same variable. You need to post the contents of your formats/label files as there's something you're not explaining quite right.

snoopy369 · ‎11-14-2013

Does tst_fields.inc have a RUN statement in it? It probably does, if the formats are being ignored. That's a problem without a really good solution without editing these files. The best solution is probably to include the tst_format.inc in the tst_fields.inc file before its run statement but after the input statement. The even better solution is to get the format file to contain _all_ variables you need, if that's possible. RETAIN like Mit suggested is another possibility, as long as you always input all variables on each line (as long as there's no conditional input or anything like that in tst_fields.inc).

Online Status	Offline
Date Last Visited	‎10-10-2025 01:59 PM

Re: What is the state of SASGF 2022?

Re: Installing add-on package

Re: Help with ods output statement

Re: drill down from visual SAS Visual analytics

Applying control-based filters to subset of data

Re: EG 7.1 code lost during update

Re: Is there a way to use FIRST and LAST options within an IF THEN sta...

Re: Conexão SAS com Python para executar uma rotina

Re: How to transpose many columns to one

Re: Using a SAS Dataset instead of an External file in this interestin...

Re: Help with ods output statement

Re: What is the state of SASGF 2022?

Re: Editing the legend in a map

Editing the legend in a map

Make SAS Studio Log Window Honor the Alt Key

Re: Finding a value in all datasets in all variables

Re: Installing add-on package

Re: proc sgpanel x-axis with multiple scales

Re: Help with ods output statement

Re: Viya 3.5 on Ubuntu 18?

Git and SAS®: A Match Made in (SAS®) Studio

Re: Removing Special Characters

Re: Removing Special Characters

Re: Removing Special Characters

Re: How to use "Full Screen" option with ods PDF?

Re: GTL - Reverse order of AXISTABLE

Re: GTL - Reverse order of AXISTABLE

Re: GTL - Reverse order of AXISTABLE

Re: GTL - Reverse order of AXISTABLE

Re: PROC FCMP Subsection of Dynamic Array

GTL - Reverse order of AXISTABLE

Re: PROC FCMP Subsection of Dynamic Array

Re: PROC FCMP Subsection of Dynamic Array

Re: PROC FCMP Subsection of Dynamic Array

Re: [newbie] Ordering output in the same order as input

Re: [newbie] Ordering output in the same order as input

SAS Global Forum 2018

SAS Global Forum