Please provide the ENTIRE log for this PROC SQL. (We don't want 100s of lines before or after this PROC SQL, just the log for this PROC SQL)   Please copy the log for this PROC SQL as text and paste it as text into the window that appears when you click on the </> icon. DO NOT SKIP THIS STEP. ... View more

The last eigenvalue indicates the collinearity problem. Most of the variability of the intercept and col12 are explained by the last eigenvalue. This probably is cause by col12 being almost all zeros (or all ones), meaning they are highly correlated. In additon, there are other columns with values > 0.7 in the last row, these two other columns indicate most of the variability is in the last eigenvalue, but not as much as col12. ... View more

@wateas wrote: Part of the issue, I think, is the default designation of the reference level.  For the factor "Trt_CC", the reference level being "no_CC" is good, but for "Weed_Rating", the reference level probably shouldn't be 5, because that is the rating for the most weedy plots and is exerting the most influence.  I'll figure out how to set the reference level, and I think I might already have an idea of how to exclude it from the dummy variable.  BRB I disagree completely, reference level has no impact here. ... View more

When you use dummy variables to replace a categorical variable, and there are n levels for this categorical variable, you want to use n-1 dummy variables. So what happens if you re-run the analysis and take col10 and col15 out of this analysis? ... View more

It means your employer or your university needs to renew the license. They probably know about this already. ... View more

Is there a format applied to variable CIG1RP?   What does PROC CONTENTS say for this variable regarding the presence or absence of a format? Please run PROC CONTENTS on the data set used in PROC PHREG and show us the (relevant parts of the) output.   Corrected: Replaced PROC FORMAT with PROC CONTENTS ... View more

  @sathya66  When I first posted the code for DATA WANT; I left two lines out, that is now corrected in my reply above, but you need to modify your code to show those changes I made. ... View more

Thanks, but I asked you to explain the logic you want to use, this doesn't explain, and doesn't answer my question. (In case its not clear, explain means write words to describe the steps to go from data set 1 to data set 2) ... View more

Please explain the logic used to obtain data set 2 from data set 1.   May I also recommend that in all of your future posts, the logic should be explained. ... View more

@primmer300174 wrote: The ask of me is to have interval data per agent for productivity. but if the interval ends at 16:45:00, that would be classed as 0.5 for that interval as they are not productive for the whole 30 min interval. Hope this clarifies what I have asked for So, please explain why your desired data is a 30 minute interval for record 1, but 15 minute intervals for records 2 through 4. Also, please SHOW us a portion of the input data in data set SCHEDULE2. ... View more

Please explain further. You say you want 30 minutes intervals, but in the bottom table (which is what you want to get) you have mostly 15 minute intervals.   Also, we would need to see a portion of the starting data, which you have not shown us. (In other words, we need to see a portion of data set SCHEDULE2) ... View more

ODS EXCEL has an option to put each BY group into a different worksheet.   ods excel file='myexcel.xlsx' options(sheet_interval='BYGROUP'); proc report data=xxx; by variablename; ... run; ... View more

@alepage wrote: I have tested my code and I have found that for the else condition, an output statement is fine.  But for the if condition, I do not need to replace the dataset but to append the data generated. So my question is how do we do that. How do we convert the condtion  if inlist and inbase then output dest2.&filename._Anonym;   if inlist and inbase then do; proc append base=dest2.&filename._Anonym; data= what do we put here; run;   You cannot put a PROC inside a DATA step. I already provided an earlier post in this thread explaining what to do instead.   This whole thread is the XY Problem. You have a "solution" that requires you to put PROC APPEND into a DATA step, but you are having trouble doing it. You haven't told us the problem that this allegedly solves, and it would be extremely helpful if you backed up and explain the entire problem you are trying to solve, rather than focusing on your solution of putting a PROC into a DATA step. Please note that backing up and explain the entire problem, rather than focusing on your desired solution, is a far superior approach that can produce much better solutions, involving less code and less confusion.   So if we're going to move forward, we first have to move backward and understand what the problem is that you are trying to solve with a PROC in a DATA step. ... View more