One other bit of information for anyone in the future working with very large survival datasets:   In addition to reducing the size of the dataset by removing duplicate censored events, I also reduced the size of the work.survival dataset by rounding calculated time values to one decimal place (i.e., before using LIFETEST). Initially my time values (in years) were created with 8 decimal places which is an unnecessary amount of precision. If I used that level of precision for the time values, the LIFETEST table would produce 30K observations even after removing duplicate censored values. If I round the time values to one decimal place before creating the LIFETEST table, the final dataset has 900 observations after removing duplicates. ... View more

Your code confirms exactly what I suspected! But I was not sure which variables to include on the NODUPKEY by statement. Your solution works perfectly with my real dataset and produces a graph with a proper XAXISTABLE in 10 seconds.   Thank you!!! You have no idea how relieving it is to figure this problem out!   One question though: I am not familiar with the _ALL_ variable that you used on the by statement. If I understand correctly, using _ALL_ after the first two variables (time stratumnum) has the effect of including all possible combinations of every other variable without actually having to write those all out. Is that correct?   Thanks again! ... View more

@Rick_SAS : I don't think it is a label problem because I created label variables separately and there are only a handful in the huge dataset. The only labels are for quartile values. If you have a minute to check my data, I've posted code to generate a simulated datafile above. ... View more

Thanks so much for your help, @Quentin !   There are about 367K records in KMSurvivalPlotOffType. Most of these records appear to be repeats of censored events. I'm wondering if those records can be summarized to reduce the size of the dataset but I'm not sure how that might be done.   One more thing: I am not plotting censored events because there are so many that the entire curve would be a solid line of censored tick marks.   I have posted the log below that results from running the SGPLOT code for my actual data.  The plot failed after running for 45 minutes with "ERROR: Java virtual machine exception. java.lang.OutOfMemoryError: Java heap space."   I have also included code below for a simulated work.Survival dataset. This is my first time writing such code so hopefully I've done so correctly. I couldn't figure out how to make the simulated data follow the same distribution as my original data but I don't think that matters for troubleshooting purposes. In my actual data the time variable (FollowY) is right-skewed and one group (OffType) is right-skewed more than the other.   *SIMULATED WORK.SURVIVAL DATASET; data SurvivalTemp; do ID = 1 to 644265; Drug = rand('Bernoulli',0.6739); FollowY = round(22*rand('Uniform'),0.1); Fail = rand('Bernoulli',0.4309); output; end; run; data SurvivalSIM; set SurvivalTemp; if Drug=1 then OffType="Non-Drug"; else OffType="Drug"; Drop Drug; run;     1 The SAS System 11:11 Saturday, March 23, 2024 1 ;*';*";*/;quit;run; 2 OPTIONS PAGENO=MIN; 3 %LET _CLIENTTASKLABEL='22_Survival.sas'; 4 %LET _CLIENTPROCESSFLOWNAME='Standalone Not In Project'; 5 %LET _CLIENTPROJECTPATH=''; 6 %LET _CLIENTPROJECTPATHHOST=''; 7 %LET _CLIENTPROJECTNAME=''; 8 %LET _SASPROGRAMFILE='X:\22_Survival.sas'; 9 %LET _SASPROGRAMFILEHOST='82461-CJIS'; 10 11 ODS _ALL_ CLOSE; 12 OPTIONS DEV=SVG; 13 GOPTIONS XPIXELS=0 YPIXELS=0; 14 %macro HTML5AccessibleGraphSupported; 15 %if %_SAS_VERCOMP_FV(9,4,4, 0,0,0) >= 0 %then ACCESSIBLE_GRAPH; 16 %mend; 17 FILENAME EGHTML TEMP; 18 ODS HTML5(ID=EGHTML) FILE=EGHTML 19 OPTIONS(BITMAP_MODE='INLINE') 20 %HTML5AccessibleGraphSupported 21 ENCODING='utf-8' 22 STYLE=HTMLBlue 23 GPATH=&sasworklocation 24 ; NOTE: Writing HTML5(EGHTML) Body file: EGHTML 25 26 ods listing gpath='\\Figures\' image_DPI=300; 27 ods graphics / reset 28 height=6.5in imagename="Figure100&Z" imagefmt=PNG ATTRPRIORITY=NONE ANTIALIASMAX=378300; 29 Footnote justify=left height=1.2 font="Times New Roman" "Figure X.XX. Kaplan-Meier Survival Curves"; 30 Title; 31 32 32 ! proc sgplot data=KMSurvivalPlotOffType noborder; 33 where Time<=20; 34 format AtRisk comma.; 35 series x=Time y=Survival / 36 lineattrs=(pattern=solid) 37 Group=Stratum 38 Name='S'; 39 scatter x=Time y=Percentile / 40 group=Quartiles 41 markerattrs=(symbol=circlefilled size=7) 42 name='Q'; 43 text x=Time y=Percentile text=Years / 44 group=Stratum 45 textattrs=(size=10) 46 position=PositionVar; 47 xaxistable atrisk / 48 x=tatrisk 49 class=stratum 50 colorgroup=stratum 51 valueattrs=(weight=bold) 52 location=inside; 53 Inset ("Drug vs. Non-Drug:" = "0.93") / 54 border 55 Title="Hazard Ratio" 2 The SAS System 11:11 Saturday, March 23, 2024 56 titleattrs=(size=10 weight=bold) 57 textattrs=(size=10) 58 Position=Top; 59 keylegend 'S' / 60 linelength=20 61 title="Type" 62 exclude=(" ") 63 Titleattrs=(size=10) 64 Valueattrs=(size=10) 65 location=outside 66 position=bottom; 67 keylegend 'Q' / 68 title="Survival Probability Quartiles" 69 titleattrs=(size=10 weight=bold) 70 exclude=("." "25") 71 down=3 72 location=inside 73 position=TopRight 74 Valueattrs=(Size=10) 75 noborder; 76 yaxis label="Survival Probability" 77 grid values=(0 to 1 by 0.10); 78 xaxis label="Years" 79 grid values=(0 to 20 by 2); 80 run; NOTE: PROCEDURE SGPLOT used (Total process time): real time 44:04.98 cpu time 20.87 seconds ERROR: Java virtual machine exception. java.lang.OutOfMemoryError: Java heap space. NOTE: The SAS System stopped processing this step because of errors. NOTE: There were 364490 observations read from the data set WORK.KMSURVIVALPLOTOFFTYPE. WHERE Time<=20; 81 82 83 %LET _CLIENTTASKLABEL=; 84 %LET _CLIENTPROCESSFLOWNAME=; 85 %LET _CLIENTPROJECTPATH=; 86 %LET _CLIENTPROJECTPATHHOST=; 87 %LET _CLIENTPROJECTNAME=; 88 %LET _SASPROGRAMFILE=; 89 %LET _SASPROGRAMFILEHOST=; 90 91 ;*';*";*/;quit;run; 92 ODS _ALL_ CLOSE; 93 94 95 QUIT; RUN; 96         ... View more

Thanks for your help, @ballardw    The dataset is quite large so I have attached the code as a text file. ... View more

Thanks for the great suggestions, @DanH_sas  and @yabwon !   I used Dan's strategy and I am almost there. Any ideas on why the LEFT datalabel wants to sit exactly on the line? Is there a way to pad it over to the left a little bit?   Thanks again!     *GRAPH - All; ods listing gpath='\\Figures\' image_DPI=300; ods graphics / reset height=6.5in imagename="Figure100&Z" imagefmt=PNG ATTRPRIORITY=NONE ANTIALIASMAX=378300; Footnote justify=left height=1.2 font="Times New Roman" "Figure X.XX. Survival Function"; Title; proc sgplot data=SurvivalPlotOffType noborder; series x=Time y=Survival / lineattrs=(pattern=solid) Group=Stratum Name='S'; scatter x=Time y=Quartiles / markerattrs=(symbol=circle size=7) name='Q'; text x=Time y=Quartiles text=Years / group=stratum textattrs=(size=10) position=PositionVar; keylegend 'Q' / location=inside position=right Valueattrs=(Size=10); yaxis label="Survival Probability" grid values=(0 to 1 by 0.10); xaxis label="Years" grid values=(0 to 20 by 2); run; ... View more

Thanks @yabwon and @DanH_sas for your suggestions! However, I am hoping to find a strategy that plots each group side-by-side so that each yearly cohort can be compared without referring to any values on the Y-axis. For example, my existing vbar plots show that for cohorts 2000 - 2004, group A (left) had a higher Time-to-Failure than group B (right), but this trend reversed for cohorts 2005 onward (group B had a higher TTF) than group A). ... View more

Brilliant, Ksharp!   However, I don't understand why the "want+1" works correctly if the "want" variable is not retained. I think (incorrectly?) that "want" will only have a value of 1 for first.ID and otherwise will be set to missing. So how does "want" equal 2 when the formula (in my mind) is "missing (.) + 1"? It seems like the value of "want" is being retained from the prior record but this variable has not been listed in the "retain" statement.   Can anyone help me understand? ... View more

You make some excellent suggestions, ballardw. I guess I didn't assume that Word was correct per se, only that the font size output from SAS does not exactly match the font size output from Word. I am comparing output on the same monitor as well as printed copies (which appear to match the monitor). When I paste the images into Word (with gridlines turned on to gauge size and position), the size and dimensions of the pasted images do not appear to change. Also, when I right-click the image and check the dimensions, they are as expected (exactly 6.5" high with no scaling and the aspect ratio locked). So as far as I can tell, Word is not changing the images after being pasted. I'm mostly confused about why changing the DPI in SGPLOT seems to slightly change the font size, even when the NOSCALE option is used. I'm also confused why the graphs displayed in the SAS output window appear to be scaled correctly and do not change when the DPI is changed but the PNG images output seem to be scaled differently depending on the DPI. ... View more

After some more investigating it appears that no combination of font size, NOSCALE, and DPI actually produces a 12-point font that exactly matches a 12-point font in Word. I previously thought that the default 96 DPI and font size 12 was an exact match, but it actually is not. I have found that when requiring 300 DPI and using the NOSCALE option that an 11.5-point font size is a close but not exact match.   Is the slight discrepancy in font size between SGPLOT and Word expected behavior? ... View more

Thanks for your reply, ballardw.   The text is not scaled very much and is most noticeable for the footnote text (actually the title but placed at the bottom). Unfortunately, the footnote/title is the only text that I definitely need in exactly 12-point font size. Other text also appears to be scaled. The scaling happens with the default font as well as the Times New Roman footnote font I have specified.   Unfortunately the data is sensitive so I can't post the original graphics, but I have reproduced the bottom of the graph with an example title and attached here.   This first image is the default 96 DPI and the footnote text is exactly 12-point font. Notice where it ends (just below the 900 mark on the x-axis).     This second image is 300 DPI and the footnote text is larger than 12-point font. Notice that it ends beyond the 1,000 mark on the x-axis.     Thanks for your help! ... View more