no, i don't close them. They normally don't move around until i've had the session open >6 hrs, or overnight, and when I have been working with multiple programs. The first hours after opening sas the tabs are well-behaved, so it will be hard for you to replicate. The only solution i see is to close the session and start it again, maybe that's what i'll have to do
... View more
cheers for the reply. I attach a photo: explorer, output, log and results tabs started on the left. But after running some programs etc, the programs move to the left and output and log tabs have started to wander to the right. When i go to check the log window I look to the left (i habit developed over 20 years) and it's not there. The tabs should be fixed in place and not move at all, for any reason at all the help documentation i linked to should still be sound. This problem started mayb 5 years ago(??) and i have just tolerated it, i assumed sas was moving things around according to how much they were used
... View more
I could not find a relevant board to post this, but any sas windows user might know how to fix the problem I'm experiencing. when using the Window Bar (described here: http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/viewer.htm#sassession.htm#dockview]) the tabs at the bottom of the screen move around eg Explorer, and the output and log windows. They don't move immediately, but after a long session they start shifting to the right and my programs shift to the left. It's quite irritating because i expect the log to always be on the left. I've tried turning off various options in the hope the tabs may start behaving, but nothing works.Anyone else experiencing this and frustrated by it? cheers
... View more
cheers for the response. The issue is about getting a clean import, that's all i'm concerned with, and i still don't have that. Yes, it's easy to assign formats etc post hoc, but it doesn't help me produce a clean log for documentation, that would be ideal. The example i gave in proc contents is not relevant actually, it's not one of the variables that's causing a problem, that was just a red herring, a distraction (in response to a previous usre's question) and it's not the main issue
... View more
good point. I ran proc contents and it shows the following for the affected variable: # Variable Type Len Format Informat Label
1 xxxxxxx Num 8 F1. xxxxxxx thus, i did the following and now the data are revealed to me (ie the issue is resolved): data a;
format a $50.;
set [dataset with the issue];
a=xxxxxxxx;
keep a;
run;
proc print data=a (obs=500);
var a;
run; i guess i can now proceed, but it's a bit disconcerting because i don't really understand all the kerfuffle....
... View more
thanks for the reply, but I think the issue is with the varchar format. The data are converted to "*" and the variable is not that long, maybe 12 characters. If i view the data, using print print or whatever, it appears as "*". What can i do to resolve this? edit: to try to get a sense of the format issue i did this: proc import
out=xxxxxx
datafile=".....\xxxxxxx.sav"
dbms=spss replace ;
fmtlib = WORK.FORMATS;
run;
proc format lib=work;
select [variable of interest];
run; but it doesn't reveal to me the format. It only says NOTE: PROCEDURE FORMAT used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds
NOTE: No formats found that match SELECT statement.
NOTE: At least one W.D format was too small for the number to be printed. The decimal may be
shifted by the "BEST" format.
... View more
I have read what I can find on this topic but it doesn't address my particular issue my code is as follows: options MSGLEVEL=I;
proc import
out=raw.data
datafile="....\data\spss\xxxxxxxx.sav"
dbms=spss replace ;
run; i get the following message in the log: NOTE: VARCHAR data type is not supported by the V9 engine.
Variable xxxxx has been converted to CHAR data type.
NOTE: Table has been opened in browse mode.
ERROR: Asterisks are an indication of a format width problem.
ERROR: Asterisks are an indication of a format width problem.
ERROR: Asterisks are an indication of a format width problem.
ERROR: Asterisks are an indication of a format width problem.
etc i've tried a number of ways to get around this, eg adding a format statement within proc import, but nothing resolves it. One of the affected variables is a key variable and thus I can't simply discard the subset of affected variables. any suggestions? cheers
... View more
excellent answers. I'll try all 3 approaches and report back.... i decided to use the "ods layout gridded" and it worked well. My code looks like this: ods pdf file="...\figure4.pdf";
title j=c h=1 "Figure 4. ....";
footnote ;
ods layout gridded columns=2;
ods region height=2.5in;
title ;
proc sgplot data=fig4 (where=(cohort=1)) noautolegend;
format cohort cohort_f. ...;
:
run;
ods region height=2.5in;
title ;
proc sgplot data=fig4 (where=(cohort=2)) noautolegend;
:
:
etc and this image looks like this: figure. I guess if i played around with it more i could create a tiff file instead of pdf, and refine it in other ways cheers
... View more
i'm trying to read up on gtl, given your suggestion, but the info out there seems scattered and incomplete. Eg, i generated my figure using sgplot. How do i now gain access to the proc template code which needs to be modified and is apparently hiding in the background somewhere? I ought to use that code as a starting point, if it's at all possible to create the fig as i want it. There are papers like this: http://support.sas.com/rnd/app/ODSGraphics/papers/modtmplt.pdf which imply that it's rather easy to obtain the source code, but what they suggest amounts to nothing.... cheers
... View more
i like this blog post by Sanjay Matange (@sanjay1 ?) https://blogs.sas.com/content/graphicallyspeaking/2014/01/18/two-in-one-graph/#prettyPhoto but how can i create a grid of such plots e.g. if i want a grid with 4 cells and each cell contains the kind of plot Sanjay has produced. Proc sgpanel does not allow the yaxis2 which achieves Sanjay's plot, and sgplot does not allow a panel. Thus, how to achieve both features...? cheers
... View more
sorry, i dont visit the message boards as frequently as i'd like to.... The code looks ok to me. Personally for clarity i might write it as: bounds b2<=1, b2>=1; xb = b0 + b1a*(Gender = 'female') + b2*log_TotalWordsInSentence + u; mu = exp(xb); and a minor thing: I'd reduce the length of the variable name 'CountPronounsInSentence' to make it readable, i didn't bother to read the loglikelihood equation ("ll = ")... because it's hard to read
... View more
excellent, youre right, it worked! it doesn't appear in the help page so i thought it wasnt an option: http://support.sas.com/documentation/cdl/en/grstatproc/62603/HTML/default/viewer.htm#panelvbox-stmt.htm
... View more
adding time to panelby would just generate a whole bunch more panels, one for each timepoint. Imagine a single figure within a single panel. In that figure i want timepoint on the x axis. There is no vbox in my code because it wouldn't produce what i need, that's the problem. My suspicion is that i need to use sgplot and greplay, but i hope not because that would be a hassle. I appreciate that's it's maybe not easy to visualise, i'd provide an example of what i need but nothing appears in a google search, that's why im asking here....
... View more
