About BrunoMueller

BrunoMueller · ‎05-05-2022

I am sorry but I can not help with this.

BrunoMueller · ‎04-13-2022

You can achieve the percent with 1 decimal by calculating the values with new dataitems, this will allow you to specify the format you want to use. Here is a screenshot comparing the two methods. The example uses sashelp.cars and the following dataitems: hp by type: AggregateTable(_Sum_, Table(_Sum_, Fixed('Type'n), 'Horsepower'n)) hp aggr: Sum [_ByGroup_] ('Horsepower'n) hp aggr / hp by type %: 'hp aggr'n / 'hp by type'n The barchart to the left uses the "Normalize groups to 100%" The barchart to the right uses the calculated dataitem "hp aggr / hp by type %"

BrunoMueller · ‎04-13-2022

As already mentioned a compute block on a specific column can only access the report-items that are to the left of it within the COLUMN statement. As a best practice I always create a _dummy computed column at the very end, this allows me to access any other report-item. Adding the NOPRINT option will avoid printing, but this computed column can also be used to display values for debugging purposes. proc report data=test; column stn avg1 avg2 avg3 _dummy; define stn / order; define avg1 /display; define avg2 / display; define avg3 / display; define _dummy / computed noprint; compute _dummy; if avg2 > avg3 then do; call define('avg2', "style", "style=[background=lightyellow]" ); end; endcomp; run;

BrunoMueller · ‎03-30-2022

To get each individual cell on a page use the ROWS=1 and COLUMNS=1 on PANELBY statement. The space between left y axis and the plot result can be controlled by using OFFSETMIN=0.12 on the COLAXIS stement. The textsize of the colaxistable can be controlled by the options valueattrs=(size=5pt) and labelattrs=(size=5pt).

BrunoMueller · ‎03-30-2022

Yes the sample code I provided creates a unique index on a column. That is not yet a PK definition. You would need to add the actual primary key deinition (which would also create the index, if it does not already exist). proc sql; alter table new_class add primary key (name); quit;

BrunoMueller · ‎03-16-2022

Actually there is any easier way which does not involve any GTL, but defining your own style, check out the sample below. /* * have a look at the default style definition * search for graphlegendbackground */ proc template; source styles.default; run; /* * now create your own style based on the default style you use * just change the definition for GraphLegendBackground */ proc template; define style mystyle; parent=styles.htmlblue; class GraphLegendBackground / backgroundcolor = ltgray color = ltgray ; end; run; /* * now create the graph using your own style definition * et voilà */ ods html5 file="c:\temp\legendbackground.html" style=mystyle ; proc sgplot data=sashelp.class tmplout="c:\temp\sgplot.sas"; styleattrs datacontrastcolors=(red blue green magenta yellow black) WALLCOLOR=LTGRAY datasymbols=(x x x circle circle circle Triangle Triangle Triangle); series x=age y=height / group=sex; keylegend / location=outside ; run; ods html5 close; Also check this paper, https://support.sas.com/resources/papers/proceedings17/SAS0675-2017.pdf, on the various style elements being used.

BrunoMueller · ‎03-16-2022

As a general rule always start with proc SGPLOT, SGPANEL etc. Only if there is not other way I would go for the Graph Template Language.

BrunoMueller · ‎03-11-2022

The KEYLEGEND statement does not support to set the background. Proc SGPLOT code is translated into the Graph Template Language (GTL), on this level it is possible to set the background of the legend. How to get the GTL from Proc SGPLOT, add the TMPLOUT= option, see below. proc sgplot data=sashelp.class tmplout="c:\temp\sgplot.sas"; styleattrs datacontrastcolors=(red blue green magenta yellow black) WALLCOLOR=LTGRAY datasymbols=(x x x circle circle circle Triangle Triangle Triangle); series x=age y=height / group=sex; keylegend / location=outside ; run; Have a look at the resulting file, this the GTL code used to create the graph. Now adapt the code by adding the BACKGROUND= option to the DISCRETELEGEND statement, see below for an example. ods path (prepend) work.mytemplates (update) ; proc template; define statgraph sgplot; begingraph / collation=binary subpixel=on dataContrastColors=( CXFF0000 CX0000FF CX008000 CXFF00FF CXFFFF00 CX000000 ) dataSymbols=( X X X CIRCLE CIRCLE CIRCLE TRIANGLE TRIANGLE TRIANGLE ); layout overlay / WallColor=CXC0C0C0 yaxisopts=(labelFitPolicy=Split) y2axisopts=(labelFitPolicy=Split); SeriesPlot X='Age'n Y='Height'n / primary=true Group='Sex'n LegendLabel="Height" NAME="SERIES"; DiscreteLegend "SERIES" / Location=Outside Title="Sex" backgroundcolor=ltgray; endlayout; endgraph; end; run; proc sgrender data=sashelp.class template=sgplot; run;

BrunoMueller · ‎03-07-2022

Use the kubectl command like so: kubectl -n yourNamespace get pods -l "launcher.sas.com/job-type=compute-server" -L "launcher.sas.com/username" The -l will select all pods that are compute servers, the -L will display the label that contains the username.

BrunoMueller · ‎02-24-2022

You can use variable lists in the define statement, see the example below. The variable lists specified are based on the variable in the input data set not how variables are listed in the column statement. See here for a doc on variable list: https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lrcon/p0wphcpsfgx6o7n1sjtqzizp1n39.htm proc contents data=sashelp.cars order=varnum short; run; proc report data=sashelp.cars(obs=30); column Make Model Type EngineSize Cylinders Horsepower MPG_City MPG_Highway Weight Wheelbase Length; define make -- type / display style={background=lightyellow}; define mpg_: / analysis sum format=z12.2 style={background=lightblue}; run;

BrunoMueller · ‎01-26-2022

I assume by YYYY_DD you mean year_month The code below uses the NLDATE function to build the string your are after. When you have nested DATA Step functions, each function needs its own %SYSFUNC. The %NRSTR macro function avoids warning messages. /*yymmd7. format - YYYY-DD*/ %let today2 = %sysfunc(nldate(%sysfunc(today()),%nrstr(%Y_%m))); %put &today2.;

BrunoMueller · ‎01-26-2022

Providing proc contents output of the data set bor would certainly help. I created some test data and everything is just printed fine, see code below. There might be issues with length or type of variables. proc format; value $dosegroupl (notsorted) '0.003' = '0.003 mg/kg' '0.03' = '0.03 mg/kg' '0.3' = '0.3 mg/kg' '2.5' = '2.5 mg/kg' '5.0' = '5.0 mg/kg' '10.0' = '10.0 mg/kg' '15.0' = '15.0 mg/kg' ; run; data bor; infile cards dlm=","; input mhdiag : $32. ; length exdosa1 $ 8; do exdosa1 = '0.003','0.03','0.3', '2.5', '5.0', '10.0','15.0'; output; end; cards; BOR PR (confirmed) unconfirmed PR ; proc tabulate data=bor missing; format exdosa1 $dosegroupl.; class mhdiag / order=freq; class exdosa1 / preloadfmt order=data; * preloadfmt forces the specific ordering defined in proc format; table mhdiag, exdosa1; run;

BrunoMueller · ‎01-21-2022

What version of SAS are you using? The doc says this about the QUERY option: The QUERY= option is available beginning with SAS Viya 3.5 and the November 2019 release of SAS 9.4M6 So might have to do with this.

BrunoMueller · ‎01-21-2022

I suggest to use Proc HTTP with the QUERY option to download what you need. See the code below for an example. Using the query option it is quite easy to provide name=value pairs in the url. %let time = 2021-11; %let cty_code = 1220; %let I_commodity = 12*; filename resp temp; proc http method="get" url='https://api.census.gov/data/timeseries/intltrade/imports/hs' query=( "get" = "YEAR,MONTH,RP,CTY_CODE,CTY_SUBCODE,DISTRICT,DIST_NAME,CON_QY1_MO,CON_QY1_YR,I_COMMODITY,I_COMMODITY_SDESC,I_COMMODITY_LDESC,CON_VAL_MO,CON_VAL_YR,CON_CHA_MO,CON_CHA_YR,GEN_VAL_MO,CAL_DUT_MO,CAL_DUT_YR" "SUMMARY_LVL2" = "HSCYCSDTRP" "COMM_LVL" = "HS10" "time"="&time" "CTY_CODE" = "&CTY_CODE" "I_COMMODITY" = "&I_COMMODITY" ) verbose out=resp ; run; libname resp json; proc copy in=resp out=work; run; libname resp clear; filename resp clear;

BrunoMueller · ‎01-20-2022

Please have a look at this blog post here https://blogs.sas.com/content/sgf/2020/04/15/getting-started-with-python-integration-to-sas-viya-part-1-making-a-connection/ it walks through how to connect to the CAS in SAS Viya for Learners.

Online Status	Offline
Date Last Visited	‎12-17-2025 09:19 AM