Samples & SAS Notes > Analytics
>
Forecasting
| Date | Title | Type | ||
|---|---|---|---|---|
| 11/19/09 |
37817 - Filter reapplied after editing the original filter condition is not updated. If a filter has been has been added, saved and applied in a Forecast Studio project, and the results returned by the filter are resorted in a manner other than the default sort order returned by the filter, then any ... http://support.sas.com/kb/37/817.html, 18KB |
Problem Note | ||
| 10/20/09 |
37474 - Incorrect forecasts are produced when future values of exogenous variables are not provided If a model with exogenous (input) variables is estimated in PROC VARMAX and out-of-sample forecasts of the response variables are desired, then future values of the input variables must be provided. PROC VARMAX first ... http://support.sas.com/kb/37/474.html, 19KB |
Problem Note | ||
| 9/16/09 |
37105 - Why does the program editor window banner say "PROC .. running" after the procedure has finished? The ANOVA, ARIMA, CATMOD, FACTEX, GLM, MODEL, OPTEX, PLAN, and REG procedures are interactive procedures. They remain active after processing a RUN statement. The "running" message in the banner of the ... http://support.sas.com/kb/37/105.html, 30KB |
Usage Note | ||
| 9/16/09 |
37181 - Warning: Output was not created -and- The current ODS SELECT/EXCLUDE/OUTPUT statement was cleared See this usage note on why the following messages occur and how to avoid them. WARNING: Output 'parameterestimates' was not created. Make sure that the output object name, label, or path is spelled correctly. ... http://support.sas.com/kb/37/181.html, 27KB |
Usage Note | ||
| 9/16/09 |
37171 - Why do I get a message that I cannot open an output data set because it is in use by me? When using an interactive procedure to create a data set, the following message may occur when trying to display the data set, such as with the Table Editor (viewtable, or vt, command). This usage note describes why ... http://support.sas.com/kb/37/171.html, 26KB |
Usage Note | ||
| 9/3/09 |
36501 - Detection of project ownership fails The internal value used to detect project ownership is stored incorrectly in the project XML file. Consequently, any action that causes the metadata to be re-created from the XML data, such as unarchiving and save as, ... http://support.sas.com/kb/36/501.html, 19KB |
Problem Note | ||
| 8/31/09 |
36250 - Read Access Violation in Task [ARIMA] may occur when PLOTS= option is specified A Read Access Violation in Task [ARIMA] may occur when the PLOTS= option is used and the FORECAST statement is specified. http://support.sas.com/kb/36/250.html, 20KB |
Problem Note | ||
| 8/21/09 |
36453 - How to import and assess outside modeling techniques using SASŪ Enterprise Miner(tm) This video shows an example of how to import a non-supplied model into SAS Enterprise Miner and be able to assess it with other models. http://support.sas.com/kb/36/453.html, 21KB |
Usage Note | ||
| 8/3/09 |
36690 - RESTRICT statement may produce incorrect results if TREND= option is specified on MODEL statement If the TREND= option is specified on the MODEL statement and the RESTRICT statement is used to impose restrictions on the parameters associated with the exogenous variables, then the restrictions are applied to the ... http://support.sas.com/kb/36/690.html, 20KB |
Problem Note | ||
| 6/24/09 |
36192 - Model continues to forecast HPFARIMASPEC model after it returns a Hessian Warning Models created using HPFARIMASPEC, containing an INPUT statement, may result in a Hessian warning when the model is fit in HPFENGINE. This warning does not stop the models from being evaluated for their fit criterion ... http://support.sas.com/kb/36/192.html, 19KB |
Problem Note | ||
