About JeffMeyers

JeffMeyers · ‎06-10-2020

I would run ODS TRACE ON; prior to an example LOGISTIC procedure and note the parts of the output that you want to capture. Each segment will have a corresponding table name shown by ODS TRACE in the log. For example, the parameter estimates table that has the estimates and chi-square p-values is captured I believe in the ParameterEstimates table, so you could output it with the following before your LOGISTIC procedure: ODS OUTPUT ParameterEstimates=_parm; You can specify multiple tables in the same ODS OUTPUT statement. After that it's just figuring out how to merge the tables you want together to get your final output table.

JeffMeyers · ‎06-10-2020

I'm curious about this version. If all 5 NCXADMIT variables are missing does visit30days also get left missing in this case instead of 0? Would it be better to declare it as 0 first? Definitely agree with you on the variable naming conventions.

JeffMeyers · ‎06-10-2020

I would set it up like the following: data blah; set yourdata; array ncd {5} nc1admit nc2admit nc3admit nc4admit nc5admit; nvisits=0; do i = 1 to dim(ncdates); if inq30from le ncd(i) le inq30to then nvisits=nvisits+1; end; drop i; run; If I knew that there are no cases where nc1admit date could be missing but the other four could not (e.g. dates have to be filled 1-5 without skipping) then I would change to this to save processing time: data blah; set yourdata; array ncd {5} nc1admit nc2admit nc3admit nc4admit nc5admit; nvisits=0; do i = 1 to dim(ncdates)-nmiss(of ncd(*)); if inq30from le ncd(i) le inq30to then nvisits=nvisits+1; end; drop i; run;

JeffMeyers · ‎06-10-2020

I'm not sure if this would be helpful for you or not, but I have a macro dedicated to summarizing different types of data and outputting to different locations (like ODS EXCEL). There is an article here: https://communities.sas.com/t5/SAS-Communities-Library/Demographic-Table-and-Subgroup-Summary-Macro-TABLEN/ta-p/634030 I ran the following on your example data set and got the attached EXCEL file. %tablen(data=testing, by=county, showpval=0, var=maxrun minrun runs firstd lastd time reduce increase,type=1 1 1 1 1 1 2 2, shading=2,outdoc=~/ibm/test.xlsx,destination=excel);

JeffMeyers · ‎06-10-2020

You can specify the delimiter in COUNTW. I do that a lot in examples like: %let x=1,2,3,4; %do i = 1 %to %sysfunc(countw(%superq(x),%str(,))); %put %scan(%superq(x),&i,%str(,)); %end; %superq above just masks things like commas, quotes etc. When using commas as the delimiter though in a macro %sysfunc make sure you wrap it with %str to tell SAS it's a macro text string and not separating options. If in a data step then you would do COUNTW(x,',') if you are using a comma as the delimiter.

JeffMeyers · ‎06-10-2020

One of my favorite things to do is to write macros to make tables/graphics/reports/etc. Some of my best ones can be found on this site (NEWSURV, MVMODELS, TABLEN, CIRCOS, DATA_SPECS, COMPARE_ALL), and a new one that I have been developing has focused on making a Consort diagram. In the past I've had to use software like Word, Visio, and PowerPoint to make these diagrams as I hadn't found a way to do it programmatically. I've seen cases where an RTF document somehow has numbers filled in to an existing chart, but didn't like that approach. My macro focuses on using TEXT plots to make the text boxes and then connects them with line statements based on the anchors of the text boxes. Here is an example of one that I made with my current macro: The macro call that I needed to use to make this was: %consort(data=for_consort,id=subject, node=screened randomized treated ntrt4 ntrt8 ntrtv2 surg adj compadj, split=* arm, offreason=scrnrsn endatrsn endrsn2) The options stand for: DATA: one row per patient data set where the variables to be used in NODE live ID: patient ID variable used for counts NODE: list of variables that determine the different nodes (or boxes) in the consort. e.g. randomization, went to surgery, etc. The value of the variable is used as the text in the text box. Should only be one unique value within each branch of the consort. If a patient doesn't exist in the node then the value should be missing for that variable. SPLIT: Determines when the consort will split. Currently only works with one split, but am working to make it work with more. The node will still be shown (randomization in the above example), and then the split will happen and the counts will be shown for each level of the SPLIT variable. * indicates no split, and the last value of split is carried forward through further nodes if left missing OFFREASON: When a patient is found in one node but not in the following node, they are counted as going "off treatment" and placed into a box branching from the consort. The reasons listed in the box are pulled from these variables, with the label of the variable being used as the header for the text box. The last variable is carried forward through further nodes if left missing. The macro calculates the x/y coordinates of the boxes as well as the lines that connect them before drawing. There are also methods within the macro to manually make the dataset for more complicated consorts. My questions are: Does the macro call make sense to use? What are features that you would want in a consort diagram macro? Has this already been done before? I've seen SAS programs from SAS workers but not using the same methodology or automation Any feedback or suggestions are appreciated! I've been rather excited by the challenge of making this program.

JeffMeyers · ‎06-10-2020

How do you want the different groups shown? In different panels, with bars next to each other, or some other way? If it's in different panels then you could use your treatment variable in your PANELBY statement in SGPANEL and try similar code to make 2 or more different groups.

JeffMeyers · ‎06-04-2020

This is what I get in Firefox. Doesn't show up in IE. I'll try to do the survey in IE. Update: I tried in IE but the sliders didn't work (didn't change the fonts). Worked in Chrome so I went with that.

JeffMeyers · ‎06-04-2020

One potential issue I see in your code is this: data m1; set m1; if trtboxflag='Control,f' then xTCA2=xTCA; if trtboxflag='Dino,b' then xTCA3=xTCA; if trtboxflag='Dino,f' then xTCA4=xTCA; You are assigning separate variables for only three of the four values. That means when you use the original variable, xTCA for your "Control,b" group it is using ALL FOUR groups for it. Make a fourth variable for just this level like you have with the other three groups and I think your values will be correct in your pretty graph. It's hard to tell because the y-axes are different but I think your blue group is the only one that changes (the Control,b group).

JeffMeyers · ‎06-03-2020

The issue I was seeing is that your "column axis labels" are actually the panel headers from the panelby statement and these are not affected by COLAXIS as far as I know. I noticed that your TRTP variable was all the same value, so I changed your code to be an SGPLOT using the AVALN variable as the category variable instead. This puts the values into the x-axis which are then affected by the SPLITPOLICY. I made the graph wider as well since the labels are still squished. ods graphics / width=15in; proc sgplot data=forfig3 description="#byval1"; format pct mypct.; format avaln avalfmt.; by dtype2; styleattrs datacolors=(CX008000 CXFFFF00 CXFFA500 CXFF0000 CX000000); vbar avaln / response=pct stat=sum group=atoxgrn barwidth=.6 clusterwidth=1 datalabel datalabelattrs=(size=7 family=arial) ; xaxis fitpolicy=splitalways splitchar="*" label='Month' labelpos=left labelattrs=(size=9 family=arial); yaxis grid min=0 max=100 offsetmin=.01 offsetmax=.01 values=(0 to 75 by 25) labelattrs=(size=10 family=arial) valuesformat=best4.0 valueattrs=(size=8 family=arial) Label="Percent"; keylegend / noborder titleattrs=(size=9 family=arial) position=bottom title='Maximum Grade'; run;

JeffMeyers · ‎06-03-2020

Here is what I did making some random data that is similar: data m1; call streaminit(123); do i = 4 to 50 by 1; week=i;trt='Control'; if trt='Control' and week=4 then month='Jan'; if trt='Control' and week=5 then month='Feb'; if trt='Control' and week=11 then month='Mar'; if trt='Control' and week=15 then month='Apr'; if trt='Control' and week=19 then month='May'; if trt='Control' and week=23 then month='Jun'; if trt='Control' and week=27 then month='Jul'; if trt='Control' and week=31 then month='Aug'; if trt='Control' and week=37 then month='Sept'; if trt='Control' and week=41 then month='Oct'; if trt='Control' and week=45 then month='Nov'; if trt='Control' and week=49 then month='Dec'; do j = 1 to 100; xnest=rand("Uniform");output; end; month='';xnest=.; week=i;trt='Dino'; do j = 1 to 100; xnest2=rand("Uniform");output; end; output; end; run; proc sgplot data=m1; vline week / response=xnest stat=mean limitstat=stderr numstd=1 legendlabel='Control' name='one'; vline week / response=xnest2 stat=mean limitstat=stderr numstd=1 legendlabel='Dino' name='two'; styleattrs datacontrastcolors=(blue red) datalinepatterns=(solid solid); xaxistable month/ nolabel position=top title="Month in 2018" titleattrs=(weight=bold size=10) pad=(top=20 bottom=0); keylegend 'one' 'two'/ title='Treatment:' noborder outerpad=(top=25 bottom=0); yaxis label="Mean Percentage of Occupied Nest Boxes" LABELATTRS=(Size=10 Weight=Bold); xaxis label="Weeks Elapsed Since Treatment" LABELATTRS=(Size=10 Weight=Bold); format xnest percent12.1; run; title; When I tried your exact SGPLOT I used TMPLOUT to see what the actual GTL code in the background was doing. I found out that even though you didn't specify a CLASS option in the XAXISTABLE that it was applying one automatically. If I removed the CLASS option in GTL the extra space went away, but there wasn't a way to do this in the SGPLOT code. So I instead broke up your estimates variable into two (one for each treatment) and did two separate VLINE statements with no GROUP options. This cleared up the issue for me:

JeffMeyers · ‎06-03-2020

Can you change your values by a randomly generated number and then post the dataset? I don't really care what the numbers are but just having something with the same structure will allow me to test solutions.

JeffMeyers · ‎06-03-2020

Hello, I would like to help but find it easiest when actually trying things myself. Could you post your dataset as an Excel or something so I can try your code directly? Just the graph dataset used in the SGPLOT code.

JeffMeyers · ‎06-03-2020

Just wanted to let you know that the link pops up as a security risk website in Firefox.

JeffMeyers · ‎05-22-2020

I just wanted to point out that this is not true: Incorrect placing of the closing ")" for the compress function. This -> call symputx ('make',compress(make,' .'),'g') Should be -> call symputx ('make',compress(make,' .','g')) The 'g' option for the call symputx function specifies that the macro will be a global macro variable.

Online Status	Offline
Date Last Visited	‎10-10-2024 06:09 PM

Re: Methods to collect run code into a dataset?

Methods to collect run code into a dataset?

Re: Demographic Table and Subgroup Summary Macro %TABLEN

Re: Demographic Table and Subgroup Summary Macro %TABLEN

Re: Demographic Table and Subgroup Summary Macro %TABLEN

Re: Using array variable names with the NLITERAL function

Re: Using array variable names with the NLITERAL function

Using array variable names with the NLITERAL function

Re: Data Library Comparison Macro %COMPARE_ALL

Re: Kaplan-Meier Survival Plotting Macro %NEWSURV

Re: Methods to collect run code into a dataset?

Re: Methods to collect run code into a dataset?

Re: Using array variable names with the NLITERAL function

Re: List of Available TAGATTR?

Re: Struggles with Enterprise Guide Results Window Style Modifications

Applying a User Defined Function to SGPLOT Axis

Re: Sankey Diagram using Jeff's macro

Re: PROC TEMPLATE QUESTION to split the label into 2 lines

Re: Sankey Diagram, Decision Tree etc.

Re: How to display values for ticks on axis as percentage (e.g. 8%) i...

Kaplan-Meier Survival Plotting Macro %NEWSURV

Demographic Table and Subgroup Summary Macro %TABLEN

Methods of a Fully Automated CONSORT Diagram Macro %CONSORT

%MVMODELS: a Macro for Survival and Logistic Analysis

Library Datasets Summary Macro %DATA_SPECS

Re: macro - with automatic table creation (including P values) - pleas...

Re: Count of hospital admissions between 2 dates

Re: Count of hospital admissions between 2 dates

Re: Summary format report ideas

Re: Counting the number of phrases in a string?

Looking for Feedback and Suggestions: New CONSORT Diagram Macro

Re: SGPANEL can I wrap a formatted x-axis?

Re: UX feedback needed on SAS Graphs: Help us improve our labels!

Re: proc sgplot xaxistable- remove a treatment

Re: SGPANEL can I wrap a formatted x-axis?

Re: proc sgplot xaxistable- remove a treatment

Re: proc sgplot xaxistable- remove a treatment

Re: proc sgplot xaxistable- remove a treatment

Re: UX feedback needed on SAS Graphs: Help us improve our labels!

Re: Exporting same dataset to multiple excel files