Yes, they've put that warning in the log because in other languages (including SAS SQL) it means 'not equals'.   Makes me think it might be AI written. Taking wrong information from closely related documents is the sort of thing that LLMs do.  ... View more

"Note that the y-axis tick mark label "13" may be a bit misleading because it is rounded up from 12.5 due to the insufficient width of the format specification"   Well spotted!  I didn't expect that would happen (and yes, the format should be wider). ... View more

I thought it had uploaded. Anyway here it is again. Actually, on a bit more reflection, it might be the min= statement that triggers the problem. I get the same problem recurring when extra data points push the axis higher. Now I'm using a values statement, which seems to work. But it seems to me that this is a bug.  ... View more

Looks like the moderator has changed the solution to the correct one. Thanks all. ... View more

Can't see how to undo my solution choice. Is that possible? ... View more

This is perfect. I'm doing this when testing the program, and will re-create the datafile at the end. ... View more

OK, so not possible. (Of course, many of us are using EG with the data on the same machine, but I understand the general principle). ... View more

Thanks everyone for all the suggestions. I'll have to learn how to do annotations. SAS is obviously looking at which axis is closest to the max point for each line and putting the label on that axis. Unfortunately this is often pretty ugly. One simple enhancement for SAS would be to add an OUTSIDERIGHT choice to the CURVELABELLOC option to allow users to force output to the right hand side. A very simple work-around (which is actually workable for my graph today) is to change the y axis to have more white space at top and bottom - then the right axis will always be closer. ... View more

Mainly just habit. This allows me to customise the appearance of each line manually. Would reshaping the data and using groups force a line-up of the labels? ... View more

Here is a work-around. I create two dummy cases at the end. But this wouldn't work if I had data point markers. * Curvelabel; data dat; input date var1 var2; cards; 1 10 20 2 15 25 3 11 . 4 18 . ; run; data dat2; retain retainvar1 retainvar2; drop retainvar1 retainvar2; set dat end=lastobs; if not(missing(var1)) then retainvar1 = var1; if not(missing(var2)) then retainvar2 = var2; output; nextdate = lag(date)+1; nextdate2 = lag(date)+2; drop nextdate nextdate2; if lastobs then do; date = nextdate; var1 = .; var2 = .; output; date = nextdate2; var1 = retainvar1; var2 = retainvar2; output; end; run; Title "Adding two dummy observations at end works if I don't have data point markers"; proc sgplot data=dat2; series x=date y=var1 /curvelabel curvelabelloc=outside break; series x=date y=var2 /curvelabel curvelabelloc=outside break; run; title; proc sgplot data=dat2; series x=date y=var1 /curvelabel curvelabelloc=inside curvelabelpos=max break; series x=date y=var2 /curvelabel curvelabelloc=inside curvelabelpos=max break; run; proc sgplot data=dat2; series x=date y=var1 /curvelabel curvelabelloc=inside curvelabelpos=max break; series x=date y=var2 /curvelabel curvelabelloc=inside curvelabelpos=max break; yaxis values=(1 to 100); run; run; ... View more