@frontlinesystems/rason-mcp-server 2026.5.1 → 2026.5.3

package/examples/datamining/TimeSeries/AddHoltWinters.json

@@ -1,80 +1,80 @@
-{
-  "modelName": "AddHoltWinters",
-  "modelDescription": "RASON Add Holt Winters Smoothing Example: This example generates a fitted model, POSTs the fitted model to the RASON server and also exports the fitted model in PMML and JSON format, then uses the fitted model to score the imported datasource and finally generates a forecast based on the fitted model. This example imports one outside data source, Airpass.txt which may be downloaded by clicking the RASON Examples Download icon (download cloud icon). To solve this model, you must first POST the model to the RASON Server by clicking the POST icon (upload cloud icon on the left). Afterwards click Choose Files (on the Properties pane on the right), browse to the location of the downloaded examples, and select Airpass.txt. Then click the down arrow next to the Play icon and click Solve. For more information on POSTing and solving example models, click Help - Defining Your Data Mining Model.",
-  "modelType": "datamining",
-  "datasources": {
-    "comment": "Defines datasources to use with this model, in the datasources section. Typically these bind to external data sources due to data volume.",
-    "myDataSrc": {
-      "comment": "Imports the outside data source, Airpass.txt, and binds the data to myDataSrc datasource. Note the direction property: import. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
-      "type": "csv",
-      "connection": "Airpass.txt",
-      "content": "time-series",
-      "direction": "import"
-    },
-    "myPMMLSrc": {
-      "comment": "This file (arima.xml) is currently setup to receive the exported fitted model in PMML format. (See the 'binding' property in the addHWModel action below.) Note the direction property, export, which specifies the information will be exported, rather than imported.",
-      "type": "xml",
-      "content": "pmml-model",
-      "connection": "arima.xml",
-      "direction": "export"
-    },
-    "jsonModelSrc": {
-      "comment": "Currently, this file is not being used. To export the fitted model in JSON format, rather than in PMML format, change the 'binding' property within the addHWModel action to 'binding':'jsonModelSrc'. After the model is solved, this file (arima.json) will contain the fitted model in JSON format. Note the direction property, export, which specifies the information will be exported, rather than imported.",
-      "type": "json",
-      "content": "json-model",
-      "connection": "arima.json",
-      "direction": "export"
-    }
-  },
-  "datasets": {
-    "comment": "Datasets are bound to an entry in the 'datasources' section",
-    "myData": {
-      "comment": "Binds myDataSrc (Airpass.txt) to myData data set.",
-      "binding": "myDataSrc"
-    }
-  },
-  "estimator": {
-    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator may appear in a RASON model.",
-    "addHWEstimator": {
-      "comment": "Defines the addHWEstimator as a Add Holt Winters smoothing time series estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
-      "type": "timeSeries",
-      "algorithm": "addHoltWinters",
-      "parameters": {
-        "period": 12,
-        "optimize": true
-      }
-    }
-  },
-  "actions": {
-    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
-    "addHWModel": {
-      "comment": "Fits addHWEstimator to myData (Airpass.txt). Generates and POSTS the fitted model to the RASON Server. Also exports the fitted model in PMML format to myPMMLSrc. To export the fitted model in JSON format, replace'binding':'myPMMLSrc' with 'binding':'jsonModelSrc'.",
-      "data": "myData",
-      "estimator": "addHWEstimator",
-      "action": "fit",
-      "binding": "myPMMLSrc",
-      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
-    },
-    "fitted": {
-      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Add Holt Winters model, addHWModel ('fittedModel':'addHWModel'). Various evaluations are requested in the results: transformation (which returns the Close price as predicted by addHWModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics'), such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
-      "data": "myData",
-      "fittedModel": "addHWModel",
-      "action": "transform",
-      "evaluations": [ "transformation", "residuals", "metrics" ]
-    },
-    "forecasted": {
-      "comment": "Uses the fitted model, addHWModel, to generate a forecast for the myData dataset. Note that various parameters are set to specify nonseasonal lag, seasonal lag, seasonality period, confidence level and the number of forecasts requested. In addition, the forecast and the difference are requested in the results. (The evaluation, difference, returns the differenced data in the Lag Analysis.) For a complete listing of all parameters and evaluations for Add Holt Winters smoothing, see the RASON Reference Guide.",
-      "data": "myData",
-      "fittedModel": "addHWModel",
-      "parameters": {
-        "numForecasts": 4,
-        "confidenceLevel": 0.9,
-        "nonSeasonalLag": 1,
-        "seasonalLag": 1,
-        "period": 12
-      },
-      "action": "forecast",
-      "evaluations": [ "forecast", "difference" ]
-    }
-  }
+{
+  "modelName": "AddHoltWinters",
+  "modelDescription": "RASON Add Holt Winters Smoothing Example: This example generates a fitted model, POSTs the fitted model to the RASON server and also exports the fitted model in PMML and JSON format, then uses the fitted model to score the imported datasource and finally generates a forecast based on the fitted model. This example imports one outside data source, Airpass.txt which may be downloaded by clicking the RASON Examples Download icon (download cloud icon). To solve this model, you must first POST the model to the RASON Server by clicking the POST icon (upload cloud icon on the left). Afterwards click Choose Files (on the Properties pane on the right), browse to the location of the downloaded examples, and select Airpass.txt. Then click the down arrow next to the Play icon and click Solve. For more information on POSTing and solving example models, click Help - Defining Your Data Mining Model.",
+  "modelType": "datamining",
+  "datasources": {
+    "comment": "Defines datasources to use with this model, in the datasources section. Typically these bind to external data sources due to data volume.",
+    "myDataSrc": {
+      "comment": "Imports the outside data source, Airpass.txt, and binds the data to myDataSrc datasource. Note the direction property: import. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
+      "type": "csv",
+      "connection": "Airpass.txt",
+      "content": "time-series",
+      "direction": "import"
+    },
+    "myPMMLSrc": {
+      "comment": "This file (arima.xml) is currently setup to receive the exported fitted model in PMML format. (See the 'binding' property in the addHWModel action below.) Note the direction property, export, which specifies the information will be exported, rather than imported.",
+      "type": "xml",
+      "content": "pmml-model",
+      "connection": "arima.xml",
+      "direction": "export"
+    },
+    "jsonModelSrc": {
+      "comment": "Currently, this file is not being used. To export the fitted model in JSON format, rather than in PMML format, change the 'binding' property within the addHWModel action to 'binding':'jsonModelSrc'. After the model is solved, this file (arima.json) will contain the fitted model in JSON format. Note the direction property, export, which specifies the information will be exported, rather than imported.",
+      "type": "json",
+      "content": "json-model",
+      "connection": "arima.json",
+      "direction": "export"
+    }
+  },
+  "datasets": {
+    "comment": "Datasets are bound to an entry in the 'datasources' section",
+    "myData": {
+      "comment": "Binds myDataSrc (Airpass.txt) to myData data set.",
+      "binding": "myDataSrc"
+    }
+  },
+  "estimator": {
+    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator may appear in a RASON model.",
+    "addHWEstimator": {
+      "comment": "Defines the addHWEstimator as a Add Holt Winters smoothing time series estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
+      "type": "timeSeries",
+      "algorithm": "addHoltWinters",
+      "parameters": {
+        "period": 12,
+        "optimize": true
+      }
+    }
+  },
+  "actions": {
+    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
+    "addHWModel": {
+      "comment": "Fits addHWEstimator to myData (Airpass.txt). Generates and POSTS the fitted model to the RASON Server. Also exports the fitted model in PMML format to myPMMLSrc. To export the fitted model in JSON format, replace'binding':'myPMMLSrc' with 'binding':'jsonModelSrc'.",
+      "data": "myData",
+      "estimator": "addHWEstimator",
+      "action": "fit",
+      "binding": "myPMMLSrc",
+      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
+    },
+    "fitted": {
+      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Add Holt Winters model, addHWModel ('fittedModel':'addHWModel'). Various evaluations are requested in the results: transformation (which returns the Close price as predicted by addHWModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics'), such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
+      "data": "myData",
+      "fittedModel": "addHWModel",
+      "action": "transform",
+      "evaluations": [ "transformation", "residuals", "metrics" ]
+    },
+    "forecasted": {
+      "comment": "Uses the fitted model, addHWModel, to generate a forecast for the myData dataset. Note that various parameters are set to specify nonseasonal lag, seasonal lag, seasonality period, confidence level and the number of forecasts requested. In addition, the forecast and the difference are requested in the results. (The evaluation, difference, returns the differenced data in the Lag Analysis.) For a complete listing of all parameters and evaluations for Add Holt Winters smoothing, see the RASON Reference Guide.",
+      "data": "myData",
+      "fittedModel": "addHWModel",
+      "parameters": {
+        "numForecasts": 4,
+        "confidenceLevel": 0.9,
+        "nonSeasonalLag": 1,
+        "seasonalLag": 1,
+        "period": 12
+      },
+      "action": "forecast",
+      "evaluations": [ "forecast", "difference" ]
+    }
+  }
 }

package/examples/datamining/TimeSeries/Arima.json

@@ -1,75 +1,75 @@
-{
-  "modelName": "Arima",
-  "modelDescription": "RASON Arima Example that POSTs fitted model (arimaModel) to the RASON Server. This fitted model is used in the the examples Scoring Using JSON ARIMA and Scoring Using PMML Arima. Both may be downloaded from Examples - Data Mining - Scoring. This model also imports a datasource, close.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select close.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
-  "modelType": "datamining",
-  "datasources": {
-    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
-    "myDataSrc": {
-      "comment": "Binds the close.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
-      "type": "csv",
-      "connection": "close.txt",
-      "content": "time-series",
-      "direction": "import"
-    }
-  },
-  "datasets": {
-    "comment": "Datasets are bound to an entry in the 'datasources' section",
-    "myData": {
-      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
-      "binding": "myDataSrc"
-    }
-  },
-  "estimator": {
-    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
-    "arimaEstimator": {
-      "comment": "Defines the arimaEstimator as an ARIMA estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
-      "type": "timeSeries",
-      "algorithm": "arima",
-      "parameters": {
-        "autoRegressiveOrder": 1,
-        "movingAverageOrder": 2,
-        "difference": 1,
-        "period": 12,
-        "seasonalAutoRegressiveOrder": 1,
-        "seasonalMovingAverageOrder": 1,
-        "seasonalDifference": 1,
-        "maxIterations": 5
-      }
-    }
-  },
-  "actions": {
-    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
-    "arimaModel": {
-      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using arimaEstimator ('estimator':'arimaEstimator'). The fitted model is POSTed to the RASON Server using export:json. Various evaluations are requested in the results such as the fitted model in JSON format, the coefficients, Lung-Box Test, variance covariance matrix, the Log Likelihood and the number of iterations. Note that results for fittedModelJson, logLikelihood and numIterations can only be viewed in the JSON results. To view, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported ARIMA parameters and evaluations.",
-      "data": "myData",
-      "estimator": "arimaEstimator",
-      "export": "json",
-      "action": "fit",
-      "evaluations": [ "fittedModelJson", "coefficientsInfo", "ljungBoxInfo", "varCovarMatrix", "logLikelihood", "numIterations" ]
-    },
-    "fitted": {
-      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted ARIMA model, arimaModel ('fittedModel':'arimaModel'). Various evaluations are requested in the results: transformation (which returns the Close price as predicted by arimaModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
-      "data": "myData",
-      "fittedModel": "arimaModel",
-      "action": "transform",
-      "evaluations": [ "transformation", "residuals", "metrics" ]
-    },
-    "forecasted": {
-      "comment": "Uses the fitted model ('fittedModel':'arimaModel') to generate a forecast (using 'action':'forecast') of 7 data points using a 95% confidence level. Various options are set such as minLag, maxLag, etc. Evaluations requested are: forecast (7 forecasted values), difference (returns the differenced data produced by Lag Analysis), autocovariance (returns the autocovariance function), autocorrelation(returns the autocorrelation function) and partialAutocorrelation(returns the partital autocorrelation function).",
-      "data": "myData",
-      "fittedModel": "arimaModel",
-      "parameters": {
-        "comment": "specify minLag, maxLag for ACF/PACF/ACVF evalautions and nonSeasonalLag, seasonalLag, period for difference",
-        "numForecasts": 7,
-        "confidenceLevel": 0.95,
-        "minLag": 4,
-        "maxLag": 10,
-        "nonSeasonalLag": 1,
-        "seasonalLag": 1,
-        "period": 12
-      },
-      "action": "forecast",
-      "evaluations": [ "forecast", "difference", "autocovariance", "autocorrelation", "partialAutocorrelation" ]
-    }
-  }
+{
+  "modelName": "Arima",
+  "modelDescription": "RASON Arima Example that POSTs fitted model (arimaModel) to the RASON Server. This fitted model is used in the the examples Scoring Using JSON ARIMA and Scoring Using PMML Arima. Both may be downloaded from Examples - Data Mining - Scoring. This model also imports a datasource, close.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select close.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
+  "modelType": "datamining",
+  "datasources": {
+    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
+    "myDataSrc": {
+      "comment": "Binds the close.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
+      "type": "csv",
+      "connection": "close.txt",
+      "content": "time-series",
+      "direction": "import"
+    }
+  },
+  "datasets": {
+    "comment": "Datasets are bound to an entry in the 'datasources' section",
+    "myData": {
+      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
+      "binding": "myDataSrc"
+    }
+  },
+  "estimator": {
+    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
+    "arimaEstimator": {
+      "comment": "Defines the arimaEstimator as an ARIMA estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
+      "type": "timeSeries",
+      "algorithm": "arima",
+      "parameters": {
+        "autoRegressiveOrder": 1,
+        "movingAverageOrder": 2,
+        "difference": 1,
+        "period": 12,
+        "seasonalAutoRegressiveOrder": 1,
+        "seasonalMovingAverageOrder": 1,
+        "seasonalDifference": 1,
+        "maxIterations": 5
+      }
+    }
+  },
+  "actions": {
+    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
+    "arimaModel": {
+      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using arimaEstimator ('estimator':'arimaEstimator'). The fitted model is POSTed to the RASON Server using export:json. Various evaluations are requested in the results such as the fitted model in JSON format, the coefficients, Lung-Box Test, variance covariance matrix, the Log Likelihood and the number of iterations. Note that results for fittedModelJson, logLikelihood and numIterations can only be viewed in the JSON results. To view, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported ARIMA parameters and evaluations.",
+      "data": "myData",
+      "estimator": "arimaEstimator",
+      "export": "json",
+      "action": "fit",
+      "evaluations": [ "fittedModelJson", "coefficientsInfo", "ljungBoxInfo", "varCovarMatrix", "logLikelihood", "numIterations" ]
+    },
+    "fitted": {
+      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted ARIMA model, arimaModel ('fittedModel':'arimaModel'). Various evaluations are requested in the results: transformation (which returns the Close price as predicted by arimaModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
+      "data": "myData",
+      "fittedModel": "arimaModel",
+      "action": "transform",
+      "evaluations": [ "transformation", "residuals", "metrics" ]
+    },
+    "forecasted": {
+      "comment": "Uses the fitted model ('fittedModel':'arimaModel') to generate a forecast (using 'action':'forecast') of 7 data points using a 95% confidence level. Various options are set such as minLag, maxLag, etc. Evaluations requested are: forecast (7 forecasted values), difference (returns the differenced data produced by Lag Analysis), autocovariance (returns the autocovariance function), autocorrelation(returns the autocorrelation function) and partialAutocorrelation(returns the partital autocorrelation function).",
+      "data": "myData",
+      "fittedModel": "arimaModel",
+      "parameters": {
+        "comment": "specify minLag, maxLag for ACF/PACF/ACVF evalautions and nonSeasonalLag, seasonalLag, period for difference",
+        "numForecasts": 7,
+        "confidenceLevel": 0.95,
+        "minLag": 4,
+        "maxLag": 10,
+        "nonSeasonalLag": 1,
+        "seasonalLag": 1,
+        "period": 12
+      },
+      "action": "forecast",
+      "evaluations": [ "forecast", "difference", "autocovariance", "autocorrelation", "partialAutocorrelation" ]
+    }
+  }
 }

package/examples/datamining/TimeSeries/DoubleExponential.json

@@ -1,66 +1,66 @@
-{
-  "modelName": "DoubleExponential",
-  "modelDescription": "RASON Double Exponential Smoothing Example that fits a model to a dataset. This model also imports a datasource, airpass.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select airpass.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
-  "modelType": "datamining",
-  "datasources": {
-    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
-    "myDataSrc": {
-      "comment": "Binds the airpass.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
-      "type": "csv",
-      "connection": "Airpass.txt",
-      "content": "time-series",
-      "direction": "import"
-    }
-  },
-  "datasets": {
-    "comment": "Datasets are bound to an entry in the datasources section",
-    "myData": {
-      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
-      "binding": "myDataSrc"
-    }
-  },
-  "estimator": {
-    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
-    "doubleExpoEstimator": {
-      "comment": "Defines the doubleExpoEstimator as a double exponential smoothing estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
-      "type": "timeSeries",
-      "algorithm": "doubleExponential",
-      "parameters": {
-        "optimize": true
-      }
-    }
-  },
-  "actions": {
-    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
-    "doubleExpoModel": {
-      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using doubleExpoEstimator ('estimator':'doubleExpoEstimator'). Various evaluations are requested in the results such as the fitted model in JSON format and the coefficients. To view the fitted model, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported Exponential Smoothing parameters and evaluations.",
-      "data": "myData",
-      "estimator": "doubleExpoEstimator",
-      "action": "fit",
-      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
-    },
-    "fitted": {
-      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Double Exponential Smoothing model, doubleExpoModel ('fittedModel':'doubleExpoModel'). Various evaluations are requested in the results: transformation (which returns the # of passengers as predicted by doubleExpoModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
-
-      "data": "myData",
-      "fittedModel": "doubleExpoModel",
-      "action": "transform",
-      "evaluations": [ "transformation", "residuals", "metrics" ]
-    },
-    "forecasted": {
-      "comment": "Uses the fitted model ('fittedModel':'doubleExpoModel') to generate a forecast (using 'action':'forecast') of 4 data points using a 90% confidence level. Various options are set such as nonseasonal lag, seasonal lag and period. Evaluations requested are: forecast (4 forecasted values) and difference (returns the differenced data produced by Lag Analysis).",
-      "data": "myData",
-      "fittedModel": "doubleExpoModel",
-      "parameters": {
-        "comment": "specify nonSeasonalLag, seasonalLag, period for difference",
-        "numForecasts": 4,
-        "confidenceLevel": 0.9,
-        "nonSeasonalLag": 1,
-        "seasonalLag": 1,
-        "period": 12
-      },
-      "action": "forecast",
-      "evaluations": [ "forecast", "difference" ]
-    }
-  }
+{
+  "modelName": "DoubleExponential",
+  "modelDescription": "RASON Double Exponential Smoothing Example that fits a model to a dataset. This model also imports a datasource, airpass.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select airpass.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
+  "modelType": "datamining",
+  "datasources": {
+    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
+    "myDataSrc": {
+      "comment": "Binds the airpass.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
+      "type": "csv",
+      "connection": "Airpass.txt",
+      "content": "time-series",
+      "direction": "import"
+    }
+  },
+  "datasets": {
+    "comment": "Datasets are bound to an entry in the datasources section",
+    "myData": {
+      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
+      "binding": "myDataSrc"
+    }
+  },
+  "estimator": {
+    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
+    "doubleExpoEstimator": {
+      "comment": "Defines the doubleExpoEstimator as a double exponential smoothing estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
+      "type": "timeSeries",
+      "algorithm": "doubleExponential",
+      "parameters": {
+        "optimize": true
+      }
+    }
+  },
+  "actions": {
+    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
+    "doubleExpoModel": {
+      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using doubleExpoEstimator ('estimator':'doubleExpoEstimator'). Various evaluations are requested in the results such as the fitted model in JSON format and the coefficients. To view the fitted model, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported Exponential Smoothing parameters and evaluations.",
+      "data": "myData",
+      "estimator": "doubleExpoEstimator",
+      "action": "fit",
+      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
+    },
+    "fitted": {
+      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Double Exponential Smoothing model, doubleExpoModel ('fittedModel':'doubleExpoModel'). Various evaluations are requested in the results: transformation (which returns the # of passengers as predicted by doubleExpoModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
+
+      "data": "myData",
+      "fittedModel": "doubleExpoModel",
+      "action": "transform",
+      "evaluations": [ "transformation", "residuals", "metrics" ]
+    },
+    "forecasted": {
+      "comment": "Uses the fitted model ('fittedModel':'doubleExpoModel') to generate a forecast (using 'action':'forecast') of 4 data points using a 90% confidence level. Various options are set such as nonseasonal lag, seasonal lag and period. Evaluations requested are: forecast (4 forecasted values) and difference (returns the differenced data produced by Lag Analysis).",
+      "data": "myData",
+      "fittedModel": "doubleExpoModel",
+      "parameters": {
+        "comment": "specify nonSeasonalLag, seasonalLag, period for difference",
+        "numForecasts": 4,
+        "confidenceLevel": 0.9,
+        "nonSeasonalLag": 1,
+        "seasonalLag": 1,
+        "period": 12
+      },
+      "action": "forecast",
+      "evaluations": [ "forecast", "difference" ]
+    }
+  }
 }

package/examples/datamining/TimeSeries/Exponential.json

@@ -1,65 +1,65 @@
-{
-  "modelName": "Exponential",
-  "modelDescription": "RASON Exponential Smoothing Example that fits a model to a dataset. This model also imports a datasource, airpass.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select airpass.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
-  "modelType": "datamining",
-  "datasources": {
-    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
-    "myDataSrc": {
-      "comment": "Binds the airpass.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
-      "type": "csv",
-      "connection": "Airpass.txt",
-      "content": "time-series",
-      "direction": "import"
-    }
-  },
-  "datasets": {
-    "comment": "Datasets are bound to an entry in the datasources section",
-    "myData": {
-      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
-      "binding": "myDataSrc"
-    }
-  },
-  "estimator": {
-    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
-    "expoEstimator": {
-      "comment": "Defines the expoEstimator as an exponential smoothing estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
-      "type": "timeSeries",
-      "algorithm": "exponential",
-      "parameters": {
-        "optimize": true
-      }
-    }
-  },
-  "actions": {
-    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
-    "expoModel": {
-      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using expoEstimator ('estimator':'expoEstimator'). Various evaluations are requested in the results such as the fitted model in JSON format and the coefficients. To view the fitted model, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported Exponential Smoothing parameters and evaluations.",
-      "data": "myData",
-      "estimator": "expoEstimator",
-      "action": "fit",
-      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
-    },
-    "fitted": {
-      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Exponential Smoothing model, expoModel ('fittedModel':'expoModel'). Various evaluations are requested in the results: transformation (which returns the # of passengers as predicted by doubleExpoModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
-      "data": "myData",
-      "fittedModel": "expoModel",
-      "action": "transform",
-      "evaluations": [ "transformation", "residuals", "metrics" ]
-    },
-    "forecasted": {
-      "comment": "Uses the fitted model ('fittedModel':'expoModel') to generate a forecast (using 'action':'forecast') of 4 data points using a 90% confidence level. Various options are set such as nonseasonal lag, seasonal lag and period. Evaluations requested are: forecast (4 forecasted values) and difference (returns the differenced data produced by Lag Analysis).",
-      "data": "myData",
-      "fittedModel": "expoModel",
-      "parameters": {
-        "comment": "specify evalautions and nonSeasonalLag, seasonalLag, period for difference",
-        "numForecasts": 4,
-        "confidenceLevel": 0.9,
-        "nonSeasonalLag": 1,
-        "seasonalLag": 1,
-        "period": 12
-      },
-      "action": "forecast",
-      "evaluations": [ "forecast", "difference" ]
-    }
-  }
+{
+  "modelName": "Exponential",
+  "modelDescription": "RASON Exponential Smoothing Example that fits a model to a dataset. This model also imports a datasource, airpass.txt, which can be downloaded by clicking the Download RASON Example Files icon (download icon) on the ribbon. To attach the source file to the example, click Choose Files (on the Properties tab on the right), navigate to the location of the downloaded files, select airpass.txt and click Open. Then click the POST icon (upload icon) to POST the model to the RASON Server, then click the down arrow next to the Play icon and select Solve to solve the model.",
+  "modelType": "datamining",
+  "datasources": {
+    "comment": "Define datasources to use with this model. Typically these bind to external data sources due to data volume.",
+    "myDataSrc": {
+      "comment": "Binds the airpass.txt source file to the myDataSrc datasource. The property content:time-series considers the 1st column as the time variable and the 2nd column as the value column in the dataframe.",
+      "type": "csv",
+      "connection": "Airpass.txt",
+      "content": "time-series",
+      "direction": "import"
+    }
+  },
+  "datasets": {
+    "comment": "Datasets are bound to an entry in the datasources section",
+    "myData": {
+      "comment": "Binds myDataSrc data source (close.txt) to myData dataset",
+      "binding": "myDataSrc"
+    }
+  },
+  "estimator": {
+    "comment": "Defines an estimator, including the type, algorithm and parameters. Only 1 estimator/transformer may appear in a RASON model.",
+    "expoEstimator": {
+      "comment": "Defines the expoEstimator as an exponential smoothing estimator; various options are set. For a complete list of all algorithm options, see the RASON Data Mining Components chapter in the RASON Reference Guide. (Click the Help tab to download.)",
+      "type": "timeSeries",
+      "algorithm": "exponential",
+      "parameters": {
+        "optimize": true
+      }
+    }
+  },
+  "actions": {
+    "comment": "Define actions, evaluations, and data to be used by the estimator created above.",
+    "expoModel": {
+      "comment": "Fits (using 'action':'fit') a model to the myData dataset ('data':'myData') using expoEstimator ('estimator':'expoEstimator'). Various evaluations are requested in the results such as the fitted model in JSON format and the coefficients. To view the fitted model, click Show Json Results in the upper right corner of the OData viewer. See the RASON Reference Guide (click the Help tab to download) for a list of all supported Exponential Smoothing parameters and evaluations.",
+      "data": "myData",
+      "estimator": "expoEstimator",
+      "action": "fit",
+      "evaluations": [ "fittedModelJson", "coefficientsInfo" ]
+    },
+    "fitted": {
+      "comment": "Scores (using 'action':'transform') the myData dataset ('data':'myData') using the fitted Exponential Smoothing model, expoModel ('fittedModel':'expoModel'). Various evaluations are requested in the results: transformation (which returns the # of passengers as predicted by doubleExpoModel), residuals (difference between the actual and predicted values), and several statistics (using 'metrics') such as SSE (sum of squared error), MSE (mean squared error), MAPE (mean absolute percentage error), MAD (mean absolute deviation), etc. See the JSON results for the statistic values.",
+      "data": "myData",
+      "fittedModel": "expoModel",
+      "action": "transform",
+      "evaluations": [ "transformation", "residuals", "metrics" ]
+    },
+    "forecasted": {
+      "comment": "Uses the fitted model ('fittedModel':'expoModel') to generate a forecast (using 'action':'forecast') of 4 data points using a 90% confidence level. Various options are set such as nonseasonal lag, seasonal lag and period. Evaluations requested are: forecast (4 forecasted values) and difference (returns the differenced data produced by Lag Analysis).",
+      "data": "myData",
+      "fittedModel": "expoModel",
+      "parameters": {
+        "comment": "specify evalautions and nonSeasonalLag, seasonalLag, period for difference",
+        "numForecasts": 4,
+        "confidenceLevel": 0.9,
+        "nonSeasonalLag": 1,
+        "seasonalLag": 1,
+        "period": 12
+      },
+      "action": "forecast",
+      "evaluations": [ "forecast", "difference" ]
+    }
+  }
 }