SAS Studio have "Server Files and Folders" that allows to Drag & Drop files and folders. While it can be convenient, it can be source of accidental file or folder shifts.  There can be examples of folders (e.g., because they were close in favorites) silently moved into distant folder without user noticing it and then it can be very hard to find who moved file, where or when it was moved. Please add option(s) (below listed by preference how to risk mitigate) to: 1) add confirmation dialog for drag and drop (it exists in WinSCP and aimed to minimize similar incidents) 2) turn off drag and drop functionality   ... View more

Is it forseen to work with SAS notebooks in SAS Studio (just like Jupyter Notebooks) via a web bowser? ... View more

I know this has been suggested before, but the issue was closed. (https://communities.sas.com/t5/SAS-Visual-Analytics/Mouse-wheel-graph-interaction/td-p/435358) We are about to publish reports for a big number of users with low computer experience. Using VA is a very small part of their daily job. To educate them all on how to avoid unintended zooming in graph objects, is not a feasible task. A possibility to deactivate mouse wheel zoom would be a great increase in usability for our VA reports, and massively reduce our support burden. I really hope you can consider implementing this soon. Thanks in advance. ... View more

Our users are often not very impressed with the reports me and my colleagues make for them. The reason is that they only see the first tab of the report. The tabs are so subtile that the users don't even see them. It's also hard to see which tab is selected. Please make it possible to style the tabs so that we can make them "pop" more.   Picture to show what I mean: Picture of "invisible" tabs in a VA report     ... View more

For data export in SAS VA (SAS Viya also?) only data type Excel, Delimeters Tab and Comma are possible. Please add option to use different compound delimeter like ';' or '##', etc.   ... View more

I have a bunch of SAS files in a directory, that I'm running using sas-viya at the command-line with. Here's the command line I use:   sas-viya batch jobs submit-pgm --context default --wait-results --pgm basic_digits.sas   I have two product suggestions that would reduce some friction:   First, I end up with a bunch of JOB folders with undistinguished names. For example here are three in the folder right now: JOB_20240510_011340_087_1 JOB_20240514_201600_284_1 JOB_20240514_202431_319_1   Without going inside of them... which of those was used to run basic_digits.sas, which was used to run advanced_digits.sas, and which was something else?   I would like to be able to provide a parameter to sas-viya that adds something after the JOB_ , and a way to default to having the name of the SAS program there. I would like something like "--results-dir-prefix" that would create this: JOB_basic_digits_20240510_011340_087_1   I *could* create one "output_{}" folder for each file and use "output_basic_digits" with --dir flag, but I wish for something where I don't have to modify the command line in two places for each job with different filenames [high susceptibility to human error]. You could also use the job name from --job-name, but that still suffers the "two command line edits" problem.   Second, "--context default" shouldn't be necessary. If one doesn't provide the context, it should use the default.   Thank you, Gary ... View more

Prometheus currently only tracks active jobs, with no visibility into completed ones. Once jobs finish, their status information from the Workload Orchestrator is not available to prometheus, limiting post-completion monitoring and analysis. It would be beneficial to externalize this data to Prometheus for better job status tracking.  ... View more

Data Driven Content objects are not only used for visualizing data. They are also the key to innovative ways to select/subset what data to display in the report. (For example the TreeSelector). Therefore it would be very useful if DDC objects could be used exactly as Control object, including being put in the reports controls area and the page controls area of the report. Implementing this would really be a game changer for us. ... View more

Request: Please can SAS include the option to calculate test statistics for the unadjusted and stratified MN method.   Background: Miettinen-Nurminen (MN) methods are increasingly being requested by regulatory agencies. This is particularly relevant for non-inferiority trials where it's appropriate for the variance to be estimated under the null hypothesis. Within the PROC FREQ procedure, it's currently possible to calculate the treatment differences (and CIs) for both the unadjusted MN and the stratified MN methods as well as other MN tests such as the Summary Score method (also referred to as Agresti Score). However, whilst for the Summary Score method SAS allows the option to calculate the test statistics this is not yet available for the unadjusted MN method or the stratified MN method.   These methods are important as they estimate variance under the null hypothesis, specifically the test statistics are of particular useful for: testing superiority and presenting a p-value studies with interim analyses, particularly when multiplicity is controlled via a group sequential design i.e. with alpha boundaries less than the typical 1-sided 2.5%/2-sided 5% alpha Example SAS code (for reference): Note: data not supplied due to proprietary nature, however code shared to illustrate current options/limitations.  The unadjusted MN treatment difference can be calculated using: proc freq data=DATA; tables TRT*AVAL / riskdiff(CL=(MN) noninferiority margin=0.1);  run; Note: whilst the (unadjusted) Wald test statistics are calculated, it would be helpful if the unadjusted MN test statistics could also be provided. The stratified MN Score treatment difference can be calculated using: proc freq data=DATA; tables STRATA*TRT*AVAL / riskdiff(CL=(MN) noninferiority margin=0.1) COMMONRISKDIFF(CL=(MN score) test=(score)); run; Note: whilst the (adjusted) Summary Score (also referred to as Agresti Score) test statistics are calculated, it would be helpful if the stratified MN test statistics could also be provided. Specifically, if MN could also be an option within COMMONRISKDIFF(TEST=( )) ... View more

HPSplit is in Base SAS/STAT as a standard offering. Random forests are a staple of predictive modeling. Move HP Forest out of SAS Enterprise Miner and put it in the SAS/STAT product. Random forests are 20 years old now, it is nowhere near a novel technique.   There are other packages that need moving over but this one is a no-brainer, at least to me. ... View more

I have two ideas for SAS Visual Analytics "Distribute reports" feature.    Ability to change the font (or any images) in the email that is sent with the distribution, and Ability to copy a list of recipient emails especially the feature will be useful if it is a large list of emails   Thanks ... View more

Partial least squares logistic regression is a good method of dealing with collinearity in logistic regression. Currently, it is not supported by SAS, so I think it necessary to include it in SAS/STAT. ... View more

Hi! Proc Means and Proc Univariate at present lack fast and accurate methods for calculation of quantile, means and standard deviation for large sets of data. In the paper "Fast and Accurate calculation... "  by Anders Sköllermo I point at a possible method.   Suggestion: Look at this method. Develop it further to be a general method and implement it in the SAS procedures. Future: I think that this method can also been very good when using several computers or parallel computers or computer networks   and also on streaming data.  However the method has not at al been tested for this. (The environment I had was SAS on demand for Academics). /Br Anders Sköllermo ... View more

The SAS EG editor, where I spend most of my day, could be much improved. I'd like to make the following suggestions to make my work easier and more efficient:   When opening a file in SAS EG, it doesn't use a standard Windows file open dialog box. Instead, you must first select from Recent, My Computer, Servers, etc. If you select My Computer or Servers, you then need to select the folder. It should just open to the last accessed folder with one click. Making all of these selections every time is annoying and unproductive. Because it does not use a standard Windows file dialog, the folder of the file you are editing is not displayed, but it should be. Since you have the ability to open local or remote files, it would be very helpful if you had a window similar to WinSCP, enabling easy file transfer between your local machine and a server. In the log window, clicking on Errors, Warnings, or Notes does not correctly subset the list below to display Errors, Warnings, or Notes. Block copy (Alt + left mouse button + drag) does not work correctly (as it does in Notepad++). You can't create a block past the end of a line - you need to insert spaces first, or you will have a jagged left edge to your selection. SAS should automatically insert spaces to match the width of the selection or the line above. You can't select a vertical line and begin inserting characters. If you want to insert a vertical block of text, you need to insert it one row at a time manually. This functionality is very easy in most editors and would save me a lot of time. When performing a replace in a selection of text, the replace dialog should stay open and the selection stay selected so that you can make another replacement without having to re-select the text. It would be nice if you could easily flag a row by clicking in the left margin, similar to what you can do in Notepad++, so that you can easily find that row again after scrolling up or down. It would be helpful to have a count of the number of rows selected at the bottom of the screen, like in Excel, so that you can easily count code lists and the like. ... View more

As I understand the situation, a "spike and slab" prior in PROC MCMC cannot now be specified because this distribution requires a combination of a DGENERAL and GENERAL distribution. [Regarding "spike and slab", see the reference:  https://www.mv.helsinki.fi/home/mjxpirin/HDS_course/material/HDS8_variable_selection.html] The "spike and slab" prior for a predictor X would support "variable selection" when using PROC MCMC.  To fully implement the approach given in the reference above, the functionality of the R package called BoomSpikeSlab would be needed. See https://cran.r-project.org/web/packages/BoomSpikeSlab/index.html ... View more

Sample code, based on SAS Usage note 22883 http://support.sas.com/kb/22/883.html   data a; do Rater1=1 to 2; do Rater2=1 to 2; input Wt @@; output; end; end; datalines; 0 3 0 3 ; run; proc freq data=a; weight Wt / zeros; tables Rater1*Rater2 / agree nocol norow nopercent plots=none; run;   This code generates a 2x2 table to estimate Cohen's Kappa with standard error and confidence interval. One of the margins has a sum of zero, but it is forced to fit a 2x2 table using the weight statement and zeros option. The results are that the estimated Kappa is zero, the standard error is zero and the Confidence Interval is (0 to 0).   I've convinced myself that the standard error result is numerically correct, having checked the result using equations in the documentation and the cited reference. I think it is a special case for 2x2 tables, since the usage note above gives an example for 4x4 tables, and the resulting standard error is strictly positive. That said, an estimated statistic having no variability might not appear correct to a reader.   I suggest that 1) PROC FREQ provides a warning/note in the log/output to draw attention to this anomaly. 2) Ideally, if there are suitable improved formulae that don't have this defect, could they be implemented as an alternative option? (I admit, I don't have a better suggestion in mind).   Reference: Fleiss JL, Cohen J, Everitt B. (1969) Large sample standard errors of kappa and weighted kappa. Psychological Bulletin. 72 (5) 323-327. https://api.semanticscholar.org/CorpusID:85541244, https://doi.org/10.1037/H0028106 ... View more

To view how well the model discriminates those with and those without the event, the user needs the area under the receiver operating characteristic curve (AUC). However, the options for the users are limited when the INMODEL= option is specified in the PROC LOGISTIC statement, with AUC only available when the user specifies both the SCORE statement and the FITSTAT option. But a big deficit in the process is the lack of confidence interval of AUC, which is automatically computed and displayed in the ROC statement but is not available when the INMODEL= option is specified in the PROC LOGISTIC statement. Therefore, when the user is validating a model, he/she cannot obtain it directly. What is more, the formula of the standard error of the AUC is not reported in anywhere of SAS Help, so the user is unable to calculate the confidence interval on his/her own. Therefore, I suggest that SAS (1) automatically compute the standard error and confidence interval of the AUC when the INMODEL= option is specified in the PROC LOGISTIC statement; (2) include the formula of the standard error of AUC in SAS Help. ... View more

Currently, PROC MIXED can implement just one type of heteroscedasticity consistent estimator of the variance, namely the Huber-White / empirical / sandwich / HC0 estimator; this is accomplished with the EMPIRICAL option on the PROC MIXED statement in conjunction with the SUBJECT= option on either the RANDOM or REPEATED statement:  https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_mixed_syntax01.htm#statug.mixed.procstmt_empirical   PROC REG, on the other hand, can implement 4 types of heteroscedasticity consistent estimators: HC0, HC1, HC2, and HC3 using the HCC option in the MODEL statement: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_reg_syntax08.htm#statug.reg.modelhcc   Long and Ervin (2000) argue that HC3 is superior to HC0.   Additional methods such as HC4, HC4m, and HC5 have been proposed in the literature and implemented in the vcovHC function of R package sandwich.    Please consider adding these additional heteroscedasticity consistent estimators to PROC MIXED.   Relevant references:  Long J. S., Ervin L. H. (2000). “Using Heteroscedasticity Consistent Standard Errors in the Linear Regression Model.” The American Statistician, 54, 217–224. Cribari-Neto F. (2004). “Asymptotic Inference under Heteroskedasticity of Unknown Form.” Comuputational Statistics & Data Analysis 45, 215–233. Cribari-Neto F., Souza T.C., Vasconcellos, K.L.P. (2007). “Inference under Heteroskedasticity and Leveraged Data.” Communications in Statistics – Theory and Methods, 36, 1877–1888. Errata: 37, 3329–3330, 2008. Cribari-Neto F., Da Silva W.B. (2011). “A New Heteroskedasticity-Consistent Covariance Matrix Estimator for the Linear Regression Model.” Advances in Statistical Analysis, 95(2), 129–146. ... View more

I became a big fan od SAS Studio recently. But there is still one feature in SAS EG that is still winning me over, but I wish this would also be available is SAS Studio: Auto-completion for variable! While auto-completion for libraries, dataset and SAS sytnax in gerneral just works as fine in SAS Studio as in SAS EG, I don't understand why the auto-completion is not available for data fields/variables from a dataset (as it is in SAS EG)? ... View more