@frontlinesystems/rason-mcp-server 2026.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (195) hide show
  1. package/LICENSE +35 -0
  2. package/README.md +282 -0
  3. package/examples/EXAMPLES_REFERENCE.md +128 -0
  4. package/examples/Optimization/Conic/AirlineHubConic.json +112 -0
  5. package/examples/Optimization/Conic/AirlineHubConic2.json +109 -0
  6. package/examples/Optimization/Conic/AirlineHubConic3.json +112 -0
  7. package/examples/Optimization/Conic/AirlineHubConic4.json +100 -0
  8. package/examples/Optimization/Conic/AirlineHubConic5.json +102 -0
  9. package/examples/Optimization/DataBinding/ProductMixCsv.json +82 -0
  10. package/examples/Optimization/DataBinding/ProductMixCsv4.json +96 -0
  11. package/examples/Optimization/DataBinding/ProductMixExcel.json +74 -0
  12. package/examples/Optimization/DataBinding/ProductMixExcel1.json +87 -0
  13. package/examples/Optimization/DataBinding/ProductMixExcel11.json +109 -0
  14. package/examples/Optimization/DataBinding/ProductMixExcel2.json +78 -0
  15. package/examples/Optimization/DataBinding/ProductMixTab.json +90 -0
  16. package/examples/Optimization/DataBinding/ProductMixTab1.json +74 -0
  17. package/examples/Optimization/DataBinding/ProductMixTab2.json +78 -0
  18. package/examples/Optimization/Linear/Inventory.json +200 -0
  19. package/examples/Optimization/Linear/Matop.json +120 -0
  20. package/examples/Optimization/Linear/ProductMix.json +98 -0
  21. package/examples/Optimization/Linear/ProductMix2.json +73 -0
  22. package/examples/Optimization/Linear/ProductMix3.json +50 -0
  23. package/examples/Optimization/Linear/ProductMix4.json +57 -0
  24. package/examples/Optimization/Linear/ProductMixCsv1.json +106 -0
  25. package/examples/Optimization/Linear/ProductMixCsv2.json +106 -0
  26. package/examples/Optimization/Linear/ProductMixSQL11.json +82 -0
  27. package/examples/Optimization/Linear/Rowop.json +127 -0
  28. package/examples/Optimization/NonLinear/AirlineHub.json +64 -0
  29. package/examples/Optimization/NonLinear/AirlineHub2.json +48 -0
  30. package/examples/Optimization/NonLinear/AirlineHub3.json +48 -0
  31. package/examples/Optimization/NonSmooth/Inventory2.json +160 -0
  32. package/examples/Optimization/Quadratic/PortfolioOpt.json +56 -0
  33. package/examples/Optimization/Quadratic/PortfolioOpt2.json +66 -0
  34. package/examples/Optimization/WithUncertainty/GasCompanyChance.json +79 -0
  35. package/examples/Optimization/WithUncertainty/GasCompanyRecourse.json +79 -0
  36. package/examples/Optimization/WithUncertainty/ProjectSelect.json +78 -0
  37. package/examples/Optimization/WithUncertainty/ProjectSelect2.json +82 -0
  38. package/examples/Optimization/WithUncertainty/ProjectSelect3.json +85 -0
  39. package/examples/Optimization/WithUncertainty/ProjectSelect4.json +75 -0
  40. package/examples/Simulation/CandyStoreSalesUsingSIP.json +148 -0
  41. package/examples/Simulation/CollegeFundGrowth1.json +424 -0
  42. package/examples/Simulation/CollegeFundGrowth1SIPModel.json +28 -0
  43. package/examples/Simulation/CollegeFundGrowth2.json +416 -0
  44. package/examples/Simulation/CollegeFundGrowthSIP.json +402 -0
  45. package/examples/Simulation/GBMSimulationModel.json +237 -0
  46. package/examples/Simulation/YieldManagement(Sim).json +70 -0
  47. package/examples/Simulation/YieldManagement2(Sim).json +73 -0
  48. package/examples/calculation/DMNExamples/DMN Box Fun with typeDef result.json +54 -0
  49. package/examples/calculation/DMNExamples/DMN Context example.json +69 -0
  50. package/examples/calculation/DMNExamples/DMN DT with typeDef result.json +43 -0
  51. package/examples/calculation/DMNExamples/FEEL Date Time example.json +28 -0
  52. package/examples/calculation/DMNExamples/FEEL For iteration example.json +66 -0
  53. package/examples/calculation/DMNExamples/FEEL For with two indices.json +16 -0
  54. package/examples/calculation/DMNExamples/FEEL For with typeDef result.json +88 -0
  55. package/examples/calculation/DMNExamples/FEEL If Then Else example.json +26 -0
  56. package/examples/calculation/DMNExamples/FEEL List example.json +38 -0
  57. package/examples/calculation/DMNExamples/FEEL List operator.json +17 -0
  58. package/examples/calculation/DMNExamples/FEEL List with typeDef collection.json +37 -0
  59. package/examples/calculation/DMNExamples/FEEL Some or Every example.json +66 -0
  60. package/examples/calculation/DecisionTables/DT Datasource example.json +53 -0
  61. package/examples/calculation/DecisionTables/DT Date and Time examples.json +92 -0
  62. package/examples/calculation/DecisionTables/DT Expression example.json +32 -0
  63. package/examples/calculation/DecisionTables/DT Hit Policy examples.json +137 -0
  64. package/examples/calculation/DecisionTables/DT Loan Recommend model.json +82 -0
  65. package/examples/calculation/DecisionTables/DT Loan Strategy Model and Predictive CSV-XML.json +219 -0
  66. package/examples/calculation/DecisionTables/DT Loan Strategy model and Datasource.json +286 -0
  67. package/examples/calculation/DecisionTables/DT Loan Strategy model and Predictive.json +204 -0
  68. package/examples/calculation/DecisionTables/DT Loan Strategy model by scratch.json +214 -0
  69. package/examples/calculation/DecisionTables/DT Output Order example.json +40 -0
  70. package/examples/calculation/DecisionTables/DT Unique example.json +39 -0
  71. package/examples/calculation/TypeDefinitions/TypeDefCF.json +65 -0
  72. package/examples/calculation/TypeDefinitions/TypeDefDT.json +58 -0
  73. package/examples/datamining/AffinityAnalysis/AssociationRules.json +52 -0
  74. package/examples/datamining/Classification/DecisionTree.json +91 -0
  75. package/examples/datamining/Classification/DiscriminantAnalysis.json +82 -0
  76. package/examples/datamining/Classification/Ensembles/Bagging.json +67 -0
  77. package/examples/datamining/Classification/Ensembles/Boosting.json +68 -0
  78. package/examples/datamining/Classification/Ensembles/RandomTrees.json +92 -0
  79. package/examples/datamining/Classification/FindBestModel.json +87 -0
  80. package/examples/datamining/Classification/LogisticRegression.json +83 -0
  81. package/examples/datamining/Classification/NaiveBayes.json +79 -0
  82. package/examples/datamining/Classification/NearestNeighbors.json +85 -0
  83. package/examples/datamining/Classification/NeuralNetwork.json +93 -0
  84. package/examples/datamining/Clustering/Hierarchical.json +55 -0
  85. package/examples/datamining/Clustering/KMeans.json +72 -0
  86. package/examples/datamining/DataSources/DelimitedFile.json +50 -0
  87. package/examples/datamining/DataSources/JSONFile.json +50 -0
  88. package/examples/datamining/DataSources/MSAccessDatabase.json +50 -0
  89. package/examples/datamining/DataSources/MSExcelTable.json +51 -0
  90. package/examples/datamining/DataSources/MSSQLDatabase.json +50 -0
  91. package/examples/datamining/DataSources/ODATATable.json +50 -0
  92. package/examples/datamining/DataSources/ODBCDatabase.json +50 -0
  93. package/examples/datamining/FeatureSelection/LinearWrapping.json +54 -0
  94. package/examples/datamining/FeatureSelection/LogisticWrapping.json +57 -0
  95. package/examples/datamining/FeatureSelection/Univariate.json +79 -0
  96. package/examples/datamining/Regression/DecisionTree.json +82 -0
  97. package/examples/datamining/Regression/Ensembles/Bagging.json +63 -0
  98. package/examples/datamining/Regression/Ensembles/Boosting.json +63 -0
  99. package/examples/datamining/Regression/Ensembles/RandomTrees.json +79 -0
  100. package/examples/datamining/Regression/FindBestModel.json +87 -0
  101. package/examples/datamining/Regression/LinearRegression.json +125 -0
  102. package/examples/datamining/Regression/NearestNeighbors.json +78 -0
  103. package/examples/datamining/Regression/NeuralNetwork.json +83 -0
  104. package/examples/datamining/Scoring/JSONClassifier.json +63 -0
  105. package/examples/datamining/Scoring/JSONClassifierNN.json +63 -0
  106. package/examples/datamining/Scoring/JSONClusterizer.json +38 -0
  107. package/examples/datamining/Scoring/JSONForecaster.json +50 -0
  108. package/examples/datamining/Scoring/JSONLinearRegression.json +57 -0
  109. package/examples/datamining/Scoring/JSONPCA.json +42 -0
  110. package/examples/datamining/Scoring/JSONRegressor.json +57 -0
  111. package/examples/datamining/Scoring/JSONTransformer.json +39 -0
  112. package/examples/datamining/Scoring/PMMLClassifier.json +43 -0
  113. package/examples/datamining/Scoring/PMMLForecaster.json +44 -0
  114. package/examples/datamining/Scoring/PMMLRegressor.json +39 -0
  115. package/examples/datamining/Scoring/PMMLTransformer.json +39 -0
  116. package/examples/datamining/Simulation/LinearRegressionSimulation.json +118 -0
  117. package/examples/datamining/Simulation/SyntheticDataGeneration.json +109 -0
  118. package/examples/datamining/Simulation/pmml-risk-scoring.json +63 -0
  119. package/examples/datamining/Summarizer/Summarization.json +55 -0
  120. package/examples/datamining/TextMining/LatentSemanticAnalysis.json +52 -0
  121. package/examples/datamining/TextMining/TfIdf-FileData.json +66 -0
  122. package/examples/datamining/TextMining/TfIdf-InlineData.json +56 -0
  123. package/examples/datamining/TimeSeries/AddHoltWinters.json +80 -0
  124. package/examples/datamining/TimeSeries/Arima.json +75 -0
  125. package/examples/datamining/TimeSeries/DoubleExponential.json +66 -0
  126. package/examples/datamining/TimeSeries/Exponential.json +65 -0
  127. package/examples/datamining/TimeSeries/LagAnalysis.json +49 -0
  128. package/examples/datamining/TimeSeries/MovingAverage.json +66 -0
  129. package/examples/datamining/TimeSeries/MulHoltWinters.json +66 -0
  130. package/examples/datamining/TimeSeries/NoTrendHoltWinters.json +66 -0
  131. package/examples/datamining/Transformation/Binning.json +70 -0
  132. package/examples/datamining/Transformation/CanonicalVariateAnalysis.json +48 -0
  133. package/examples/datamining/Transformation/CategoryReduction.json +52 -0
  134. package/examples/datamining/Transformation/Factorization.json +51 -0
  135. package/examples/datamining/Transformation/MissingDataHandling.json +84 -0
  136. package/examples/datamining/Transformation/OneHotEncoding-DataInline.json +55 -0
  137. package/examples/datamining/Transformation/OneHotEncoding-DatainFile.json +49 -0
  138. package/examples/datamining/Transformation/PartitionTimeSeries.json +49 -0
  139. package/examples/datamining/Transformation/Partitioning-DF.json +73 -0
  140. package/examples/datamining/Transformation/Partitioning.json +47 -0
  141. package/examples/datamining/Transformation/PartitioningWithOversampling-DF.json +66 -0
  142. package/examples/datamining/Transformation/PartitioningWithOversampling.json +45 -0
  143. package/examples/datamining/Transformation/PrincipalComponentsAnalysis.json +53 -0
  144. package/examples/datamining/Transformation/Rescaling.json +68 -0
  145. package/examples/datamining/Transformation/Sampling.json +44 -0
  146. package/examples/datamining/Transformation/StratifiedSampling.json +47 -0
  147. package/examples/flow/SQLServerTransform.json +261 -0
  148. package/examples/flow/dm-calc-pipeline.json +278 -0
  149. package/examples/flow/dm-pipeline-simulation.json +114 -0
  150. package/examples/flow/opt-sim-pipeline.json +160 -0
  151. package/examples/flow/sim-dm-pipeline.json +107 -0
  152. package/examples/flow/sim-sim-pipeline.json +137 -0
  153. package/examples/index.json +4679 -0
  154. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/DataFiltering/ListwithFilter.json +53 -0
  155. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/ProductMix5.json +58 -0
  156. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/compoundWhileStatement.json +36 -0
  157. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/ifThenElseStatement.json +34 -0
  158. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/nestedLoop.json +26 -0
  159. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/ParallelArray.json +48 -0
  160. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/indexedArray.json +70 -0
  161. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/nonParallelArray.json +50 -0
  162. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/sumAggregateExample.json +338 -0
  163. package/examples/rason-features/Arrays_Loops_Tables/ArrayExamples/tsp.json +62 -0
  164. package/examples/rason-features/BoxIterators/Box_Fun_Loop_Iter_Sim_RASON.json +191 -0
  165. package/examples/rason-features/BoxIterators/Box_Fun_Loop_Sim_RASON.json +76 -0
  166. package/examples/rason-features/BoxIterators/Box_Fun_Sim_RASON.json +109 -0
  167. package/examples/rason-features/BoxIterators/Box_Iter_SIM_RASON.json +69 -0
  168. package/examples/rason-features/BoxIterators/Box_Iterator_Calc_Loop.json +183 -0
  169. package/examples/rason-features/BoxIterators/Box_Iterator_with_typeDef_partial.json +79 -0
  170. package/examples/rason-features/BoxLambdaExamples/BoxFunOptimize.json +155 -0
  171. package/examples/rason-features/BoxLambdaExamples/BoxFunSimulate.json +119 -0
  172. package/examples/rason-features/BoxLambdaExamples/LambdaFunOptimize.json +143 -0
  173. package/examples/rason-features/BoxLambdaExamples/LambdaFunSimulate.json +82 -0
  174. package/examples/rason-features/ReferenceGuide/RGFirehouseLocation.json +69 -0
  175. package/examples/rason-features/ReferenceGuide/RGFirehouseLocationConic.json +114 -0
  176. package/examples/rason-features/ReferenceGuide/RGProductMixCsv1.json +108 -0
  177. package/examples/rason-features/ReferenceGuide/RGProductMixExcel11.json +117 -0
  178. package/examples/rason-features/ReferenceGuide/RGProductMixSQL11.json +108 -0
  179. package/examples/rason-features/UserGuide/UGAirlineHubCSV.json +67 -0
  180. package/examples/rason-features/UserGuide/UGForecast.json +51 -0
  181. package/examples/rason-features/UserGuide/UGProductMix1.json +49 -0
  182. package/examples/rason-features/UserGuide/UGProductMix2.json +49 -0
  183. package/examples/rason-features/UserGuide/UGProductMixTab1.json +68 -0
  184. package/examples/rason-features/UserGuide/UGProductMixTab2.json +77 -0
  185. package/examples/rason-features/UserGuide/UGProductMixTab3.json +67 -0
  186. package/examples/rason-features/UserGuide/UGProductMixTab4.json +71 -0
  187. package/examples/rason-features/UserGuide/UGProductMixTab5.json +68 -0
  188. package/examples/rason-features/UserGuide/UGProjectSelect0.json +92 -0
  189. package/examples/rason-features/UserGuide/UGProjectSelect1.json +75 -0
  190. package/examples/rason-features/UserGuide/UGProjectSelect2.json +75 -0
  191. package/examples/rason-features/UserGuide/UGYieldManagement1.json +62 -0
  192. package/examples/rason-features/UserGuide/UGYieldManagement2.json +62 -0
  193. package/examples/rason-features/UserGuide/UGYieldManagement3.json +64 -0
  194. package/out/index.cjs +361 -0
  195. package/package.json +76 -0
@@ -0,0 +1,4679 @@
1
+ [
2
+ {
3
+ "filePath": "calculation/DMNExamples/DMN Box Fun with typeDef result.json",
4
+ "modelName": "BKMinFEEL",
5
+ "description": "BKM in FEEL",
6
+ "modelType": "calculation",
7
+ "subcategory": null,
8
+ "features": [
9
+ "formulas",
10
+ "data",
11
+ "box-functions"
12
+ ],
13
+ "tags": [
14
+ "box-function",
15
+ "calculation"
16
+ ]
17
+ },
18
+ {
19
+ "filePath": "calculation/TypeDefinitions/TypeDefCF.json",
20
+ "modelName": "BoxFunTypeDefAllowedValues",
21
+ "description": "RASON Example of Box function in FEEL with allowed values for box function inputs and input types passed as a JSON object. This example computes a loan payment based on customer input such as the loan principal amount, interest rate and the term in months.",
22
+ "modelType": "calculation",
23
+ "subcategory": null,
24
+ "features": [
25
+ "formulas",
26
+ "data",
27
+ "box-functions"
28
+ ],
29
+ "tags": [
30
+ "box-function",
31
+ "calculation"
32
+ ]
33
+ },
34
+ {
35
+ "filePath": "rason-features/BoxIterators/Box_Iterator_with_typeDef_partial.json",
36
+ "modelName": "BoxIter_FEELwithTypeDef",
37
+ "description": "Example of box iterator using FEEL language",
38
+ "modelType": "calculation",
39
+ "subcategory": null,
40
+ "features": [
41
+ "formulas",
42
+ "data",
43
+ "box-functions",
44
+ "box-iterators"
45
+ ],
46
+ "isFeatureDemo": true,
47
+ "tags": [
48
+ "box-function",
49
+ "box-iterator",
50
+ "calculation"
51
+ ]
52
+ },
53
+ {
54
+ "filePath": "rason-features/BoxIterators/Box_Iterator_Calc_Loop.json",
55
+ "modelName": "Calc_Box_Fcn_and_Box_Iters",
56
+ "description": "This example includes 1 box function and 4 box iterators. Each one calculates the monthly payments of 3 loans.",
57
+ "modelType": "calculation",
58
+ "subcategory": null,
59
+ "features": [
60
+ "formulas",
61
+ "data",
62
+ "box-functions",
63
+ "box-iterators"
64
+ ],
65
+ "isFeatureDemo": true,
66
+ "tags": [
67
+ "box-function",
68
+ "box-iterator",
69
+ "calculation"
70
+ ]
71
+ },
72
+ {
73
+ "filePath": "simulation/CollegeFundGrowth1SIPModel.json",
74
+ "modelName": "CollegeFundGrowth1",
75
+ "description": "",
76
+ "modelType": "calculation",
77
+ "subcategory": null,
78
+ "features": [],
79
+ "tags": [
80
+ "calculation"
81
+ ]
82
+ },
83
+ {
84
+ "filePath": "calculation/DMNExamples/DMN Context example.json",
85
+ "modelName": "DMN_Context_Example",
86
+ "description": "Example of Context in Excel",
87
+ "modelType": "calculation",
88
+ "subcategory": null,
89
+ "features": [
90
+ "formulas",
91
+ "data"
92
+ ],
93
+ "tags": [
94
+ "calculation"
95
+ ]
96
+ },
97
+ {
98
+ "filePath": "calculation/DMNExamples/DMN DT with typeDef result.json",
99
+ "modelName": "DMN_DT_with_TypeDef_Result",
100
+ "description": "Decision Table model uses TypeDefs for all inputs/outputs.",
101
+ "modelType": "calculation",
102
+ "subcategory": null,
103
+ "features": [
104
+ "formulas",
105
+ "data",
106
+ "decision-tables"
107
+ ],
108
+ "decisionTableCount": 1,
109
+ "hitPolicies": [
110
+ "U"
111
+ ],
112
+ "tags": [
113
+ "calculation",
114
+ "decision-table"
115
+ ]
116
+ },
117
+ {
118
+ "filePath": "calculation/DecisionTables/DT Datasource example.json",
119
+ "modelName": "DTDatasourceExample",
120
+ "description": "",
121
+ "modelType": "calculation",
122
+ "subcategory": null,
123
+ "features": [
124
+ "formulas",
125
+ "data",
126
+ "datasources",
127
+ "decision-tables"
128
+ ],
129
+ "decisionTableCount": 1,
130
+ "hitPolicies": [
131
+ "U"
132
+ ],
133
+ "tags": [
134
+ "calculation",
135
+ "data-binding",
136
+ "decision-table"
137
+ ]
138
+ },
139
+ {
140
+ "filePath": "calculation/DecisionTables/DT Date and Time examples.json",
141
+ "modelName": "DTDateTimeExample",
142
+ "description": "RASON Date and Time Decision Table Examples: Decision Tables contain a set of rules which specify actions to perform based on specific conditions. Decision tables are a good tool to use when there is a consistent number of rules, or conditions, to be evaluated followed by a specific set of actions to be perfrmed once a rule, or condition, is met. This example contains 3 decision tables, tblRiskRating, tblTollTax and tblParkingFee.",
143
+ "modelType": "calculation",
144
+ "subcategory": null,
145
+ "features": [
146
+ "formulas",
147
+ "data",
148
+ "decision-tables"
149
+ ],
150
+ "decisionTableCount": 3,
151
+ "hitPolicies": [
152
+ "U"
153
+ ],
154
+ "tags": [
155
+ "calculation",
156
+ "decision-table"
157
+ ]
158
+ },
159
+ {
160
+ "filePath": "calculation/DecisionTables/DT Expression example.json",
161
+ "modelName": "DTExpressionExample",
162
+ "description": "RASON Decision Table Example using an Expression: This example illustrates how to utilize duration in an expression in the body of a decision table. The tblParkingFee decision table calculates a fee based on the time spent in a parking garage.",
163
+ "modelType": "calculation",
164
+ "subcategory": null,
165
+ "features": [
166
+ "formulas",
167
+ "data",
168
+ "decision-tables"
169
+ ],
170
+ "decisionTableCount": 1,
171
+ "hitPolicies": [
172
+ "Unique"
173
+ ],
174
+ "tags": [
175
+ "calculation",
176
+ "decision-table"
177
+ ]
178
+ },
179
+ {
180
+ "filePath": "calculation/DecisionTables/DT Hit Policy examples.json",
181
+ "modelName": "DTHitPolicyExample",
182
+ "description": "RASON Decision Table Hit Policy Example: This example illustrates the use of all 7 Hit Policies supported by RASON Decision Services: Unique, Any, Priority, First, Rule Order, Output Order, & Collect. See each table descriptions for more information.",
183
+ "modelType": "calculation",
184
+ "subcategory": null,
185
+ "features": [
186
+ "formulas",
187
+ "decision-tables"
188
+ ],
189
+ "decisionTableCount": 7,
190
+ "hitPolicies": [
191
+ "A",
192
+ "C+",
193
+ "U",
194
+ "F",
195
+ "R",
196
+ "O",
197
+ "P"
198
+ ],
199
+ "tags": [
200
+ "calculation",
201
+ "decision-table"
202
+ ]
203
+ },
204
+ {
205
+ "filePath": "calculation/DecisionTables/DT Loan Recommend model.json",
206
+ "modelName": "DTLoanRecommendExample",
207
+ "description": "RASON Decision Table Example: The decision table tblLoanTypes, returns a loan that meets the criteria passed in the loanTypes formula (within the formula section). A data table, bankRates, has been entered into the data section. This table lists various banks offering the types of loans listed in the rules section of the tblLoanTypes decision table. For example, AimLoan bank offers a conventional ARM 3/1 loan with a term of 360 months, APR of 3.103, requiring a 20% down payment. The loanTypes formula returns the loans meeting the criteria passed. The formula 'recom' (in the formula section), joins the results for 'loanTypes' with the data table, bankRates. The result for loanTypes is a table containing two loans an ARM 3/1 loan and a Fixed 40 loan. The PsiJoin function matches these two loans with the loans from the bankRates table to return several ARM 3/1 loans from various banks. (Since no bank offers the Fixed 40 loan, no results are returned for this loan.) For a complete walkthrough of this example, see the Decision Table chapter within Analytic Solver User Guide.",
208
+ "modelType": "calculation",
209
+ "subcategory": null,
210
+ "features": [
211
+ "formulas",
212
+ "data",
213
+ "decision-tables"
214
+ ],
215
+ "psiFunctions": [
216
+ "PsiJoin"
217
+ ],
218
+ "decisionTableCount": 1,
219
+ "hitPolicies": [
220
+ "C"
221
+ ],
222
+ "tags": [
223
+ "calculation",
224
+ "decision-table",
225
+ "probability-distribution"
226
+ ]
227
+ },
228
+ {
229
+ "filePath": "calculation/DecisionTables/DT Loan Strategy model and Datasource.json",
230
+ "modelName": "DTLoanStrategyExamplewDatasource",
231
+ "description": "RASON Decision Table Example: Loan Strategy model with imported data sources: The difference between this example and the original DTLoanStrategyModel, is that this example imports the customer data and loan data from an outside data source, in this example two CVS files: customers.txt and loans.txt.",
232
+ "modelType": "calculation",
233
+ "subcategory": null,
234
+ "features": [
235
+ "formulas",
236
+ "data",
237
+ "datasources",
238
+ "decision-tables"
239
+ ],
240
+ "decisionTableCount": 8,
241
+ "hitPolicies": [
242
+ "collect+",
243
+ "unique",
244
+ "priority"
245
+ ],
246
+ "tags": [
247
+ "calculation",
248
+ "data-binding",
249
+ "decision-table"
250
+ ]
251
+ },
252
+ {
253
+ "filePath": "calculation/DecisionTables/DT Loan Strategy model by scratch.json",
254
+ "modelName": "DTLoanStrategyFromScratch",
255
+ "description": "Loan Strategy model",
256
+ "modelType": "calculation",
257
+ "subcategory": null,
258
+ "features": [
259
+ "formulas",
260
+ "data",
261
+ "decision-tables"
262
+ ],
263
+ "decisionTableCount": 8,
264
+ "hitPolicies": [
265
+ "collect+",
266
+ "unique",
267
+ "priority"
268
+ ],
269
+ "tags": [
270
+ "calculation",
271
+ "decision-table"
272
+ ]
273
+ },
274
+ {
275
+ "filePath": "calculation/DecisionTables/DT Loan Strategy model and Predictive.json",
276
+ "modelName": "DTLoanStrategyPredictive",
277
+ "description": "RASON Decision Table Example: Loan Strategy using a PMML predictive model inline: The difference between this example and the original DTLoanStrategy example is that this example expands on the DT Loan Strategy Model by adding an element to the formula, appRiskScore. The formula for appRiskScore returns the minimum of 2 outputs. The first output is produced from a linear regression model scoring new data contained in predictiveInput (within the data section). The second output is from the decision table, tblAppRiskScore, given the inputs: custAge (40), maritalStatus (single) and employmentStatus (selfemployed).",
278
+ "modelType": "calculation",
279
+ "subcategory": null,
280
+ "features": [
281
+ "formulas",
282
+ "data",
283
+ "decision-tables"
284
+ ],
285
+ "psiFunctions": [
286
+ "PsiPredict"
287
+ ],
288
+ "decisionTableCount": 6,
289
+ "hitPolicies": [
290
+ "C+",
291
+ "U",
292
+ "P"
293
+ ],
294
+ "tags": [
295
+ "calculation",
296
+ "decision-table",
297
+ "probability-distribution"
298
+ ]
299
+ },
300
+ {
301
+ "filePath": "calculation/DecisionTables/DT Loan Strategy Model and Predictive CSV-XML.json",
302
+ "modelName": "DTLoanStrategyPredictiveCSVXML",
303
+ "description": "RASON Decision Table Example: Loan Strategy Example importing data using CSV and XML files: The difference between this example and the DTLoanStrategyPredictive exammple is that this example imports the predictive model from within the datasources section. The predictive model is then used to score new data. The output from the scoring is used as an input to a decision table.",
304
+ "modelType": "calculation",
305
+ "subcategory": null,
306
+ "features": [
307
+ "formulas",
308
+ "data",
309
+ "datasources",
310
+ "decision-tables"
311
+ ],
312
+ "psiFunctions": [
313
+ "PsiPredict"
314
+ ],
315
+ "decisionTableCount": 6,
316
+ "hitPolicies": [
317
+ "C+",
318
+ "U",
319
+ "P"
320
+ ],
321
+ "tags": [
322
+ "calculation",
323
+ "data-binding",
324
+ "decision-table",
325
+ "probability-distribution"
326
+ ]
327
+ },
328
+ {
329
+ "filePath": "calculation/DecisionTables/DT Output Order example.json",
330
+ "modelName": "DTOutputOrderExample",
331
+ "description": "RASON Decision Table Example using the ''O' policy: The example illustrates the sue of the Output Order hit policy which means that if multiple rules are hit, the collection of results is returned in the priority order as listed for outputValues. This decision table accepts two input parameters, age and service, and returns the number of vacation days that an employee is entitled to. ",
332
+ "modelType": "calculation",
333
+ "subcategory": null,
334
+ "features": [
335
+ "formulas",
336
+ "data",
337
+ "decision-tables"
338
+ ],
339
+ "decisionTableCount": 1,
340
+ "hitPolicies": [
341
+ "outputOrder"
342
+ ],
343
+ "tags": [
344
+ "calculation",
345
+ "decision-table"
346
+ ]
347
+ },
348
+ {
349
+ "filePath": "calculation/DecisionTables/DT Unique example.json",
350
+ "modelName": "DTUniqueExample",
351
+ "description": "RASON Decision Table Example using the 'U' policy: This decision table in this model returns a patient's health risk rating based on their age and medical history. ",
352
+ "modelType": "calculation",
353
+ "subcategory": null,
354
+ "features": [
355
+ "formulas",
356
+ "data",
357
+ "decision-tables"
358
+ ],
359
+ "decisionTableCount": 1,
360
+ "hitPolicies": [
361
+ "Unique"
362
+ ],
363
+ "tags": [
364
+ "calculation",
365
+ "decision-table"
366
+ ]
367
+ },
368
+ {
369
+ "filePath": "calculation/TypeDefinitions/TypeDefDT.json",
370
+ "modelName": "DTUniqueExamplewTypeDefandAllowedValues",
371
+ "description": "RASON Decision Table 'U' policy example with Type Definition and Allowed Values: This example calculates the health risk of an adult given two inputs: age and a medical history.",
372
+ "modelType": "calculation",
373
+ "subcategory": null,
374
+ "features": [
375
+ "formulas",
376
+ "data",
377
+ "decision-tables"
378
+ ],
379
+ "decisionTableCount": 1,
380
+ "hitPolicies": [
381
+ "Unique"
382
+ ],
383
+ "tags": [
384
+ "calculation",
385
+ "decision-table"
386
+ ]
387
+ },
388
+ {
389
+ "filePath": "calculation/DMNExamples/FEEL Date Time example.json",
390
+ "modelName": "FEEL_Date_Time_Example",
391
+ "description": "Example of specific Date/Time FEEL operations",
392
+ "modelType": "calculation",
393
+ "subcategory": null,
394
+ "features": [
395
+ "formulas",
396
+ "data"
397
+ ],
398
+ "tags": [
399
+ "calculation"
400
+ ]
401
+ },
402
+ {
403
+ "filePath": "calculation/DMNExamples/FEEL For iteration example.json",
404
+ "modelName": "FEEL_For_Iteration_Example",
405
+ "description": "",
406
+ "modelType": "calculation",
407
+ "subcategory": null,
408
+ "features": [
409
+ "formulas",
410
+ "data",
411
+ "box-functions"
412
+ ],
413
+ "tags": [
414
+ "box-function",
415
+ "calculation"
416
+ ]
417
+ },
418
+ {
419
+ "filePath": "calculation/DMNExamples/FEEL For with two indices.json",
420
+ "modelName": "FEEL_for_with_two_indices",
421
+ "description": "FEEL 'for' iteration example with two indices",
422
+ "modelType": "calculation",
423
+ "subcategory": null,
424
+ "features": [
425
+ "formulas",
426
+ "data"
427
+ ],
428
+ "tags": [
429
+ "calculation"
430
+ ]
431
+ },
432
+ {
433
+ "filePath": "calculation/DMNExamples/FEEL For with typeDef result.json",
434
+ "modelName": "FEEL_For_with_TypeDef_result",
435
+ "description": "Example of 'for' iteration in FEEL",
436
+ "modelType": "calculation",
437
+ "subcategory": null,
438
+ "features": [
439
+ "formulas",
440
+ "data",
441
+ "box-functions"
442
+ ],
443
+ "tags": [
444
+ "box-function",
445
+ "calculation"
446
+ ]
447
+ },
448
+ {
449
+ "filePath": "calculation/DMNExamples/FEEL If Then Else example.json",
450
+ "modelName": "FEEL_If_Then_Else_Example",
451
+ "description": "Example of 'if then else' in FEEL",
452
+ "modelType": "calculation",
453
+ "subcategory": null,
454
+ "features": [
455
+ "formulas",
456
+ "data",
457
+ "box-functions"
458
+ ],
459
+ "tags": [
460
+ "box-function",
461
+ "calculation"
462
+ ]
463
+ },
464
+ {
465
+ "filePath": "calculation/DMNExamples/FEEL List example.json",
466
+ "modelName": "FEEL_List_Example",
467
+ "description": "Example of a list with component type definition",
468
+ "modelType": "calculation",
469
+ "subcategory": null,
470
+ "features": [
471
+ "formulas",
472
+ "data"
473
+ ],
474
+ "tags": [
475
+ "calculation"
476
+ ]
477
+ },
478
+ {
479
+ "filePath": "calculation/DMNExamples/FEEL List operator.json",
480
+ "modelName": "FEEL_List_Operator",
481
+ "description": "Example of a list operator definition",
482
+ "modelType": "calculation",
483
+ "subcategory": null,
484
+ "features": [
485
+ "formulas",
486
+ "data"
487
+ ],
488
+ "tags": [
489
+ "calculation"
490
+ ]
491
+ },
492
+ {
493
+ "filePath": "calculation/DMNExamples/FEEL List with typeDef collection.json",
494
+ "modelName": "FEEL_List_with_typeDef_Collection",
495
+ "description": "",
496
+ "modelType": "calculation",
497
+ "subcategory": null,
498
+ "features": [
499
+ "formulas",
500
+ "data"
501
+ ],
502
+ "tags": [
503
+ "calculation"
504
+ ]
505
+ },
506
+ {
507
+ "filePath": "calculation/DMNExamples/FEEL Some or Every example.json",
508
+ "modelName": "FEEL_Some_or_Every_example",
509
+ "description": "",
510
+ "modelType": "calculation",
511
+ "subcategory": null,
512
+ "features": [
513
+ "formulas",
514
+ "data",
515
+ "box-functions"
516
+ ],
517
+ "tags": [
518
+ "box-function",
519
+ "calculation"
520
+ ]
521
+ },
522
+ {
523
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/DataFiltering/ListwithFilter.json",
524
+ "modelName": "ListwithFilter",
525
+ "description": "Example illustrating how to filter a table (list).",
526
+ "modelType": "calculation",
527
+ "subcategory": "data-filtering",
528
+ "features": [
529
+ "formulas",
530
+ "data"
531
+ ],
532
+ "isFeatureDemo": true,
533
+ "tags": [
534
+ "calculation",
535
+ "data-filtering"
536
+ ]
537
+ },
538
+ {
539
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/compoundWhileStatement.json",
540
+ "modelName": "compoundWhileStatement",
541
+ "description": "example of compound and while statements",
542
+ "modelType": "calculation",
543
+ "subcategory": "loops",
544
+ "features": [
545
+ "formulas",
546
+ "data"
547
+ ],
548
+ "isFeatureDemo": true,
549
+ "tags": [
550
+ "calculation",
551
+ "loops"
552
+ ]
553
+ },
554
+ {
555
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/ifThenElseStatement.json",
556
+ "modelName": "ifThenElseStatement",
557
+ "description": "example of if-then-else statement",
558
+ "modelType": "calculation",
559
+ "subcategory": "loops",
560
+ "features": [
561
+ "formulas",
562
+ "data"
563
+ ],
564
+ "isFeatureDemo": true,
565
+ "tags": [
566
+ "calculation",
567
+ "loops"
568
+ ]
569
+ },
570
+ {
571
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/nestedLoop.json",
572
+ "modelName": "nestedLoops",
573
+ "description": "Example of a nested loop",
574
+ "modelType": "calculation",
575
+ "subcategory": "loops",
576
+ "features": [
577
+ "formulas",
578
+ "data"
579
+ ],
580
+ "isFeatureDemo": true,
581
+ "tags": [
582
+ "calculation",
583
+ "loops"
584
+ ]
585
+ },
586
+ {
587
+ "filePath": "datamining/AffinityAnalysis/AssociationRules.json",
588
+ "modelName": "AssociationRules",
589
+ "description": "Affinity Analysis: Association Rules. This RASON model example showcases the Association Rules feature. The goal of association rules mining is to recognize associations and/or correlations among large sets of data items, such as market basket analysis.",
590
+ "modelType": "datamining",
591
+ "subcategory": "affinity",
592
+ "features": [
593
+ "datasources",
594
+ "datasets",
595
+ "estimator",
596
+ "actions"
597
+ ],
598
+ "algorithmType": "affinityAnalysis",
599
+ "algorithm": "associationRules",
600
+ "dataSourceTypes": [
601
+ "csv"
602
+ ],
603
+ "actions": [
604
+ "fit",
605
+ "transform"
606
+ ],
607
+ "tags": [
608
+ "affinity",
609
+ "affinityAnalysis",
610
+ "associationRules",
611
+ "data-binding",
612
+ "data-science",
613
+ "machine-learning"
614
+ ]
615
+ },
616
+ {
617
+ "filePath": "datamining/Classification/DecisionTree.json",
618
+ "modelName": "DecisionTreeClassification",
619
+ "description": "Classification: Decision Tree; This RASON model example generates a fitted model and POSTs the model to the RASON server. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
620
+ "modelType": "datamining",
621
+ "subcategory": "classification",
622
+ "features": [
623
+ "datasources",
624
+ "datasets",
625
+ "estimator",
626
+ "actions",
627
+ "preprocessor"
628
+ ],
629
+ "algorithmType": "classification",
630
+ "algorithm": "decisionTree",
631
+ "dataSourceTypes": [
632
+ "csv"
633
+ ],
634
+ "actions": [
635
+ "fit",
636
+ "predict"
637
+ ],
638
+ "tags": [
639
+ "classification",
640
+ "data-binding",
641
+ "data-science",
642
+ "decisionTree",
643
+ "machine-learning"
644
+ ]
645
+ },
646
+ {
647
+ "filePath": "datamining/Classification/DiscriminantAnalysis.json",
648
+ "modelName": "DiscriminantAnalysis",
649
+ "description": "This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
650
+ "modelType": "datamining",
651
+ "subcategory": "classification",
652
+ "features": [
653
+ "datasources",
654
+ "datasets",
655
+ "estimator",
656
+ "actions"
657
+ ],
658
+ "algorithmType": "classification",
659
+ "algorithm": "discriminantAnalysis",
660
+ "dataSourceTypes": [
661
+ "csv"
662
+ ],
663
+ "actions": [
664
+ "fit",
665
+ "predict"
666
+ ],
667
+ "tags": [
668
+ "classification",
669
+ "data-binding",
670
+ "data-science",
671
+ "discriminantAnalysis",
672
+ "machine-learning"
673
+ ]
674
+ },
675
+ {
676
+ "filePath": "datamining/Classification/FindBestModel.json",
677
+ "modelName": "FindBestModelClassify",
678
+ "description": "",
679
+ "modelType": "datamining",
680
+ "subcategory": "classification",
681
+ "features": [
682
+ "datasources",
683
+ "datasets",
684
+ "estimator",
685
+ "actions"
686
+ ],
687
+ "algorithmType": "classification",
688
+ "algorithm": "findBestModel",
689
+ "dataSourceTypes": [
690
+ "csv"
691
+ ],
692
+ "actions": [
693
+ "fit",
694
+ "predict"
695
+ ],
696
+ "tags": [
697
+ "classification",
698
+ "data-binding",
699
+ "data-science",
700
+ "findBestModel",
701
+ "machine-learning"
702
+ ]
703
+ },
704
+ {
705
+ "filePath": "datamining/Classification/LogisticRegression.json",
706
+ "modelName": "LogisticRegression",
707
+ "description": "Classification logistic regression: This RASON model example generates a fitted model and POSTs the model to the RASON server. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
708
+ "modelType": "datamining",
709
+ "subcategory": "classification",
710
+ "features": [
711
+ "datasources",
712
+ "datasets",
713
+ "estimator",
714
+ "actions"
715
+ ],
716
+ "algorithmType": "classification",
717
+ "algorithm": "logisticRegression",
718
+ "dataSourceTypes": [
719
+ "csv"
720
+ ],
721
+ "actions": [
722
+ "fit",
723
+ "predict"
724
+ ],
725
+ "tags": [
726
+ "classification",
727
+ "data-binding",
728
+ "data-science",
729
+ "logisticRegression",
730
+ "machine-learning"
731
+ ]
732
+ },
733
+ {
734
+ "filePath": "datamining/Classification/NaiveBayes.json",
735
+ "modelName": "NaiveBayes",
736
+ "description": "Classification: Naive Bayes: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
737
+ "modelType": "datamining",
738
+ "subcategory": "classification",
739
+ "features": [
740
+ "datasources",
741
+ "datasets",
742
+ "estimator",
743
+ "actions"
744
+ ],
745
+ "algorithmType": "classification",
746
+ "algorithm": "naiveBayes",
747
+ "dataSourceTypes": [
748
+ "csv"
749
+ ],
750
+ "actions": [
751
+ "fit",
752
+ "predict"
753
+ ],
754
+ "tags": [
755
+ "classification",
756
+ "data-binding",
757
+ "data-science",
758
+ "machine-learning",
759
+ "naiveBayes"
760
+ ]
761
+ },
762
+ {
763
+ "filePath": "datamining/Classification/NearestNeighbors.json",
764
+ "modelName": "NearestNeighborsClassification",
765
+ "description": "Classification: K Nearest Neighbors; This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
766
+ "modelType": "datamining",
767
+ "subcategory": "classification",
768
+ "features": [
769
+ "datasources",
770
+ "datasets",
771
+ "estimator",
772
+ "actions"
773
+ ],
774
+ "algorithmType": "classification",
775
+ "algorithm": "nearestNeighbors",
776
+ "dataSourceTypes": [
777
+ "csv"
778
+ ],
779
+ "actions": [
780
+ "fit",
781
+ "predict"
782
+ ],
783
+ "tags": [
784
+ "classification",
785
+ "data-binding",
786
+ "data-science",
787
+ "machine-learning",
788
+ "nearestNeighbors"
789
+ ]
790
+ },
791
+ {
792
+ "filePath": "datamining/Classification/NeuralNetwork.json",
793
+ "modelName": "NeuralNetworkClassification",
794
+ "description": "Classification: Neural Network; This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.txt. Both 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 both hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
795
+ "modelType": "datamining",
796
+ "subcategory": "classification",
797
+ "features": [
798
+ "datasources",
799
+ "datasets",
800
+ "estimator",
801
+ "actions"
802
+ ],
803
+ "algorithmType": "classification",
804
+ "algorithm": "neuralNetwork",
805
+ "dataSourceTypes": [
806
+ "csv"
807
+ ],
808
+ "actions": [
809
+ "fit",
810
+ "predict"
811
+ ],
812
+ "tags": [
813
+ "classification",
814
+ "data-binding",
815
+ "data-science",
816
+ "machine-learning",
817
+ "neuralNetwork"
818
+ ]
819
+ },
820
+ {
821
+ "filePath": "datamining/Clustering/Hierarchical.json",
822
+ "modelName": "HierarchicalClustering",
823
+ "description": "Clustering: Hierarchical: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score a dataset. This example uses an outside data source, hald-small.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 hald-small.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 Science Model.",
824
+ "modelType": "datamining",
825
+ "subcategory": "clustering",
826
+ "features": [
827
+ "datasources",
828
+ "datasets",
829
+ "estimator",
830
+ "actions"
831
+ ],
832
+ "algorithmType": "clustering",
833
+ "algorithm": "hierarchical",
834
+ "dataSourceTypes": [
835
+ "csv"
836
+ ],
837
+ "actions": [
838
+ "fit",
839
+ "predict"
840
+ ],
841
+ "tags": [
842
+ "clustering",
843
+ "data-binding",
844
+ "data-science",
845
+ "hierarchical",
846
+ "machine-learning"
847
+ ]
848
+ },
849
+ {
850
+ "filePath": "datamining/Clustering/KMeans.json",
851
+ "modelName": "KMeansClustering",
852
+ "description": "k-Means Clustering Example: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score a dataset. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.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 both files. 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 Science Model.",
853
+ "modelType": "datamining",
854
+ "subcategory": "clustering",
855
+ "features": [
856
+ "datasources",
857
+ "datasets",
858
+ "estimator",
859
+ "actions"
860
+ ],
861
+ "algorithmType": "clustering",
862
+ "algorithm": "kMeans",
863
+ "dataSourceTypes": [
864
+ "csv"
865
+ ],
866
+ "actions": [
867
+ "fit",
868
+ "predict"
869
+ ],
870
+ "tags": [
871
+ "clustering",
872
+ "data-binding",
873
+ "data-science",
874
+ "kMeans",
875
+ "machine-learning"
876
+ ]
877
+ },
878
+ {
879
+ "filePath": "datamining/DataSources/DelimitedFile.json",
880
+ "modelName": "DelimitedFile",
881
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within the hald-small.txt delimited file. This example uses the outside data source, hald-small, 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 the hald-small.txt file. Click Open. 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 Science Model.",
882
+ "modelType": "datamining",
883
+ "subcategory": "data-sources",
884
+ "features": [
885
+ "datasources",
886
+ "datasets",
887
+ "estimator",
888
+ "actions"
889
+ ],
890
+ "algorithmType": "transformation",
891
+ "algorithm": "rescaling",
892
+ "dataSourceTypes": [
893
+ "csv"
894
+ ],
895
+ "actions": [
896
+ "fit",
897
+ "transform"
898
+ ],
899
+ "tags": [
900
+ "data-binding",
901
+ "data-science",
902
+ "data-sources",
903
+ "machine-learning",
904
+ "rescaling",
905
+ "transformation"
906
+ ]
907
+ },
908
+ {
909
+ "filePath": "datamining/DataSources/JSONFile.json",
910
+ "modelName": "JSONFile",
911
+ "description": "Transformation: Rescaling: This example uses the outside data source, hald-small-nested.json, 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 the hald-small-nested.json file. Click Open. 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 Science Model.",
912
+ "modelType": "datamining",
913
+ "subcategory": "data-sources",
914
+ "features": [
915
+ "datasources",
916
+ "datasets",
917
+ "estimator",
918
+ "actions"
919
+ ],
920
+ "algorithmType": "transformation",
921
+ "algorithm": "rescaling",
922
+ "dataSourceTypes": [
923
+ "json"
924
+ ],
925
+ "actions": [
926
+ "fit",
927
+ "transform"
928
+ ],
929
+ "tags": [
930
+ "data-binding",
931
+ "data-science",
932
+ "data-sources",
933
+ "machine-learning",
934
+ "rescaling",
935
+ "transformation"
936
+ ]
937
+ },
938
+ {
939
+ "filePath": "datamining/DataSources/MSAccessDatabase.json",
940
+ "modelName": "MSAccessDatabase",
941
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within a Microsoft Access database. This example uses the database, ms-access-db.accdb, 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 the ms-access-db.accdb database. Click Open. 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 Science Model.",
942
+ "modelType": "datamining",
943
+ "subcategory": "data-sources",
944
+ "features": [
945
+ "datasources",
946
+ "datasets",
947
+ "estimator",
948
+ "actions"
949
+ ],
950
+ "algorithmType": "transformation",
951
+ "algorithm": "rescaling",
952
+ "dataSourceTypes": [
953
+ "access"
954
+ ],
955
+ "actions": [
956
+ "fit",
957
+ "transform"
958
+ ],
959
+ "tags": [
960
+ "data-binding",
961
+ "data-science",
962
+ "data-sources",
963
+ "machine-learning",
964
+ "rescaling",
965
+ "transformation"
966
+ ]
967
+ },
968
+ {
969
+ "filePath": "datamining/DataSources/MSExcelTable.json",
970
+ "modelName": "MSExcelTable",
971
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within the Microsoft Excel spreadsheet, hald.xlsx, 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 the hald.xlsx workbook. Click Open. 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 Science Model.",
972
+ "modelType": "datamining",
973
+ "subcategory": "data-sources",
974
+ "features": [
975
+ "datasources",
976
+ "datasets",
977
+ "estimator",
978
+ "actions"
979
+ ],
980
+ "algorithmType": "transformation",
981
+ "algorithm": "rescaling",
982
+ "dataSourceTypes": [
983
+ "excel"
984
+ ],
985
+ "actions": [
986
+ "fit",
987
+ "transform"
988
+ ],
989
+ "tags": [
990
+ "data-binding",
991
+ "data-science",
992
+ "data-sources",
993
+ "machine-learning",
994
+ "rescaling",
995
+ "transformation"
996
+ ]
997
+ },
998
+ {
999
+ "filePath": "datamining/DataSources/MSSQLDatabase.json",
1000
+ "modelName": "MSSQLDatabase",
1001
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within an MS-SQL database. (This model is for illustration purposes only.) Note that RASON now allows Data Connections. In previous versions of RASON, models that accessed external databases required actual credentials to be passed, such as database URLs, port numbers, usernames and passwords, in the text of the RASON model, in a datasource declaration, as shown below. RASON now offers an alternative to tackle this security risk by substituting 'connection': 'Driver={SQL Server} ...' with three options: a file containing the contents of 'connection', a named Data Connection or a URL pointing to Microsoft Common Data Service. Click Help - Rason Subscriptions -- Data Connections for more information.",
1002
+ "modelType": "datamining",
1003
+ "subcategory": "data-sources",
1004
+ "features": [
1005
+ "datasources",
1006
+ "datasets",
1007
+ "estimator",
1008
+ "actions"
1009
+ ],
1010
+ "algorithmType": "transformation",
1011
+ "algorithm": "rescaling",
1012
+ "dataSourceTypes": [
1013
+ "mssql"
1014
+ ],
1015
+ "actions": [
1016
+ "fit",
1017
+ "transform"
1018
+ ],
1019
+ "tags": [
1020
+ "data-binding",
1021
+ "data-science",
1022
+ "data-sources",
1023
+ "machine-learning",
1024
+ "rescaling",
1025
+ "transformation"
1026
+ ]
1027
+ },
1028
+ {
1029
+ "filePath": "datamining/DataSources/ODATATable.json",
1030
+ "modelName": "ODATATable",
1031
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within an OData table. (This model is for illustration purposes only.) See below for information on using a Data Connection.",
1032
+ "modelType": "datamining",
1033
+ "subcategory": "data-sources",
1034
+ "features": [
1035
+ "datasources",
1036
+ "datasets",
1037
+ "estimator",
1038
+ "actions"
1039
+ ],
1040
+ "algorithmType": "transformation",
1041
+ "algorithm": "rescaling",
1042
+ "dataSourceTypes": [
1043
+ "odata"
1044
+ ],
1045
+ "actions": [
1046
+ "fit",
1047
+ "transform"
1048
+ ],
1049
+ "tags": [
1050
+ "data-binding",
1051
+ "data-science",
1052
+ "data-sources",
1053
+ "machine-learning",
1054
+ "rescaling",
1055
+ "transformation"
1056
+ ]
1057
+ },
1058
+ {
1059
+ "filePath": "datamining/DataSources/ODBCDatabase.json",
1060
+ "modelName": "ODBCDatabase",
1061
+ "description": "Transformation: Rescaling: This RASON model example rescales the data contained within an ODBC database. (This example is for illustration purposes only.) Note that RASON now allows Data Connections. In previous versions of RASON, models that accessed external databases required actual credentials to be passed, such as database URLs, port numbers, usernames and passwords, in the text of the RASON model, in a datasource declaration, as shown below. RASON now offers an alternative to tackle this security risk by substituting 'connection': 'Driver={SQL Server} ...' with three options: a file containing the contents of 'connection', a named Data Connection or a URL pointing to Microsoft Common Data Service. Click Help - Rason Subscriptions -- Data Connections for more information.",
1062
+ "modelType": "datamining",
1063
+ "subcategory": "data-sources",
1064
+ "features": [
1065
+ "datasources",
1066
+ "datasets",
1067
+ "estimator",
1068
+ "actions"
1069
+ ],
1070
+ "algorithmType": "transformation",
1071
+ "algorithm": "rescaling",
1072
+ "dataSourceTypes": [
1073
+ "odbc"
1074
+ ],
1075
+ "actions": [
1076
+ "fit",
1077
+ "transform"
1078
+ ],
1079
+ "tags": [
1080
+ "data-binding",
1081
+ "data-science",
1082
+ "data-sources",
1083
+ "machine-learning",
1084
+ "rescaling",
1085
+ "transformation"
1086
+ ]
1087
+ },
1088
+ {
1089
+ "filePath": "datamining/Classification/Ensembles/Bagging.json",
1090
+ "modelName": "BaggingClassification",
1091
+ "description": "Bagging Classification Example: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score the training partition. This example uses one outside data source, hald-small-binary-train.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 hald-small-binary-train.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 Science Model.",
1092
+ "modelType": "datamining",
1093
+ "subcategory": "ensembles",
1094
+ "features": [
1095
+ "datasources",
1096
+ "datasets",
1097
+ "estimator",
1098
+ "actions"
1099
+ ],
1100
+ "algorithmType": "classification",
1101
+ "algorithm": "bagging",
1102
+ "dataSourceTypes": [
1103
+ "csv"
1104
+ ],
1105
+ "actions": [
1106
+ "fit",
1107
+ "predict"
1108
+ ],
1109
+ "tags": [
1110
+ "bagging",
1111
+ "classification",
1112
+ "data-binding",
1113
+ "data-science",
1114
+ "ensembles",
1115
+ "machine-learning"
1116
+ ]
1117
+ },
1118
+ {
1119
+ "filePath": "datamining/Regression/Ensembles/Bagging.json",
1120
+ "modelName": "BaggingRegression",
1121
+ "description": "Bagging Regression Example: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score the training partition. This example uses one outside data source, hald-small.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 hald-small.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 Science Model.",
1122
+ "modelType": "datamining",
1123
+ "subcategory": "ensembles",
1124
+ "features": [
1125
+ "datasources",
1126
+ "datasets",
1127
+ "estimator",
1128
+ "actions"
1129
+ ],
1130
+ "algorithmType": "regression",
1131
+ "algorithm": "bagging",
1132
+ "dataSourceTypes": [
1133
+ "csv"
1134
+ ],
1135
+ "actions": [
1136
+ "fit",
1137
+ "predict"
1138
+ ],
1139
+ "tags": [
1140
+ "bagging",
1141
+ "data-binding",
1142
+ "data-science",
1143
+ "ensembles",
1144
+ "machine-learning",
1145
+ "regression"
1146
+ ]
1147
+ },
1148
+ {
1149
+ "filePath": "datamining/Classification/Ensembles/Boosting.json",
1150
+ "modelName": "BoostingClassification",
1151
+ "description": "Classification Boosting Example: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score the training partition. This example uses one outside data source, hald-small-binary-train.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 hald-small-binary-train.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 Science Model.",
1152
+ "modelType": "datamining",
1153
+ "subcategory": "ensembles",
1154
+ "features": [
1155
+ "datasources",
1156
+ "datasets",
1157
+ "estimator",
1158
+ "actions"
1159
+ ],
1160
+ "algorithmType": "classification",
1161
+ "algorithm": "boosting",
1162
+ "dataSourceTypes": [
1163
+ "csv"
1164
+ ],
1165
+ "actions": [
1166
+ "fit",
1167
+ "predict"
1168
+ ],
1169
+ "tags": [
1170
+ "boosting",
1171
+ "classification",
1172
+ "data-binding",
1173
+ "data-science",
1174
+ "ensembles",
1175
+ "machine-learning"
1176
+ ]
1177
+ },
1178
+ {
1179
+ "filePath": "datamining/Regression/Ensembles/Boosting.json",
1180
+ "modelName": "BoostingRegression",
1181
+ "description": "Regression Boosting Example: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score the training partition. This example uses one outside data source, hald-small.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 hald-small.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.",
1182
+ "modelType": "datamining",
1183
+ "subcategory": "ensembles",
1184
+ "features": [
1185
+ "datasources",
1186
+ "datasets",
1187
+ "estimator",
1188
+ "actions"
1189
+ ],
1190
+ "algorithmType": "regression",
1191
+ "algorithm": "boosting",
1192
+ "dataSourceTypes": [
1193
+ "csv"
1194
+ ],
1195
+ "actions": [
1196
+ "fit",
1197
+ "predict"
1198
+ ],
1199
+ "tags": [
1200
+ "boosting",
1201
+ "data-binding",
1202
+ "data-science",
1203
+ "ensembles",
1204
+ "machine-learning",
1205
+ "regression"
1206
+ ]
1207
+ },
1208
+ {
1209
+ "filePath": "datamining/Regression/Ensembles/RandomTrees.json",
1210
+ "modelName": "RandomTreesRegression",
1211
+ "description": "Regression Random Trees: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-train.txt and hald-small-valid.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, select both files and click Open. 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.",
1212
+ "modelType": "datamining",
1213
+ "subcategory": "ensembles",
1214
+ "features": [
1215
+ "datasources",
1216
+ "datasets",
1217
+ "estimator",
1218
+ "actions",
1219
+ "preprocessor"
1220
+ ],
1221
+ "algorithmType": "regression",
1222
+ "algorithm": "randomTrees",
1223
+ "dataSourceTypes": [
1224
+ "csv"
1225
+ ],
1226
+ "actions": [
1227
+ "fit",
1228
+ "predict"
1229
+ ],
1230
+ "tags": [
1231
+ "data-binding",
1232
+ "data-science",
1233
+ "ensembles",
1234
+ "machine-learning",
1235
+ "randomTrees",
1236
+ "regression"
1237
+ ]
1238
+ },
1239
+ {
1240
+ "filePath": "datamining/Classification/Ensembles/RandomTrees.json",
1241
+ "modelName": "RTClassification",
1242
+ "description": "Classification Random Trees: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-binary-train.txt and hald-small-binary-valid.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 hald-small-binary-train.txt and hald-small-binary-valid.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 Science Model.",
1243
+ "modelType": "datamining",
1244
+ "subcategory": "ensembles",
1245
+ "features": [
1246
+ "datasources",
1247
+ "datasets",
1248
+ "estimator",
1249
+ "actions",
1250
+ "preprocessor"
1251
+ ],
1252
+ "algorithmType": "classification",
1253
+ "algorithm": "randomTrees",
1254
+ "dataSourceTypes": [
1255
+ "csv"
1256
+ ],
1257
+ "actions": [
1258
+ "fit",
1259
+ "predict"
1260
+ ],
1261
+ "tags": [
1262
+ "classification",
1263
+ "data-binding",
1264
+ "data-science",
1265
+ "ensembles",
1266
+ "machine-learning",
1267
+ "randomTrees"
1268
+ ]
1269
+ },
1270
+ {
1271
+ "filePath": "datamining/FeatureSelection/LinearWrapping.json",
1272
+ "modelName": "LinearWrapping",
1273
+ "description": "Feature Selection Linear Wrapping: This RASON model example illustrates how to import data from an outside datasource, fit a model to the Feature Selection estimator, then use the fitted model to transform the dataset using feature selection linear wrapping.",
1274
+ "modelType": "datamining",
1275
+ "subcategory": "feature-selection",
1276
+ "features": [
1277
+ "datasources",
1278
+ "datasets",
1279
+ "estimator",
1280
+ "actions"
1281
+ ],
1282
+ "algorithmType": "featureSelection",
1283
+ "algorithm": "linearWrapping",
1284
+ "dataSourceTypes": [
1285
+ "csv"
1286
+ ],
1287
+ "actions": [
1288
+ "fit",
1289
+ "transform"
1290
+ ],
1291
+ "tags": [
1292
+ "data-binding",
1293
+ "data-science",
1294
+ "feature-selection",
1295
+ "featureSelection",
1296
+ "linearWrapping",
1297
+ "machine-learning"
1298
+ ]
1299
+ },
1300
+ {
1301
+ "filePath": "datamining/FeatureSelection/LogisticWrapping.json",
1302
+ "modelName": "LogisticWrapping",
1303
+ "description": "Feature Selection Logistic Wrapping: This RASON model example illustrates how to import data from an outside datasource, fit a model to the Feature Selection estimator, then use the fitted model to transform the dataset using feature selection logistic wrapping.",
1304
+ "modelType": "datamining",
1305
+ "subcategory": "feature-selection",
1306
+ "features": [
1307
+ "datasources",
1308
+ "datasets",
1309
+ "estimator",
1310
+ "actions"
1311
+ ],
1312
+ "algorithmType": "featureSelection",
1313
+ "algorithm": "logisticWrapping",
1314
+ "dataSourceTypes": [
1315
+ "csv"
1316
+ ],
1317
+ "actions": [
1318
+ "fit",
1319
+ "transform"
1320
+ ],
1321
+ "tags": [
1322
+ "data-binding",
1323
+ "data-science",
1324
+ "feature-selection",
1325
+ "featureSelection",
1326
+ "logisticWrapping",
1327
+ "machine-learning"
1328
+ ]
1329
+ },
1330
+ {
1331
+ "filePath": "datamining/FeatureSelection/Univariate.json",
1332
+ "modelName": "Univariate",
1333
+ "description": "Feature Selection Univariate: This RASON model example illustrates how to import data from an outside datasource, fit a model to the Feature Selection estimator, then use the fitted model to transform the dataset using feature selection univariate.",
1334
+ "modelType": "datamining",
1335
+ "subcategory": "feature-selection",
1336
+ "features": [
1337
+ "datasources",
1338
+ "datasets",
1339
+ "estimator",
1340
+ "actions"
1341
+ ],
1342
+ "algorithmType": "featureSelection",
1343
+ "algorithm": "univariate",
1344
+ "dataSourceTypes": [
1345
+ "csv"
1346
+ ],
1347
+ "actions": [
1348
+ "fit",
1349
+ "transform"
1350
+ ],
1351
+ "tags": [
1352
+ "data-binding",
1353
+ "data-science",
1354
+ "feature-selection",
1355
+ "featureSelection",
1356
+ "machine-learning",
1357
+ "univariate"
1358
+ ]
1359
+ },
1360
+ {
1361
+ "filePath": "datamining/Regression/DecisionTree.json",
1362
+ "modelName": "DecisionTreeRegression",
1363
+ "description": "Regression Decision Trees: This RASON model example generates a fitted model and POSTs the model to the RASON server. This example uses two outside data sources, hald-small-train.txt and hald-small-valid.txt. Both 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 both hald-small-train.txt and hald-small-valid.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 Science Model.",
1364
+ "modelType": "datamining",
1365
+ "subcategory": "regression",
1366
+ "features": [
1367
+ "datasources",
1368
+ "datasets",
1369
+ "estimator",
1370
+ "actions",
1371
+ "preprocessor"
1372
+ ],
1373
+ "algorithmType": "regression",
1374
+ "algorithm": "decisionTree",
1375
+ "dataSourceTypes": [
1376
+ "csv"
1377
+ ],
1378
+ "actions": [
1379
+ "fit",
1380
+ "predict"
1381
+ ],
1382
+ "tags": [
1383
+ "data-binding",
1384
+ "data-science",
1385
+ "decisionTree",
1386
+ "machine-learning",
1387
+ "regression"
1388
+ ]
1389
+ },
1390
+ {
1391
+ "filePath": "datamining/Regression/FindBestModel.json",
1392
+ "modelName": "FindBestModelPredict",
1393
+ "description": "",
1394
+ "modelType": "datamining",
1395
+ "subcategory": "regression",
1396
+ "features": [
1397
+ "datasources",
1398
+ "datasets",
1399
+ "estimator",
1400
+ "actions"
1401
+ ],
1402
+ "algorithmType": "regression",
1403
+ "algorithm": "findBestModel",
1404
+ "dataSourceTypes": [
1405
+ "csv"
1406
+ ],
1407
+ "actions": [
1408
+ "fit",
1409
+ "predict"
1410
+ ],
1411
+ "tags": [
1412
+ "data-binding",
1413
+ "data-science",
1414
+ "findBestModel",
1415
+ "machine-learning",
1416
+ "regression"
1417
+ ]
1418
+ },
1419
+ {
1420
+ "filePath": "datamining/Regression/LinearRegression.json",
1421
+ "modelName": "LinearRegression",
1422
+ "description": "Regression: Linear Model: This RASON model example generates a fitted model and POSTs the model to the RASON server. This example uses three outside data sources, hald-small-train.txt, hald-small-valid.txt and hald-small-score-single-rec.txt. All 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 all three files. 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 Science Model.",
1423
+ "modelType": "datamining",
1424
+ "subcategory": "regression",
1425
+ "features": [
1426
+ "datasources",
1427
+ "datasets",
1428
+ "estimator",
1429
+ "actions"
1430
+ ],
1431
+ "algorithmType": "regression",
1432
+ "algorithm": "linearRegression",
1433
+ "dataSourceTypes": [
1434
+ "csv"
1435
+ ],
1436
+ "actions": [
1437
+ "fit",
1438
+ "predict"
1439
+ ],
1440
+ "tags": [
1441
+ "data-binding",
1442
+ "data-science",
1443
+ "linearRegression",
1444
+ "machine-learning",
1445
+ "regression"
1446
+ ]
1447
+ },
1448
+ {
1449
+ "filePath": "datamining/Regression/NearestNeighbors.json",
1450
+ "modelName": "NearestNeighborsRegression",
1451
+ "description": "Regression: K Nearest Neighbors; This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-train.txt and hald-small-valid.txt. Both 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 both files. 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 Science Model.",
1452
+ "modelType": "datamining",
1453
+ "subcategory": "regression",
1454
+ "features": [
1455
+ "datasources",
1456
+ "datasets",
1457
+ "estimator",
1458
+ "actions"
1459
+ ],
1460
+ "algorithmType": "regression",
1461
+ "algorithm": "nearestNeighbors",
1462
+ "dataSourceTypes": [
1463
+ "csv"
1464
+ ],
1465
+ "actions": [
1466
+ "fit",
1467
+ "predict"
1468
+ ],
1469
+ "tags": [
1470
+ "data-binding",
1471
+ "data-science",
1472
+ "machine-learning",
1473
+ "nearestNeighbors",
1474
+ "regression"
1475
+ ]
1476
+ },
1477
+ {
1478
+ "filePath": "datamining/Regression/NeuralNetwork.json",
1479
+ "modelName": "NeuralNetworkRegression",
1480
+ "description": "Regression Neural Network: This RASON model example generates a fitted model and POSTs the model to the RASON server. Then uses the fitted model to score both the training and validation partitions. This example uses two outside data sources, hald-small-train.txt and hald-small-valid.txt. Both 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 both hald-small-train.txt and hald-small-valid.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 Science Model.",
1481
+ "modelType": "datamining",
1482
+ "subcategory": "regression",
1483
+ "features": [
1484
+ "datasources",
1485
+ "datasets",
1486
+ "estimator",
1487
+ "actions"
1488
+ ],
1489
+ "algorithmType": "regression",
1490
+ "algorithm": "neuralNetwork",
1491
+ "dataSourceTypes": [
1492
+ "csv"
1493
+ ],
1494
+ "actions": [
1495
+ "fit",
1496
+ "predict"
1497
+ ],
1498
+ "tags": [
1499
+ "data-binding",
1500
+ "data-science",
1501
+ "machine-learning",
1502
+ "neuralNetwork",
1503
+ "regression"
1504
+ ]
1505
+ },
1506
+ {
1507
+ "filePath": "datamining/Scoring/JSONClassifier.json",
1508
+ "modelName": "JSONClassifier",
1509
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Nearest Neighbor Classification model (Examples -- Data Science -- Classification -- NearestNeighbors.json) which generates and POSTs the fitted model used in this example to the RASON server. In addition, this model also imports two datasources, hald-small-binary.txt and hald-small-binary-txt. Both can be downloaded by clicking the RASON Examples download icon. To attach the datasources to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select both files, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1510
+ "modelType": "datamining",
1511
+ "subcategory": "scoring",
1512
+ "features": [
1513
+ "datasources",
1514
+ "datasets",
1515
+ "actions"
1516
+ ],
1517
+ "dataSourceTypes": [
1518
+ "csv"
1519
+ ],
1520
+ "actions": [
1521
+ "predict"
1522
+ ],
1523
+ "tags": [
1524
+ "data-binding",
1525
+ "data-science",
1526
+ "machine-learning",
1527
+ "scoring"
1528
+ ]
1529
+ },
1530
+ {
1531
+ "filePath": "datamining/Scoring/JSONClassifierNN.json",
1532
+ "modelName": "JSONClassifierNN",
1533
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Neurel Network Classification model (Examples -- Data Science -- Classification -- NeuralNetwork.json) which generates and POSTs the fitted model used in this example to the RASON server. In addition, this model also imports two datasources, hald-small-binary.txt and hald-small-binary-txt. Both can be downloaded by clicking the RASON Examples download icon. To attach the datasources to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select both files, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1534
+ "modelType": "datamining",
1535
+ "subcategory": "scoring",
1536
+ "features": [
1537
+ "datasources",
1538
+ "datasets",
1539
+ "actions"
1540
+ ],
1541
+ "dataSourceTypes": [
1542
+ "csv"
1543
+ ],
1544
+ "actions": [
1545
+ "predict"
1546
+ ],
1547
+ "tags": [
1548
+ "data-binding",
1549
+ "data-science",
1550
+ "machine-learning",
1551
+ "scoring"
1552
+ ]
1553
+ },
1554
+ {
1555
+ "filePath": "datamining/Scoring/JSONClusterizer.json",
1556
+ "modelName": "JSONClusterizer",
1557
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the k-Nearest Neighbors Clustering model (Examples -- Data Science -- Clustering -- KMeans.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, hald-small-binary.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select hald-small-binary.txt, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1558
+ "modelType": "datamining",
1559
+ "subcategory": "scoring",
1560
+ "features": [
1561
+ "datasources",
1562
+ "datasets",
1563
+ "actions"
1564
+ ],
1565
+ "dataSourceTypes": [
1566
+ "csv"
1567
+ ],
1568
+ "actions": [
1569
+ "predict"
1570
+ ],
1571
+ "tags": [
1572
+ "data-binding",
1573
+ "data-science",
1574
+ "machine-learning",
1575
+ "scoring"
1576
+ ]
1577
+ },
1578
+ {
1579
+ "filePath": "datamining/Scoring/JSONForecaster.json",
1580
+ "modelName": "JSONForecaster",
1581
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the ARIMA example model (Examples -- Data Science -- Time Series -- ARIMA.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, close.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select close.txt, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1582
+ "modelType": "datamining",
1583
+ "subcategory": "scoring",
1584
+ "features": [
1585
+ "datasources",
1586
+ "datasets",
1587
+ "actions"
1588
+ ],
1589
+ "dataSourceTypes": [
1590
+ "csv"
1591
+ ],
1592
+ "actions": [
1593
+ "forecast",
1594
+ "transform"
1595
+ ],
1596
+ "tags": [
1597
+ "data-binding",
1598
+ "data-science",
1599
+ "machine-learning",
1600
+ "scoring"
1601
+ ]
1602
+ },
1603
+ {
1604
+ "filePath": "datamining/Scoring/JSONLinearRegression.json",
1605
+ "modelName": "JSONLinearRegression",
1606
+ "description": "This RASON model deomonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Linear Regression example model (Examples -- Data Science -- Regression -- LinearRegression.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports two datasources, hald-small.txt and hald-small-score.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the 2 files, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1607
+ "modelType": "datamining",
1608
+ "subcategory": "scoring",
1609
+ "features": [
1610
+ "datasources",
1611
+ "datasets",
1612
+ "actions"
1613
+ ],
1614
+ "dataSourceTypes": [
1615
+ "csv"
1616
+ ],
1617
+ "actions": [
1618
+ "predict"
1619
+ ],
1620
+ "tags": [
1621
+ "data-binding",
1622
+ "data-science",
1623
+ "machine-learning",
1624
+ "scoring"
1625
+ ]
1626
+ },
1627
+ {
1628
+ "filePath": "datamining/Scoring/JSONPCA.json",
1629
+ "modelName": "JSONPCA",
1630
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the PCA example model (Examples -- Data Science -- Transformation -- PrincipalComponentsAnalysis.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, Irisfacto.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the file, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1631
+ "modelType": "datamining",
1632
+ "subcategory": "scoring",
1633
+ "features": [
1634
+ "datasources",
1635
+ "datasets",
1636
+ "actions"
1637
+ ],
1638
+ "dataSourceTypes": [
1639
+ "csv"
1640
+ ],
1641
+ "actions": [
1642
+ "transform"
1643
+ ],
1644
+ "tags": [
1645
+ "data-binding",
1646
+ "data-science",
1647
+ "machine-learning",
1648
+ "scoring"
1649
+ ]
1650
+ },
1651
+ {
1652
+ "filePath": "datamining/Scoring/JSONRegressor.json",
1653
+ "modelName": "JSONRegressor",
1654
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Nearest Neighbors example model (Examples -- Data Science -- Regression -- NearestNeighbors.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports two datasources, hald-small.txt and hald-small-score.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the 2 files, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1655
+ "modelType": "datamining",
1656
+ "subcategory": "scoring",
1657
+ "features": [
1658
+ "datasources",
1659
+ "datasets",
1660
+ "actions"
1661
+ ],
1662
+ "dataSourceTypes": [
1663
+ "csv"
1664
+ ],
1665
+ "actions": [
1666
+ "predict"
1667
+ ],
1668
+ "tags": [
1669
+ "data-binding",
1670
+ "data-science",
1671
+ "machine-learning",
1672
+ "scoring"
1673
+ ]
1674
+ },
1675
+ {
1676
+ "filePath": "datamining/Scoring/JSONTransformer.json",
1677
+ "modelName": "JSONTransformer",
1678
+ "description": "This RASON model demonstrates how to transform a dataset containing new data using a previously fit, fitted model. In order to solve this model you must first run the Rescaling example model (Examples -- Data Science -- Transformation -- Rescaling.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, hald-small.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the file, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1679
+ "modelType": "datamining",
1680
+ "subcategory": "scoring",
1681
+ "features": [
1682
+ "datasources",
1683
+ "datasets",
1684
+ "actions"
1685
+ ],
1686
+ "dataSourceTypes": [
1687
+ "csv"
1688
+ ],
1689
+ "actions": [
1690
+ "transform"
1691
+ ],
1692
+ "tags": [
1693
+ "data-binding",
1694
+ "data-science",
1695
+ "machine-learning",
1696
+ "scoring"
1697
+ ]
1698
+ },
1699
+ {
1700
+ "filePath": "datamining/Scoring/PMMLClassifier.json",
1701
+ "modelName": "PMMLClassifier",
1702
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Logistic Regression example model (Examples -- Data Science -- Classification -- LogisticRegression.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports a datasource, hald-small-binary-score.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the file, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1703
+ "modelType": "datamining",
1704
+ "subcategory": "scoring",
1705
+ "features": [
1706
+ "datasources",
1707
+ "datasets",
1708
+ "actions"
1709
+ ],
1710
+ "dataSourceTypes": [
1711
+ "csv"
1712
+ ],
1713
+ "actions": [
1714
+ "predict"
1715
+ ],
1716
+ "tags": [
1717
+ "data-binding",
1718
+ "data-science",
1719
+ "machine-learning",
1720
+ "scoring"
1721
+ ]
1722
+ },
1723
+ {
1724
+ "filePath": "datamining/Scoring/PMMLForecaster.json",
1725
+ "modelName": "PMMLForecaster",
1726
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the ARIMA example model (Examples -- Data Science -- Time Series -- ARIMA.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, close.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select close.txt, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1727
+ "modelType": "datamining",
1728
+ "subcategory": "scoring",
1729
+ "features": [
1730
+ "datasources",
1731
+ "datasets",
1732
+ "actions"
1733
+ ],
1734
+ "dataSourceTypes": [
1735
+ "csv"
1736
+ ],
1737
+ "actions": [
1738
+ "forecast"
1739
+ ],
1740
+ "tags": [
1741
+ "data-binding",
1742
+ "data-science",
1743
+ "machine-learning",
1744
+ "scoring"
1745
+ ]
1746
+ },
1747
+ {
1748
+ "filePath": "datamining/Scoring/PMMLRegressor.json",
1749
+ "modelName": "PMMLRegressor",
1750
+ "description": "This RASON model demonstrates how to score new data using a previously fit, fitted model. In order to solve this model you must first run the Linear Regression example model (Examples -- Data Science -- Regression -- LinearRegression.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports a datasource, hald-small-score.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the file, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1751
+ "modelType": "datamining",
1752
+ "subcategory": "scoring",
1753
+ "features": [
1754
+ "datasources",
1755
+ "datasets",
1756
+ "actions"
1757
+ ],
1758
+ "dataSourceTypes": [
1759
+ "csv"
1760
+ ],
1761
+ "actions": [
1762
+ "predict"
1763
+ ],
1764
+ "tags": [
1765
+ "data-binding",
1766
+ "data-science",
1767
+ "machine-learning",
1768
+ "scoring"
1769
+ ]
1770
+ },
1771
+ {
1772
+ "filePath": "datamining/Scoring/PMMLTransformer.json",
1773
+ "modelName": "PMMLTransformer",
1774
+ "description": "This RASON model demonstrates how to transform a dataset containing new data using a previously fit, fitted model. In order to solve this model you must first run the Rescaling example model (Examples -- Data Science -- Transformation -- Rescaling.json) which generates and POSTs the fitted model used in this example, to the RASON server. In addition, this model also imports one datasource, hald-small-valid.txt, which can be downloaded by clicking the RASON Examples download icon. To attach the datasource to this example, click Choose Files (in the Properties pane on the right), browse to the location of the downloaded files, select the file, then click Open. Afterwards, click the POST icon to post the model with datafiles attached, then click the down arrow next to the Play icon and select Solve.",
1775
+ "modelType": "datamining",
1776
+ "subcategory": "scoring",
1777
+ "features": [
1778
+ "datasources",
1779
+ "datasets",
1780
+ "actions"
1781
+ ],
1782
+ "dataSourceTypes": [
1783
+ "csv"
1784
+ ],
1785
+ "actions": [
1786
+ "transform"
1787
+ ],
1788
+ "tags": [
1789
+ "data-binding",
1790
+ "data-science",
1791
+ "machine-learning",
1792
+ "scoring"
1793
+ ]
1794
+ },
1795
+ {
1796
+ "filePath": "datamining/Simulation/LinearRegressionSimulation.json",
1797
+ "modelName": "mlr-sim",
1798
+ "description": "Linear Regression RASON Model with Synthetic Data Generation: The Synthetic Data Generation feature allows users to generate synthetic data by automated Metalog probability distribution selection and parameter fitting, Rank Correlation or Copula fitting, and random sampling. This can be beneficial when the actual training data is limited or when the data owner is unwilling to release the actual, full dataset but agrees to supply a limited copy or a synthetic version that statistically resembles the properties of the actual dataset.",
1799
+ "modelType": "datamining",
1800
+ "subcategory": "simulation",
1801
+ "features": [
1802
+ "datasources",
1803
+ "datasets",
1804
+ "estimator",
1805
+ "actions"
1806
+ ],
1807
+ "algorithmType": "regression",
1808
+ "algorithm": "linearRegression",
1809
+ "dataSourceTypes": [
1810
+ "csv"
1811
+ ],
1812
+ "actions": [
1813
+ "fit",
1814
+ "predict"
1815
+ ],
1816
+ "tags": [
1817
+ "data-binding",
1818
+ "data-science",
1819
+ "linearRegression",
1820
+ "machine-learning",
1821
+ "regression",
1822
+ "simulation"
1823
+ ]
1824
+ },
1825
+ {
1826
+ "filePath": "datamining/Simulation/pmml-risk-scoring.json",
1827
+ "modelName": "pmmlRiskScorer",
1828
+ "description": "Regression: Linear RASON model scoring from pmml and risk analysis. This example model first imports two datasources, a training partition and a file containing new data. Then each datasource is bound to a dataset. Afterwards a previously posted fitted model, linear-fitted, is used to score both datasets. The fitted model must first be POSTed to the RASON Server BEFORE this model can be POSTed. Download the fitted model by clicking the download icon above RASON Examples (on the ribbon). Then click the Open File icon (far left), browse to the downloaded files, and open the file, linear-fitted.xml. POST the fitted model by clicking the POST icon, cloud icon on the left of the ribbon.",
1829
+ "modelType": "datamining",
1830
+ "subcategory": "simulation",
1831
+ "features": [
1832
+ "datasources",
1833
+ "datasets",
1834
+ "actions"
1835
+ ],
1836
+ "dataSourceTypes": [
1837
+ "csv"
1838
+ ],
1839
+ "actions": [
1840
+ "predict"
1841
+ ],
1842
+ "tags": [
1843
+ "data-binding",
1844
+ "data-science",
1845
+ "machine-learning",
1846
+ "simulation"
1847
+ ]
1848
+ },
1849
+ {
1850
+ "filePath": "datamining/Simulation/SyntheticDataGeneration.json",
1851
+ "modelName": "syntheticDataGeneration",
1852
+ "description": "RASON model example of how to use Synthetic Data Generation: This example demonstrates the API of the SyntheticDataGenerator object in the RASON modeling language, using the process: fit and select distributions and correlations for all columns (variables) in the dataset and generate the synthetic data. The original/synthetic data can be further analyzed using 'summarization' functionality. See the Summarization example for more information (Examples - Data Science - Summarization).",
1853
+ "modelType": "datamining",
1854
+ "subcategory": "simulation",
1855
+ "features": [
1856
+ "datasources",
1857
+ "datasets",
1858
+ "actions"
1859
+ ],
1860
+ "dataSourceTypes": [
1861
+ "csv"
1862
+ ],
1863
+ "actions": [
1864
+ "transform"
1865
+ ],
1866
+ "tags": [
1867
+ "data-binding",
1868
+ "data-science",
1869
+ "machine-learning",
1870
+ "simulation"
1871
+ ]
1872
+ },
1873
+ {
1874
+ "filePath": "datamining/Summarizer/Summarization.json",
1875
+ "modelName": "summarization",
1876
+ "description": "This RASON model example calls summarization to calculate statistics, percentiles and six sigma metrics for the dataset.",
1877
+ "modelType": "datamining",
1878
+ "subcategory": "summarization",
1879
+ "features": [
1880
+ "datasources",
1881
+ "datasets",
1882
+ "actions"
1883
+ ],
1884
+ "dataSourceTypes": [
1885
+ "csv"
1886
+ ],
1887
+ "actions": [
1888
+ "transform"
1889
+ ],
1890
+ "tags": [
1891
+ "data-binding",
1892
+ "data-science",
1893
+ "machine-learning",
1894
+ "summarization"
1895
+ ]
1896
+ },
1897
+ {
1898
+ "filePath": "datamining/TextMining/LatentSemanticAnalysis.json",
1899
+ "modelName": "LatentSemanticAnalysis",
1900
+ "description": "RASON Example using Text Miner - Latent Semantic Anlaysis is a technique in natural language processing between a set of documents and their contained terms by generating a set of concepts related to the documents and terms.",
1901
+ "modelType": "datamining",
1902
+ "subcategory": "text-mining",
1903
+ "features": [
1904
+ "datasources",
1905
+ "datasets",
1906
+ "estimator",
1907
+ "actions"
1908
+ ],
1909
+ "algorithmType": "textMining",
1910
+ "algorithm": "latentSemanticAnalysis",
1911
+ "dataSourceTypes": [
1912
+ "csv"
1913
+ ],
1914
+ "actions": [
1915
+ "fit",
1916
+ "transform"
1917
+ ],
1918
+ "tags": [
1919
+ "data-binding",
1920
+ "data-science",
1921
+ "latentSemanticAnalysis",
1922
+ "machine-learning",
1923
+ "text-mining",
1924
+ "textMining"
1925
+ ]
1926
+ },
1927
+ {
1928
+ "filePath": "datamining/TextMining/TfIdf-FileData.json",
1929
+ "modelName": "Tfldf-FileData",
1930
+ "description": "Text Mining RASON example - TF-IDF: TF-IDF stands for Term Frequency Inverse Document Frequency of records. It can be defined as the calculation of how relevant a word in a series or corpus is to a text.",
1931
+ "modelType": "datamining",
1932
+ "subcategory": "text-mining",
1933
+ "features": [
1934
+ "datasources",
1935
+ "datasets",
1936
+ "estimator",
1937
+ "actions"
1938
+ ],
1939
+ "algorithmType": "textMining",
1940
+ "algorithm": "tfIdf",
1941
+ "dataSourceTypes": [
1942
+ "csv"
1943
+ ],
1944
+ "actions": [
1945
+ "fit",
1946
+ "transform"
1947
+ ],
1948
+ "tags": [
1949
+ "data-binding",
1950
+ "data-science",
1951
+ "machine-learning",
1952
+ "text-mining",
1953
+ "textMining",
1954
+ "tfIdf"
1955
+ ]
1956
+ },
1957
+ {
1958
+ "filePath": "datamining/TextMining/TfIdf-InlineData.json",
1959
+ "modelName": "Tfldf-InlineData",
1960
+ "description": "RASON Text Mining - TF-IDF example: TF-IDF stands for Term Frequency Inverse Document Frequency of records. It can be defined as the calculation of how relevant a word in a series or corpus is to a text. See the TFIDF-FileData example (Examples - Data Mining - Text Mining) to see an example where the text sample is imported from an outside data source.",
1961
+ "modelType": "datamining",
1962
+ "subcategory": "text-mining",
1963
+ "features": [
1964
+ "datasets",
1965
+ "estimator",
1966
+ "actions"
1967
+ ],
1968
+ "algorithmType": "textMining",
1969
+ "algorithm": "tfIdf",
1970
+ "actions": [
1971
+ "fit",
1972
+ "transform"
1973
+ ],
1974
+ "tags": [
1975
+ "data-science",
1976
+ "machine-learning",
1977
+ "text-mining",
1978
+ "textMining",
1979
+ "tfIdf"
1980
+ ]
1981
+ },
1982
+ {
1983
+ "filePath": "datamining/TimeSeries/AddHoltWinters.json",
1984
+ "modelName": "AddHoltWinters",
1985
+ "description": "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.",
1986
+ "modelType": "datamining",
1987
+ "subcategory": "time-series",
1988
+ "features": [
1989
+ "datasources",
1990
+ "datasets",
1991
+ "estimator",
1992
+ "actions"
1993
+ ],
1994
+ "algorithmType": "timeSeries",
1995
+ "algorithm": "addHoltWinters",
1996
+ "dataSourceTypes": [
1997
+ "csv",
1998
+ "xml",
1999
+ "json"
2000
+ ],
2001
+ "actions": [
2002
+ "fit",
2003
+ "transform",
2004
+ "forecast"
2005
+ ],
2006
+ "tags": [
2007
+ "addHoltWinters",
2008
+ "data-binding",
2009
+ "data-science",
2010
+ "machine-learning",
2011
+ "time-series",
2012
+ "timeSeries"
2013
+ ]
2014
+ },
2015
+ {
2016
+ "filePath": "datamining/TimeSeries/Arima.json",
2017
+ "modelName": "Arima",
2018
+ "description": "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.",
2019
+ "modelType": "datamining",
2020
+ "subcategory": "time-series",
2021
+ "features": [
2022
+ "datasources",
2023
+ "datasets",
2024
+ "estimator",
2025
+ "actions"
2026
+ ],
2027
+ "algorithmType": "timeSeries",
2028
+ "algorithm": "arima",
2029
+ "dataSourceTypes": [
2030
+ "csv"
2031
+ ],
2032
+ "actions": [
2033
+ "fit",
2034
+ "transform",
2035
+ "forecast"
2036
+ ],
2037
+ "tags": [
2038
+ "arima",
2039
+ "data-binding",
2040
+ "data-science",
2041
+ "machine-learning",
2042
+ "time-series",
2043
+ "timeSeries"
2044
+ ]
2045
+ },
2046
+ {
2047
+ "filePath": "datamining/TimeSeries/DoubleExponential.json",
2048
+ "modelName": "DoubleExponential",
2049
+ "description": "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.",
2050
+ "modelType": "datamining",
2051
+ "subcategory": "time-series",
2052
+ "features": [
2053
+ "datasources",
2054
+ "datasets",
2055
+ "estimator",
2056
+ "actions"
2057
+ ],
2058
+ "algorithmType": "timeSeries",
2059
+ "algorithm": "doubleExponential",
2060
+ "dataSourceTypes": [
2061
+ "csv"
2062
+ ],
2063
+ "actions": [
2064
+ "fit",
2065
+ "transform",
2066
+ "forecast"
2067
+ ],
2068
+ "tags": [
2069
+ "data-binding",
2070
+ "data-science",
2071
+ "doubleExponential",
2072
+ "machine-learning",
2073
+ "time-series",
2074
+ "timeSeries"
2075
+ ]
2076
+ },
2077
+ {
2078
+ "filePath": "datamining/TimeSeries/Exponential.json",
2079
+ "modelName": "Exponential",
2080
+ "description": "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.",
2081
+ "modelType": "datamining",
2082
+ "subcategory": "time-series",
2083
+ "features": [
2084
+ "datasources",
2085
+ "datasets",
2086
+ "estimator",
2087
+ "actions"
2088
+ ],
2089
+ "algorithmType": "timeSeries",
2090
+ "algorithm": "exponential",
2091
+ "dataSourceTypes": [
2092
+ "csv"
2093
+ ],
2094
+ "actions": [
2095
+ "fit",
2096
+ "transform",
2097
+ "forecast"
2098
+ ],
2099
+ "tags": [
2100
+ "data-binding",
2101
+ "data-science",
2102
+ "exponential",
2103
+ "machine-learning",
2104
+ "time-series",
2105
+ "timeSeries"
2106
+ ]
2107
+ },
2108
+ {
2109
+ "filePath": "datamining/TimeSeries/LagAnalysis.json",
2110
+ "modelName": "LagAnalysis",
2111
+ "description": "RASON Example Model - Arima Lag Analysis Time Series RASON Example: This model imports an outside data source, binds the datasource to a dataset, creates a lag analysis time series estimator, then uses the estimator to generate a lag analysis forecast. To download the datasource, close.txt, click 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.",
2112
+ "modelType": "datamining",
2113
+ "subcategory": "time-series",
2114
+ "features": [
2115
+ "datasources",
2116
+ "datasets",
2117
+ "estimator",
2118
+ "actions"
2119
+ ],
2120
+ "algorithmType": "timeSeries",
2121
+ "algorithm": "lagAnalysis",
2122
+ "dataSourceTypes": [
2123
+ "csv"
2124
+ ],
2125
+ "actions": [
2126
+ "forecast"
2127
+ ],
2128
+ "tags": [
2129
+ "data-binding",
2130
+ "data-science",
2131
+ "lagAnalysis",
2132
+ "machine-learning",
2133
+ "time-series",
2134
+ "timeSeries"
2135
+ ]
2136
+ },
2137
+ {
2138
+ "filePath": "datamining/TimeSeries/MovingAverage.json",
2139
+ "modelName": "MovingAverage",
2140
+ "description": "Moving-Average Smoothing RASON Example that fits a model to data, imported from an outside file, Airpass.txt. This dataset includes two columns, month and passengers, recording the number of airline passengers from Jan 1949 to Dec 1960. This file may 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.",
2141
+ "modelType": "datamining",
2142
+ "subcategory": "time-series",
2143
+ "features": [
2144
+ "datasources",
2145
+ "datasets",
2146
+ "estimator",
2147
+ "actions"
2148
+ ],
2149
+ "algorithmType": "timeSeries",
2150
+ "algorithm": "movingAverage",
2151
+ "dataSourceTypes": [
2152
+ "csv"
2153
+ ],
2154
+ "actions": [
2155
+ "fit",
2156
+ "transform",
2157
+ "forecast"
2158
+ ],
2159
+ "tags": [
2160
+ "data-binding",
2161
+ "data-science",
2162
+ "machine-learning",
2163
+ "movingAverage",
2164
+ "time-series",
2165
+ "timeSeries"
2166
+ ]
2167
+ },
2168
+ {
2169
+ "filePath": "datamining/TimeSeries/MulHoltWinters.json",
2170
+ "modelName": "MulHoltWinters",
2171
+ "description": "Multiplicative Holt- Winters Smoothing RASON Example that fits a model to data, imported from an outside file, Airpass.txt. This time series dataset includes two columns, month and passengers, recording the number of airline passengers from Jan 1949 to Dec 1960. This file may 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.",
2172
+ "modelType": "datamining",
2173
+ "subcategory": "time-series",
2174
+ "features": [
2175
+ "datasources",
2176
+ "datasets",
2177
+ "estimator",
2178
+ "actions"
2179
+ ],
2180
+ "algorithmType": "timeSeries",
2181
+ "algorithm": "mulHoltWinters",
2182
+ "dataSourceTypes": [
2183
+ "csv"
2184
+ ],
2185
+ "actions": [
2186
+ "fit",
2187
+ "transform",
2188
+ "forecast"
2189
+ ],
2190
+ "tags": [
2191
+ "data-binding",
2192
+ "data-science",
2193
+ "machine-learning",
2194
+ "mulHoltWinters",
2195
+ "time-series",
2196
+ "timeSeries"
2197
+ ]
2198
+ },
2199
+ {
2200
+ "filePath": "datamining/TimeSeries/NoTrendHoltWinters.json",
2201
+ "modelName": "NoTrendHoltWinters",
2202
+ "description": "RASON No Trend Holt - Winters Smoothing Example that fits a model to data, imported from an outside file, Airpass.txt. This time series dataset includes two columns, month and passengers, recording the number of airline passengers from Jan 1949 to Dec 1960. This file may 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.",
2203
+ "modelType": "datamining",
2204
+ "subcategory": "time-series",
2205
+ "features": [
2206
+ "datasources",
2207
+ "datasets",
2208
+ "estimator",
2209
+ "actions"
2210
+ ],
2211
+ "algorithmType": "timeSeries",
2212
+ "algorithm": "noTrendHoltWinters",
2213
+ "dataSourceTypes": [
2214
+ "csv"
2215
+ ],
2216
+ "actions": [
2217
+ "fit",
2218
+ "transform",
2219
+ "forecast"
2220
+ ],
2221
+ "tags": [
2222
+ "data-binding",
2223
+ "data-science",
2224
+ "machine-learning",
2225
+ "noTrendHoltWinters",
2226
+ "time-series",
2227
+ "timeSeries"
2228
+ ]
2229
+ },
2230
+ {
2231
+ "filePath": "datamining/Transformation/Binning.json",
2232
+ "modelName": "Binning",
2233
+ "description": "Transformation RASON model example that performs binning on an imported data source. This datasource 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 Binning.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.",
2234
+ "modelType": "datamining",
2235
+ "subcategory": "transformation",
2236
+ "features": [
2237
+ "datasources",
2238
+ "datasets",
2239
+ "estimator",
2240
+ "actions"
2241
+ ],
2242
+ "algorithmType": "transformation",
2243
+ "algorithm": "binning",
2244
+ "dataSourceTypes": [
2245
+ "csv"
2246
+ ],
2247
+ "actions": [
2248
+ "fit",
2249
+ "transform"
2250
+ ],
2251
+ "tags": [
2252
+ "binning",
2253
+ "data-binding",
2254
+ "data-science",
2255
+ "machine-learning",
2256
+ "transformation"
2257
+ ]
2258
+ },
2259
+ {
2260
+ "filePath": "datamining/Transformation/CanonicalVariateAnalysis.json",
2261
+ "modelName": "CanonicalVariateAnalysis",
2262
+ "description": "Transformation RASON model example that performs canonical variate analysis on an imported data source. This datasource 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 iris.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.",
2263
+ "modelType": "datamining",
2264
+ "subcategory": "transformation",
2265
+ "features": [
2266
+ "datasources",
2267
+ "datasets",
2268
+ "estimator",
2269
+ "actions"
2270
+ ],
2271
+ "algorithmType": "transformation",
2272
+ "algorithm": "canonicalVariateAnalysis",
2273
+ "dataSourceTypes": [
2274
+ "csv"
2275
+ ],
2276
+ "actions": [
2277
+ "fit",
2278
+ "transform"
2279
+ ],
2280
+ "tags": [
2281
+ "canonicalVariateAnalysis",
2282
+ "data-binding",
2283
+ "data-science",
2284
+ "machine-learning",
2285
+ "transformation"
2286
+ ]
2287
+ },
2288
+ {
2289
+ "filePath": "datamining/Transformation/CategoryReduction.json",
2290
+ "modelName": "CategoryReduction",
2291
+ "description": "Transformation RASON model example that performs category reduction on an imported data source. This datasource 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 hald-small.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.",
2292
+ "modelType": "datamining",
2293
+ "subcategory": "transformation",
2294
+ "features": [
2295
+ "datasources",
2296
+ "datasets",
2297
+ "actions"
2298
+ ],
2299
+ "dataSourceTypes": [
2300
+ "csv"
2301
+ ],
2302
+ "actions": [
2303
+ "fit",
2304
+ "transform"
2305
+ ],
2306
+ "tags": [
2307
+ "data-binding",
2308
+ "data-science",
2309
+ "machine-learning",
2310
+ "transformation"
2311
+ ]
2312
+ },
2313
+ {
2314
+ "filePath": "datamining/Transformation/Factorization.json",
2315
+ "modelName": "Factorization",
2316
+ "description": "Transformation RASON model example that performs factorization (category scores in Analytic Solver Data Mining) on an imported data source. This datasource 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 hald-small.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.",
2317
+ "modelType": "datamining",
2318
+ "subcategory": "transformation",
2319
+ "features": [
2320
+ "datasources",
2321
+ "datasets",
2322
+ "estimator",
2323
+ "actions"
2324
+ ],
2325
+ "algorithmType": "transformation",
2326
+ "algorithm": "factorization",
2327
+ "dataSourceTypes": [
2328
+ "csv"
2329
+ ],
2330
+ "actions": [
2331
+ "fit",
2332
+ "transform"
2333
+ ],
2334
+ "tags": [
2335
+ "data-binding",
2336
+ "data-science",
2337
+ "factorization",
2338
+ "machine-learning",
2339
+ "transformation"
2340
+ ]
2341
+ },
2342
+ {
2343
+ "filePath": "datamining/Transformation/MissingDataHandling.json",
2344
+ "modelName": "MissingDataHandling",
2345
+ "description": "Transformation RASON model example that performs imputation (or missing data handling). 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.",
2346
+ "modelType": "datamining",
2347
+ "subcategory": "transformation",
2348
+ "features": [
2349
+ "datasets",
2350
+ "estimator",
2351
+ "actions"
2352
+ ],
2353
+ "algorithmType": "transformation",
2354
+ "algorithm": "imputation",
2355
+ "actions": [
2356
+ "fit",
2357
+ "transform"
2358
+ ],
2359
+ "tags": [
2360
+ "data-science",
2361
+ "imputation",
2362
+ "machine-learning",
2363
+ "transformation"
2364
+ ]
2365
+ },
2366
+ {
2367
+ "filePath": "datamining/Transformation/OneHotEncoding-DatainFile.json",
2368
+ "modelName": "OneHotEncodingFileData",
2369
+ "description": "Transformation RASON model example that performs one-hot encoding (Create Dummies in Analytic Solver). This example uses an outside data source, hald-small.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 hald-small.txt and click Open. 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.",
2370
+ "modelType": "datamining",
2371
+ "subcategory": "transformation",
2372
+ "features": [
2373
+ "datasources",
2374
+ "datasets",
2375
+ "estimator",
2376
+ "actions"
2377
+ ],
2378
+ "algorithmType": "transformation",
2379
+ "algorithm": "oneHotEncoding",
2380
+ "dataSourceTypes": [
2381
+ "csv"
2382
+ ],
2383
+ "actions": [
2384
+ "fit",
2385
+ "transform"
2386
+ ],
2387
+ "tags": [
2388
+ "data-binding",
2389
+ "data-science",
2390
+ "machine-learning",
2391
+ "oneHotEncoding",
2392
+ "transformation"
2393
+ ]
2394
+ },
2395
+ {
2396
+ "filePath": "datamining/Transformation/OneHotEncoding-DataInline.json",
2397
+ "modelName": "OneHotEncodingInlineData",
2398
+ "description": "Transformation RASON model example that performs one-hot encoding (Create Dummies in Analytic Solver). In this example, the data is supplied inline. 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.",
2399
+ "modelType": "datamining",
2400
+ "subcategory": "transformation",
2401
+ "features": [
2402
+ "datasets",
2403
+ "estimator",
2404
+ "actions"
2405
+ ],
2406
+ "algorithmType": "transformation",
2407
+ "algorithm": "oneHotEncoding",
2408
+ "actions": [
2409
+ "fit",
2410
+ "transform"
2411
+ ],
2412
+ "tags": [
2413
+ "data-science",
2414
+ "machine-learning",
2415
+ "oneHotEncoding",
2416
+ "transformation"
2417
+ ]
2418
+ },
2419
+ {
2420
+ "filePath": "datamining/Transformation/Partitioning.json",
2421
+ "modelName": "Partitioning",
2422
+ "description": "Transformation RASON model example that performs partitioning. This example uses an outside data source, hald-small-binary.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 hald-small-binary.txt and click Open. 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.",
2423
+ "modelType": "datamining",
2424
+ "subcategory": "transformation",
2425
+ "features": [
2426
+ "datasources",
2427
+ "datasets",
2428
+ "actions"
2429
+ ],
2430
+ "dataSourceTypes": [
2431
+ "csv"
2432
+ ],
2433
+ "actions": [
2434
+ "transform"
2435
+ ],
2436
+ "tags": [
2437
+ "data-binding",
2438
+ "data-science",
2439
+ "machine-learning",
2440
+ "transformation"
2441
+ ]
2442
+ },
2443
+ {
2444
+ "filePath": "datamining/Transformation/Partitioning-DF.json",
2445
+ "modelName": "PartitioningDF",
2446
+ "description": "transformation: partitioning",
2447
+ "modelType": "datamining",
2448
+ "subcategory": "transformation",
2449
+ "features": [
2450
+ "datasources",
2451
+ "datasets",
2452
+ "actions"
2453
+ ],
2454
+ "dataSourceTypes": [
2455
+ "csv"
2456
+ ],
2457
+ "actions": [
2458
+ "transform"
2459
+ ],
2460
+ "tags": [
2461
+ "data-binding",
2462
+ "data-science",
2463
+ "machine-learning",
2464
+ "transformation"
2465
+ ]
2466
+ },
2467
+ {
2468
+ "filePath": "datamining/Transformation/PartitioningWithOversampling.json",
2469
+ "modelName": "PartitioningWithOversampling",
2470
+ "description": "Transformation RASON model example that performs partitioning with oversampling. The difference between this oversampling example and the PartitionWithOversamplingDF example is that this example does not return the partitions as dataframes. This example uses an outside data source, hald-small-binary.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 hald-small-binary.txt and click Open. 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.",
2471
+ "modelType": "datamining",
2472
+ "subcategory": "transformation",
2473
+ "features": [
2474
+ "datasources",
2475
+ "datasets",
2476
+ "actions"
2477
+ ],
2478
+ "dataSourceTypes": [
2479
+ "csv"
2480
+ ],
2481
+ "actions": [
2482
+ "transform"
2483
+ ],
2484
+ "tags": [
2485
+ "data-binding",
2486
+ "data-science",
2487
+ "machine-learning",
2488
+ "transformation"
2489
+ ]
2490
+ },
2491
+ {
2492
+ "filePath": "datamining/Transformation/PartitioningWithOversampling-DF.json",
2493
+ "modelName": "PartitioningWithOversamplingDF",
2494
+ "description": "Transformation RASON model example that performs partitioning with oversampling. The difference between this oversampling example and the PartitionWithOversampling example is that this example returns the partitions as dataframes. This example uses an outside data source, hald-small-binary.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 hald-small-binary.txt and click Open. 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.",
2495
+ "modelType": "datamining",
2496
+ "subcategory": "transformation",
2497
+ "features": [
2498
+ "datasources",
2499
+ "datasets",
2500
+ "actions"
2501
+ ],
2502
+ "dataSourceTypes": [
2503
+ "csv"
2504
+ ],
2505
+ "actions": [
2506
+ "transform"
2507
+ ],
2508
+ "tags": [
2509
+ "data-binding",
2510
+ "data-science",
2511
+ "machine-learning",
2512
+ "transformation"
2513
+ ]
2514
+ },
2515
+ {
2516
+ "filePath": "datamining/Transformation/PrincipalComponentsAnalysis.json",
2517
+ "modelName": "PrincipalComponentsAnalysis",
2518
+ "description": "Transformation RASON model example that performs principal components analysis. This example uses an outside data source, irisfacto.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 irisfacto.txt and click Open. 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.",
2519
+ "modelType": "datamining",
2520
+ "subcategory": "transformation",
2521
+ "features": [
2522
+ "datasources",
2523
+ "datasets",
2524
+ "estimator",
2525
+ "actions"
2526
+ ],
2527
+ "algorithmType": "transformation",
2528
+ "algorithm": "principalComponentAnalysis",
2529
+ "dataSourceTypes": [
2530
+ "csv"
2531
+ ],
2532
+ "actions": [
2533
+ "fit",
2534
+ "transform"
2535
+ ],
2536
+ "tags": [
2537
+ "data-binding",
2538
+ "data-science",
2539
+ "machine-learning",
2540
+ "principalComponentAnalysis",
2541
+ "transformation"
2542
+ ]
2543
+ },
2544
+ {
2545
+ "filePath": "datamining/Transformation/Rescaling.json",
2546
+ "modelName": "Rescaling",
2547
+ "description": "Transformation RASON model example that performs rescaling. This example uses an outside data source, hald-small-train.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 hald-small-train and click Open. 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.",
2548
+ "modelType": "datamining",
2549
+ "subcategory": "transformation",
2550
+ "features": [
2551
+ "datasources",
2552
+ "datasets",
2553
+ "estimator",
2554
+ "actions"
2555
+ ],
2556
+ "algorithmType": "transformation",
2557
+ "algorithm": "rescaling",
2558
+ "dataSourceTypes": [
2559
+ "csv"
2560
+ ],
2561
+ "actions": [
2562
+ "fit",
2563
+ "transform"
2564
+ ],
2565
+ "tags": [
2566
+ "data-binding",
2567
+ "data-science",
2568
+ "machine-learning",
2569
+ "rescaling",
2570
+ "transformation"
2571
+ ]
2572
+ },
2573
+ {
2574
+ "filePath": "datamining/Transformation/Sampling.json",
2575
+ "modelName": "Sampling",
2576
+ "description": "Transformation RASON model example that samples a dataset. This example uses an outside data source, hald-small-binary.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 hald-small-binary.txt and click Open. 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.",
2577
+ "modelType": "datamining",
2578
+ "subcategory": "transformation",
2579
+ "features": [
2580
+ "datasources",
2581
+ "datasets",
2582
+ "actions"
2583
+ ],
2584
+ "dataSourceTypes": [
2585
+ "csv"
2586
+ ],
2587
+ "actions": [
2588
+ "transform"
2589
+ ],
2590
+ "tags": [
2591
+ "data-binding",
2592
+ "data-science",
2593
+ "machine-learning",
2594
+ "transformation"
2595
+ ]
2596
+ },
2597
+ {
2598
+ "filePath": "datamining/Transformation/StratifiedSampling.json",
2599
+ "modelName": "StratifiedSampling",
2600
+ "description": "Transformation RASON model example that performs stratefied sampling on a dataset. When statefied sampling is used, the population is first divided into groups of similar items. These groups are called strata. Each stratum, in turn, is sampled using simple random sampling. These samples are then combined to form a stratified random sample. This example uses an outside data source, hald-small-binary.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 hald-small-binary.txt and click Open. 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.",
2601
+ "modelType": "datamining",
2602
+ "subcategory": "transformation",
2603
+ "features": [
2604
+ "datasources",
2605
+ "datasets",
2606
+ "actions"
2607
+ ],
2608
+ "dataSourceTypes": [
2609
+ "csv"
2610
+ ],
2611
+ "actions": [
2612
+ "transform"
2613
+ ],
2614
+ "tags": [
2615
+ "data-binding",
2616
+ "data-science",
2617
+ "machine-learning",
2618
+ "transformation"
2619
+ ]
2620
+ },
2621
+ {
2622
+ "filePath": "datamining/Transformation/PartitionTimeSeries.json",
2623
+ "modelName": "TimeSeriesPartitioning",
2624
+ "description": "Transformation RASON model example that performs partitioning on a time series dataset. This example uses an outside data source, 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. 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.",
2625
+ "modelType": "datamining",
2626
+ "subcategory": "transformation",
2627
+ "features": [
2628
+ "datasources",
2629
+ "datasets",
2630
+ "actions"
2631
+ ],
2632
+ "dataSourceTypes": [
2633
+ "csv"
2634
+ ],
2635
+ "actions": [
2636
+ "transform"
2637
+ ],
2638
+ "tags": [
2639
+ "data-binding",
2640
+ "data-science",
2641
+ "machine-learning",
2642
+ "transformation"
2643
+ ]
2644
+ },
2645
+ {
2646
+ "filePath": "flow/SQLServerTransform.json",
2647
+ "modelName": "dmMLRSQLWorkflow",
2648
+ "description": "Example illustrates how SQL server commands may be utilized to manipulate data within a decision flow. This example includes 5 stages. RASON enables users to easily define multi-stage 'decision flows', where a stage can perform a SQL operation, apply a data transformation, train a machine learning model, apply it to score new data, run a simulation, solve a mathematical optimization problem, or evaluate one or more linked decision tables. Results are passed between stages in a rich, standard 'Indexed Data Frame' form. RASON uses an in-memory SQL database engine, plus 'smart evaluation' to run only the stages that have new input data, to execute these multi-stage flows as efficiently as possible. This decision flow uses two outside data source which can be downloaded by clicking RASON Example files icon. Then click Choose Files, from the Properties pane, browse to the location of the downloaded files, and click OK. To solve this model, first POST the model to the RASON server by clicking the POST icon, cloud icon, on the Editor ribbon. Then solve by clicking the down arrow next to the play icon, and clicking Solve.",
2649
+ "modelType": "flow",
2650
+ "subcategory": null,
2651
+ "features": [],
2652
+ "stageCount": 5,
2653
+ "tags": [
2654
+ "decision-flow",
2655
+ "multi-stage",
2656
+ "pipeline"
2657
+ ]
2658
+ },
2659
+ {
2660
+ "filePath": "flow/dm-calc-pipeline.json",
2661
+ "modelName": "ds-calc-workflow",
2662
+ "description": "This decision flow contains three stages. In the first stage, mlr-sim-stage, a dataset is imported and partitioned, then a Linear Regression model is fit to the training partition.. The second stage, scoringStage, uses the fitted model from stage 1 to score a new dataset. The third stage, decisionStage, accepts the newly scored data as an input to a decision table. The two imported datasets are loan_applicants_training.txt and loan_applicant_new.txt. Both can be downloaded by clicking the download icon on the Editor ribbon. To attach both datasets to this model, click Choose Files from the Properties pane, then browse to the location of the downloaded files and click Open. Then POST the model to the RASON server using the Post icon and to solve, click the down arrow next to the play icon and select Solve.",
2663
+ "modelType": "flow",
2664
+ "subcategory": null,
2665
+ "features": [],
2666
+ "stageCount": 3,
2667
+ "tags": [
2668
+ "decision-flow",
2669
+ "multi-stage",
2670
+ "pipeline"
2671
+ ]
2672
+ },
2673
+ {
2674
+ "filePath": "flow/dm-pipeline-simulation.json",
2675
+ "modelName": "ds-risk-analysis-flow",
2676
+ "description": "",
2677
+ "modelType": "flow",
2678
+ "subcategory": null,
2679
+ "features": [],
2680
+ "stageCount": 2,
2681
+ "tags": [
2682
+ "decision-flow",
2683
+ "multi-stage",
2684
+ "pipeline"
2685
+ ]
2686
+ },
2687
+ {
2688
+ "filePath": "flow/opt-sim-pipeline.json",
2689
+ "modelName": "optSimWorkflow",
2690
+ "description": "This decision flow is made up of two stages, an optimization stage and a simulation stage. \nThe optimization stage solves an optimization model that selects an optimal mix of capital improvement projects. Afterwards, the simulation stage then runs a simulation. To view the contents of the decision flow, click the Show RASON Editor icon on the top right of the Editor grid. \nTo run, simply POST the model by clicking the POST icon (cloud icon), then solve the flow by clicking the down arrow next to the play button icon and select Solve. Click Help on the RASON ribbon for more information on posting and solving RASON Decision Flows.",
2691
+ "modelType": "flow",
2692
+ "subcategory": null,
2693
+ "features": [],
2694
+ "psiFunctions": [
2695
+ "PsiTriangular",
2696
+ "PsiBinomial"
2697
+ ],
2698
+ "stageCount": 2,
2699
+ "tags": [
2700
+ "decision-flow",
2701
+ "multi-stage",
2702
+ "pipeline",
2703
+ "probability-distribution"
2704
+ ]
2705
+ },
2706
+ {
2707
+ "filePath": "flow/sim-dm-pipeline.json",
2708
+ "modelName": "simDMWorkflow",
2709
+ "description": "Simulation/DataScience workflow example: This decision flow includes two stages: a simulation stage (simStage) and a data science stage (kMeansStage). The first stage runs a simulation, then uses the simulation trial results as data for a clustering algorithm in the 2nd stage. To solve the decision flow, you must first POST the example by clicking the POST icon (cloud icon) on the Editor tab ribbon. Afterwards, click the down arrow next to the play icon and click Solve. This example uses no outside data source files. ",
2710
+ "modelType": "flow",
2711
+ "subcategory": null,
2712
+ "features": [],
2713
+ "psiFunctions": [
2714
+ "PsiLogNormal"
2715
+ ],
2716
+ "stageCount": 2,
2717
+ "tags": [
2718
+ "decision-flow",
2719
+ "multi-stage",
2720
+ "pipeline",
2721
+ "probability-distribution"
2722
+ ]
2723
+ },
2724
+ {
2725
+ "filePath": "flow/sim-sim-pipeline.json",
2726
+ "modelName": "simsimWorkflow",
2727
+ "description": "This decision flow contains two stages. Each stage runs a simulation. The first stage runs a simulation, then second stage uses the mean value from the 1st stage as an input to a formula in the 2nd stage. To see the contents of the decision flow, click the Show RASON model editor icon at the top, right of the grid. To solve, first POST the decision flow by clicking the POST (cloud) icon, then solve by clicking the down arrow next to the play icon and select Solve. For more information on posting and solving decision flows, click the Help tab.",
2728
+ "modelType": "flow",
2729
+ "subcategory": null,
2730
+ "features": [],
2731
+ "psiFunctions": [
2732
+ "PsiTriangular",
2733
+ "PsiBinomial"
2734
+ ],
2735
+ "stageCount": 2,
2736
+ "tags": [
2737
+ "decision-flow",
2738
+ "multi-stage",
2739
+ "pipeline",
2740
+ "probability-distribution"
2741
+ ]
2742
+ },
2743
+ {
2744
+ "filePath": "rason-features/BoxLambdaExamples/BoxFunOptimize.json",
2745
+ "modelName": "BoxFunOptimize",
2746
+ "description": "This Box Function calculates the distance function based on 4 inputs x1, x2 and y1, y2. A Box function is a custom, reusable function. This example solves an optimization model using the funDistance box function to calculate the distance between a proposed airline hub and six regional airports.",
2747
+ "modelType": "optimization",
2748
+ "subcategory": null,
2749
+ "features": [
2750
+ "variables",
2751
+ "constraints",
2752
+ "objective",
2753
+ "formulas",
2754
+ "data",
2755
+ "engine-settings",
2756
+ "box-functions"
2757
+ ],
2758
+ "isFeatureDemo": true,
2759
+ "variableCount": 2,
2760
+ "constraintCount": 6,
2761
+ "objectiveType": "min",
2762
+ "tags": [
2763
+ "box-function",
2764
+ "grg nonlinear",
2765
+ "min",
2766
+ "optimization"
2767
+ ]
2768
+ },
2769
+ {
2770
+ "filePath": "rason-features/BoxLambdaExamples/LambdaFunOptimize.json",
2771
+ "modelName": "LambdaFunOptimize",
2772
+ "description": "In this example, a LAMBDA Excel functon is used to create a custom, reusable function that can be called mulitiple times to calculate the distance between a proposed airline hub and 6 regional airports. Notice that the decision varaibles, constraints and the objective function have not changed from the original AirlineHub example under Examples - Optimization - Nonlinear.",
2773
+ "modelType": "optimization",
2774
+ "subcategory": null,
2775
+ "features": [
2776
+ "variables",
2777
+ "constraints",
2778
+ "objective",
2779
+ "formulas",
2780
+ "data",
2781
+ "engine-settings",
2782
+ "box-functions"
2783
+ ],
2784
+ "isFeatureDemo": true,
2785
+ "variableCount": 2,
2786
+ "constraintCount": 6,
2787
+ "objectiveType": "min",
2788
+ "tags": [
2789
+ "box-function",
2790
+ "grg nonlinear",
2791
+ "min",
2792
+ "optimization"
2793
+ ]
2794
+ },
2795
+ {
2796
+ "filePath": "rason-features/ReferenceGuide/RGFirehouseLocation.json",
2797
+ "modelName": "RGFirehouseLocation",
2798
+ "description": "RASON Conic Optimization Example: Example of solving a nonlinear Optimization Model with Cone Constraints. The goal of this example is to find a location, given by x and y coordinates, of a proposed firehouse that minimizes the maximum distance between the firehouse and six cities in the region.",
2799
+ "modelType": "optimization",
2800
+ "subcategory": null,
2801
+ "features": [
2802
+ "variables",
2803
+ "constraints",
2804
+ "objective",
2805
+ "engine-settings"
2806
+ ],
2807
+ "isFeatureDemo": true,
2808
+ "variableCount": 3,
2809
+ "constraintCount": 6,
2810
+ "objectiveType": "minimize",
2811
+ "tags": [
2812
+ "grg nonlinear",
2813
+ "minimize",
2814
+ "optimization"
2815
+ ]
2816
+ },
2817
+ {
2818
+ "filePath": "rason-features/ReferenceGuide/RGFirehouseLocationConic.json",
2819
+ "modelName": "RGFirehouseLocationConic",
2820
+ "description": "RASON Conic Optimization Example: Example of solving a Conic Optimization Model. The goal of this example is the same for the RGFirehouseLocation example, to find a location, given by x and y coordinates, of a proposed firehouse that minimizes the maximum distance between the firehouse and six cities in the region. The difference between this example and the RGFirehouseLocation example is that this example replaces the 6 nonlinear constraints (calculating the distances betwen the proposed firehouse location and each city) with a 6 conic constraints. Since the model is now a conic optimization model, the SOCP Barrier engine can be used. ",
2821
+ "modelType": "optimization",
2822
+ "subcategory": null,
2823
+ "features": [
2824
+ "variables",
2825
+ "constraints",
2826
+ "objective",
2827
+ "data",
2828
+ "engine-settings"
2829
+ ],
2830
+ "isFeatureDemo": true,
2831
+ "variableCount": 6,
2832
+ "constraintCount": 9,
2833
+ "objectiveType": "minimize",
2834
+ "tags": [
2835
+ "minimize",
2836
+ "optimization",
2837
+ "socp barrier"
2838
+ ]
2839
+ },
2840
+ {
2841
+ "filePath": "rason-features/ReferenceGuide/RGProductMixCsv1.json",
2842
+ "modelName": "RGProductMixCsv1",
2843
+ "description": "RASON Conic Optimization Example: Illustrates binding to a CSV File. In this example, initial variable values are first imported from the CSV file ResultVarsInit.txt and, after the model is solved, the final variable values are saved back to that same CSV file. The final constraint values are saved to ResultFcns.txt and the final objective value is saved to ResultObj.txt. Both ResultFcns.txt and ResultObj.txt will be created once the model is solved. (Click Download RASON Examples icon to download all source files. To attach the files to the example, click Choose Files, navigate to the location of the saved files, select ProductMixParts.txt, ProductMixInventory.txt, ProductMixProfits.txt and ResultVarsInit.txt and click Open. Then POST the model by clicking the POST icon, then solve the model by clicking the down arrow next to the Play icon and selecting Solve.",
2844
+ "modelType": "optimization",
2845
+ "subcategory": null,
2846
+ "features": [
2847
+ "variables",
2848
+ "constraints",
2849
+ "objective",
2850
+ "formulas",
2851
+ "data",
2852
+ "datasources"
2853
+ ],
2854
+ "isFeatureDemo": true,
2855
+ "variableCount": 1,
2856
+ "constraintCount": 1,
2857
+ "objectiveType": "maximize",
2858
+ "tags": [
2859
+ "data-binding",
2860
+ "maximize",
2861
+ "optimization"
2862
+ ]
2863
+ },
2864
+ {
2865
+ "filePath": "rason-features/ReferenceGuide/RGProductMixExcel11.json",
2866
+ "modelName": "RGProductMixExcel11",
2867
+ "description": "RASON Conic Optimization Example: Example illustrates how to bind to an Excel sheet: In this example, data is imported from an Excel file. To perform the same steps when importing/exporting to an Excel file, you need to specify the cell address containing the dimensions to be imported and/or the cells to which the results should be exported. In this example, the vars_data data source is again importing initial decision variable values and then exporting the final decision variable values to the same Excel workbook. See Data Sources within the RASON Reference Guide for more information. (Click Help tab to download.) ",
2868
+ "modelType": "optimization",
2869
+ "subcategory": null,
2870
+ "features": [
2871
+ "variables",
2872
+ "constraints",
2873
+ "objective",
2874
+ "formulas",
2875
+ "data",
2876
+ "datasources"
2877
+ ],
2878
+ "isFeatureDemo": true,
2879
+ "variableCount": 1,
2880
+ "constraintCount": 1,
2881
+ "objectiveType": "maximize",
2882
+ "tags": [
2883
+ "data-binding",
2884
+ "maximize",
2885
+ "optimization"
2886
+ ]
2887
+ },
2888
+ {
2889
+ "filePath": "rason-features/ReferenceGuide/RGProductMixSQL11.json",
2890
+ "modelName": "RGProductMixSQL11",
2891
+ "description": "RASON Conic Optimization Example that uses SQL table binding: This example illustrates how to import and export data from an odbc database, specifically a Microsoft Access database. See the Named Data Connections within the RASON User Guide for more information on how to create a named data connection where you can maintain your data access credentials in a secure Azure 'vault' rather than passing them in the connection property.",
2892
+ "modelType": "optimization",
2893
+ "subcategory": null,
2894
+ "features": [
2895
+ "variables",
2896
+ "constraints",
2897
+ "objective",
2898
+ "formulas",
2899
+ "data",
2900
+ "datasources"
2901
+ ],
2902
+ "isFeatureDemo": true,
2903
+ "variableCount": 1,
2904
+ "constraintCount": 1,
2905
+ "objectiveType": "maximize",
2906
+ "tags": [
2907
+ "data-binding",
2908
+ "maximize",
2909
+ "optimization"
2910
+ ]
2911
+ },
2912
+ {
2913
+ "filePath": "rason-features/UserGuide/UGAirlineHubCSV.json",
2914
+ "modelName": "UGAirlineHubCSV",
2915
+ "description": "RASON Distance Minimization Nonlinear Optimization Example - This example is used in the Introduction chapter within the RASON User Guide (downloadable from the Help tab) to illustrate RASON's ability to import data from an outside source. Many realistic models use large tables of data, often drawn from multiple data fields or databases. The goal of this example is to find a location of an airline hub serving several regional airports. The location of the hub should be as close to equidistant to each airport served, as possible. In this example the datasources section imports a CSV file containing a list of coordinates for the regional airports. AirlineHubData.csv contains three columns: 'cities', containing the city name, dx and dy, containing the x and y coordinates of each airport. Our list of city coordinates is located in a CSV file, however, our data could also have been located in an ODBC database or an Excel file. Click Help - RASON Subscriptions -- Data Connections to see how to setup a secure data connection in RASON. To download AirlineHubData.csv, click Download RASON example data from the ribbon. To attach the file to the example, click Choose Files (on the Properties pane), browse to the location of the downloaded files, select AirlineHubData.csv and click Open. Then click POST (upload icon on ribbon) to post the model to the RASON Server. Finally, click the down arrow next the Play icon and click Solve to solve the model. The x and y values in the final solution will be the x and y coordinates of the proprosed airline hub.",
2916
+ "modelType": "optimization",
2917
+ "subcategory": null,
2918
+ "features": [
2919
+ "variables",
2920
+ "constraints",
2921
+ "objective",
2922
+ "data",
2923
+ "datasources",
2924
+ "engine-settings"
2925
+ ],
2926
+ "isFeatureDemo": true,
2927
+ "variableCount": 3,
2928
+ "constraintCount": 1,
2929
+ "objectiveType": "minimize",
2930
+ "tags": [
2931
+ "data-binding",
2932
+ "grg nonlinear",
2933
+ "minimize",
2934
+ "optimization"
2935
+ ]
2936
+ },
2937
+ {
2938
+ "filePath": "rason-features/UserGuide/UGProductMix1.json",
2939
+ "modelName": "UGProductMix1_BasicLinearModel",
2940
+ "description": "RASON Product Mix Example: UGProductMix1 Example - This example is discussed in the Defining Your Optimization Model chapter. Assume a company manufatures TVs, stereos and speakers, using a common parts inventory of chassis, LOCD screens, speakers power supplies and various internal electronics. Parts are in limited supply. This model works well for the business situation initially described, with exactly three products and five types of parts but it's not very flexible. What if more products were added and more parts were required? In the next example UGProductMix2Example, the model will be generalized so it can handle different numbers of products and parts.",
2941
+ "modelType": "optimization",
2942
+ "subcategory": null,
2943
+ "features": [
2944
+ "variables",
2945
+ "constraints",
2946
+ "objective"
2947
+ ],
2948
+ "isFeatureDemo": true,
2949
+ "variableCount": 1,
2950
+ "constraintCount": 5,
2951
+ "objectiveType": "maximize",
2952
+ "tags": [
2953
+ "maximize",
2954
+ "optimization"
2955
+ ]
2956
+ },
2957
+ {
2958
+ "filePath": "rason-features/UserGuide/UGProductMix2.json",
2959
+ "modelName": "UGProductMix2_ImprovedLinearModel",
2960
+ "description": "RASON Product Mix Example: UGProductMix2 Example - This example is discussed in the Defining Your Optimization chapter within the RASON User Guide. See 'The Improve Model' section within the chapter. One way to make the original product mix model (UGProductMix1Example) more flexible is to use RASON's built-in functions that operate on all the elements of an array at once, treating it as a vector or matrix. With this version of the model, if the number of parts or products are increased or decreased, you will need to adjust the size of your arrays, but no changes will be needed for the constraints formula which can sometimes be the hardest part of the model to define.",
2961
+ "modelType": "optimization",
2962
+ "subcategory": null,
2963
+ "features": [
2964
+ "variables",
2965
+ "constraints",
2966
+ "objective",
2967
+ "data"
2968
+ ],
2969
+ "isFeatureDemo": true,
2970
+ "variableCount": 1,
2971
+ "constraintCount": 1,
2972
+ "objectiveType": "maximize",
2973
+ "tags": [
2974
+ "maximize",
2975
+ "optimization"
2976
+ ]
2977
+ },
2978
+ {
2979
+ "filePath": "rason-features/UserGuide/UGProductMixTab1.json",
2980
+ "modelName": "UGProductMixTable1",
2981
+ "description": "RASON Product Mix Example: Arrays in the RASON Modeling language are limited to 2-dimensions. If you require an array containing more than 2-dimensions, a table may be created. There are many advantages to using tables: 1. Tables may hold more than 2 dimensions, 2. A table result may be used in an indexed array formula, 3. A table can be sparse while an array is dense, 4. The evaluation of a table is less expensive (time consuming) than the evaluation of an array with more than 2 dimensions. In this example, the matrix above has been specified in line (within the RASON model) as the parts table. This table contains 15 elements and is indexed using two dimensions: part and prod. Note that this table is DENSE, meaning that zero values have been supplied as well as non-zero values. See the next example, UGProductMixTable2 to see an example of a SPARSE table, meaning only non-zero values are supplied. (To open this full example, and any example referenced in this guide, click the down array under RASON examples -- Examples discussed in the RASON User Guide.)",
2982
+ "modelType": "optimization",
2983
+ "subcategory": null,
2984
+ "features": [
2985
+ "variables",
2986
+ "constraints",
2987
+ "objective",
2988
+ "data"
2989
+ ],
2990
+ "isFeatureDemo": true,
2991
+ "variableCount": 1,
2992
+ "constraintCount": 5,
2993
+ "objectiveType": "maximize",
2994
+ "tags": [
2995
+ "maximize",
2996
+ "optimization"
2997
+ ]
2998
+ },
2999
+ {
3000
+ "filePath": "rason-features/UserGuide/UGProductMixTab2.json",
3001
+ "modelName": "UGProductMixTable2",
3002
+ "description": "RASON Product Mix Example: This example solves the same model as UGProductMixTable1, with two modifications. 1. Instead of passing a DENSE table, in which both zero and non-zero elements are passed in the parts table, this example passes a SPARSE table where only non-zero elements are passed. 2. This example model illustrates how to use an index set to dimension a table. RASON uses index sets exclusively to dimension tables and arrays.",
3003
+ "modelType": "optimization",
3004
+ "subcategory": null,
3005
+ "features": [
3006
+ "variables",
3007
+ "constraints",
3008
+ "objective",
3009
+ "formulas",
3010
+ "data"
3011
+ ],
3012
+ "isFeatureDemo": true,
3013
+ "variableCount": 1,
3014
+ "constraintCount": 1,
3015
+ "objectiveType": "maximize",
3016
+ "tags": [
3017
+ "maximize",
3018
+ "optimization"
3019
+ ]
3020
+ },
3021
+ {
3022
+ "filePath": "rason-features/UserGuide/UGProductMixTab3.json",
3023
+ "modelName": "UGProductMixTable3",
3024
+ "description": "RASON Product Mix Example: This example solves the same model as UGProductMixTable1, except that this example passes a SPARSE table (as in UGProductMixTable2) and uses the sortIndexCols property within the parts table.",
3025
+ "modelType": "optimization",
3026
+ "subcategory": null,
3027
+ "features": [
3028
+ "variables",
3029
+ "constraints",
3030
+ "objective",
3031
+ "data"
3032
+ ],
3033
+ "isFeatureDemo": true,
3034
+ "variableCount": 1,
3035
+ "constraintCount": 1,
3036
+ "objectiveType": "maximize",
3037
+ "tags": [
3038
+ "maximize",
3039
+ "optimization"
3040
+ ]
3041
+ },
3042
+ {
3043
+ "filePath": "rason-features/UserGuide/UGProductMixTab4.json",
3044
+ "modelName": "UGProductMixTable4",
3045
+ "description": "RASON Product Mix Example: Solves the same model as UGProductMixTable3. However, in this example, the inventory values are also entered as a table. Also, the constraints are entered in standard form, i.e. sumproduct(x,parts)-inventory <= 0",
3046
+ "modelType": "optimization",
3047
+ "subcategory": null,
3048
+ "features": [
3049
+ "variables",
3050
+ "constraints",
3051
+ "objective",
3052
+ "data"
3053
+ ],
3054
+ "isFeatureDemo": true,
3055
+ "variableCount": 1,
3056
+ "constraintCount": 1,
3057
+ "objectiveType": "maximize",
3058
+ "tags": [
3059
+ "maximize",
3060
+ "optimization"
3061
+ ]
3062
+ },
3063
+ {
3064
+ "filePath": "rason-features/UserGuide/UGProductMixTab5.json",
3065
+ "modelName": "UGProductMixTable5",
3066
+ "description": "RASON Product Mix Example: This example solves the same model as UGProductMixTable1 through 4. In this example, 1. the inventory values are supplied as upper bounds to each of the parts constraints, 2. The final values of the profits table will be included in the result, 3.Each constraint is entered separately.",
3067
+ "modelType": "optimization",
3068
+ "subcategory": null,
3069
+ "features": [
3070
+ "variables",
3071
+ "constraints",
3072
+ "objective",
3073
+ "data"
3074
+ ],
3075
+ "isFeatureDemo": true,
3076
+ "variableCount": 1,
3077
+ "constraintCount": 5,
3078
+ "objectiveType": "maximize",
3079
+ "tags": [
3080
+ "maximize",
3081
+ "optimization"
3082
+ ]
3083
+ },
3084
+ {
3085
+ "filePath": "rason-features/UserGuide/UGProjectSelect0.json",
3086
+ "modelName": "UGProjectSelect0Example",
3087
+ "description": "RASON Example - Simulation Optimization: This example is discussed in the chapter, Defining Your Stochastic Optimization Model, within the RASON User Guide, downloadable from the Help tab. This example is a capital budgeting problem, where the projects being considered for funding have uncertain future cash flows. In this example, simulation optimization is used to find a solution using the Evolutionary Engine. Assume eight different capital projects are proposed for funding in your company. Each one has a known initial investment. Each project has a 90% chance of success, and if a project succeeds, it will have an uncertain (but positive) future cash flow. Funding all eight projects would require a total initial investment of $2.5 million, but our capital budget is only $1.5 million. Hence, we must choose a subset of the projects to fund that will maximize our expected total future cash flow, while ensuring that our total initial investment does not exceed our $1.5 million budget.",
3088
+ "modelType": "optimization",
3089
+ "subcategory": null,
3090
+ "features": [
3091
+ "variables",
3092
+ "constraints",
3093
+ "objective",
3094
+ "uncertain-variables",
3095
+ "formulas",
3096
+ "engine-settings"
3097
+ ],
3098
+ "isFeatureDemo": true,
3099
+ "psiFunctions": [
3100
+ "PsiTriangular",
3101
+ "PsiBinomial"
3102
+ ],
3103
+ "variableCount": 1,
3104
+ "constraintCount": 1,
3105
+ "objectiveType": "maximize",
3106
+ "tags": [
3107
+ "maximize",
3108
+ "monte-carlo",
3109
+ "optimization",
3110
+ "probability-distribution",
3111
+ "stochastic"
3112
+ ]
3113
+ },
3114
+ {
3115
+ "filePath": "rason-features/UserGuide/UGProjectSelect1.json",
3116
+ "modelName": "UGProjectSelect1Example",
3117
+ "description": "RASON Stochastic Optimization Example: This example is a Stochastic LP and is discussed in the chapter, Defining Your Stochastic Optimization Model, within the RASON User Guide (downloadable from the Help tab). The original model, UGProjectSelect0 (Examples -- Models discussed in User Guide -- UGProjectSelect0.json) is solved via Simulation Optimization. However, there are two additional methods besides simulation optimization that can solve Stochastic LPs, stochastic programming and robust optimization. For this model, we will choose a transformation to Stochastic Programming Deterministic Equivalent by replacing simulationOptimization: True with transformStochastic: deterministicEquivalent in modelSettings.",
3118
+ "modelType": "optimization",
3119
+ "subcategory": null,
3120
+ "features": [
3121
+ "variables",
3122
+ "constraints",
3123
+ "objective",
3124
+ "uncertain-variables",
3125
+ "formulas",
3126
+ "engine-settings"
3127
+ ],
3128
+ "isFeatureDemo": true,
3129
+ "psiFunctions": [
3130
+ "PsiBinomial",
3131
+ "PsiTriangular"
3132
+ ],
3133
+ "variableCount": 1,
3134
+ "constraintCount": 1,
3135
+ "objectiveType": "maximize",
3136
+ "tags": [
3137
+ "maximize",
3138
+ "monte-carlo",
3139
+ "optimization",
3140
+ "probability-distribution",
3141
+ "stochastic"
3142
+ ]
3143
+ },
3144
+ {
3145
+ "filePath": "rason-features/UserGuide/UGProjectSelect2.json",
3146
+ "modelName": "UGProjectSelect2Example",
3147
+ "description": "RASON Stochastic Optimization Model: Robust Counterpart: This example is a Stochastic LP. This example is not directly discussed in the Defining Your Stochastic Optimization Model. Rather, this example simply uses the 3rd and final method to solve a stochastic LP. Recall that UGProjectSelect0 solved via simulation optimization and UGProjectSelect1 solved via stochastic transformation using the deterministic method. This example uses the stochastic transformation using the robust counterpart method. To use robust counterpart, simply enter 'robustCounterpart' for 'transformStochastic' in 'modelSettings'. The remainder of the model remains unchanged from UGProjectSelect1.",
3148
+ "modelType": "optimization",
3149
+ "subcategory": null,
3150
+ "features": [
3151
+ "variables",
3152
+ "constraints",
3153
+ "objective",
3154
+ "uncertain-variables",
3155
+ "formulas",
3156
+ "engine-settings"
3157
+ ],
3158
+ "isFeatureDemo": true,
3159
+ "psiFunctions": [
3160
+ "PsiBinomial",
3161
+ "PsiTriangular"
3162
+ ],
3163
+ "variableCount": 1,
3164
+ "constraintCount": 1,
3165
+ "objectiveType": "maximize",
3166
+ "tags": [
3167
+ "maximize",
3168
+ "monte-carlo",
3169
+ "optimization",
3170
+ "probability-distribution",
3171
+ "stochastic"
3172
+ ]
3173
+ },
3174
+ {
3175
+ "filePath": "rason-features/UserGuide/UGYieldManagement3.json",
3176
+ "modelName": "UGYieldManagement3Example",
3177
+ "description": "RASON Simulation Optimization Model: Running multiple parameterized simulations in UGYieldManagement2, and examining the results has given us a good deal of information about the behavior of this simulation model. However, if we take just a few more steps we can answer the question, 'How many tickets should we sell to realize the maximum expected net revenue?' By changing 'sold' from a simulation parameter to a decision variable, we can setup a simulation optimization model. See the Defining Your Stochastic Optimization chapter within the RASON User Guide for a complete discussion of this example and also the previous examples UGYieldManagement 1 and 2.",
3178
+ "modelType": "optimization",
3179
+ "subcategory": null,
3180
+ "features": [
3181
+ "variables",
3182
+ "objective",
3183
+ "uncertain-variables",
3184
+ "formulas",
3185
+ "data",
3186
+ "engine-settings"
3187
+ ],
3188
+ "isFeatureDemo": true,
3189
+ "psiFunctions": [
3190
+ "PsiLogNormal"
3191
+ ],
3192
+ "variableCount": 1,
3193
+ "constraintCount": 0,
3194
+ "objectiveType": "maximize",
3195
+ "tags": [
3196
+ "evolutionary",
3197
+ "maximize",
3198
+ "monte-carlo",
3199
+ "optimization",
3200
+ "probability-distribution",
3201
+ "stochastic"
3202
+ ]
3203
+ },
3204
+ {
3205
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/ParallelArray.json",
3206
+ "modelName": "AirlineHub2Example",
3207
+ "description": "This example is identical to Airline Hub 2 RASON Nonlinear Optimization Example. This example showcases how to use an array to formulate multiple constraints at once.",
3208
+ "modelType": "optimization",
3209
+ "subcategory": "arrays",
3210
+ "features": [
3211
+ "variables",
3212
+ "constraints",
3213
+ "objective",
3214
+ "data"
3215
+ ],
3216
+ "isFeatureDemo": true,
3217
+ "variableCount": 3,
3218
+ "constraintCount": 1,
3219
+ "objectiveType": "minimize",
3220
+ "tags": [
3221
+ "arrays",
3222
+ "minimize",
3223
+ "optimization"
3224
+ ]
3225
+ },
3226
+ {
3227
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/indexedArray.json",
3228
+ "modelName": "indexedArray",
3229
+ "description": "Solves the product mix example problem. However, in this example, the constraints are created using a 'for' statement, an indexed array. For more information on this example, see RASON Examples -- Example Models Discussed in RASON User Guide -- UGProductMixTab4.json.",
3230
+ "modelType": "optimization",
3231
+ "subcategory": "arrays",
3232
+ "features": [
3233
+ "variables",
3234
+ "constraints",
3235
+ "objective",
3236
+ "data"
3237
+ ],
3238
+ "isFeatureDemo": true,
3239
+ "variableCount": 1,
3240
+ "constraintCount": 1,
3241
+ "objectiveType": "maximize",
3242
+ "tags": [
3243
+ "arrays",
3244
+ "maximize",
3245
+ "optimization"
3246
+ ]
3247
+ },
3248
+ {
3249
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/nonParallelArray.json",
3250
+ "modelName": "nonParallelArrayExample",
3251
+ "description": "This example is identical to the ProductMix4 .json example under RASON Examples-Optimization-LinearExamples. It is included here to showcase the non-parallel array 'num_used' in the 'constraints' section, below.",
3252
+ "modelType": "optimization",
3253
+ "subcategory": "arrays",
3254
+ "features": [
3255
+ "variables",
3256
+ "constraints",
3257
+ "objective",
3258
+ "data"
3259
+ ],
3260
+ "isFeatureDemo": true,
3261
+ "variableCount": 1,
3262
+ "constraintCount": 1,
3263
+ "objectiveType": "maximize",
3264
+ "tags": [
3265
+ "arrays",
3266
+ "maximize",
3267
+ "optimization"
3268
+ ]
3269
+ },
3270
+ {
3271
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/sumAggregateExample.json",
3272
+ "modelName": "sumAggregateLogistics",
3273
+ "description": "",
3274
+ "modelType": "optimization",
3275
+ "subcategory": "arrays",
3276
+ "features": [
3277
+ "variables",
3278
+ "constraints",
3279
+ "objective",
3280
+ "formulas",
3281
+ "data",
3282
+ "engine-settings"
3283
+ ],
3284
+ "isFeatureDemo": true,
3285
+ "variableCount": 3,
3286
+ "constraintCount": 3,
3287
+ "objectiveType": "min",
3288
+ "tags": [
3289
+ "arrays",
3290
+ "lp/quadratic",
3291
+ "min",
3292
+ "optimization"
3293
+ ]
3294
+ },
3295
+ {
3296
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/tsp.json",
3297
+ "modelName": "usingRecursiveFor",
3298
+ "description": "",
3299
+ "modelType": "optimization",
3300
+ "subcategory": "arrays",
3301
+ "features": [
3302
+ "variables",
3303
+ "objective",
3304
+ "formulas",
3305
+ "data",
3306
+ "datasources",
3307
+ "engine-settings"
3308
+ ],
3309
+ "isFeatureDemo": true,
3310
+ "variableCount": 1,
3311
+ "constraintCount": 0,
3312
+ "objectiveType": "min",
3313
+ "tags": [
3314
+ "arrays",
3315
+ "data-binding",
3316
+ "min",
3317
+ "nonlinear grg",
3318
+ "optimization"
3319
+ ]
3320
+ },
3321
+ {
3322
+ "filePath": "optimization/Conic/AirlineHubConic2.json",
3323
+ "modelName": "AirlineHubConic2Example",
3324
+ "description": "Airline Hub Conic 2 RASON Optimization Example: This model minimizes the distance between several regional airports and a proposed hub location. The difference between this example and the original AirlineHubConicExample is that this example uses vertical vectors. For a complete description of this model, see AirlineHubConic Example.",
3325
+ "modelType": "optimization",
3326
+ "subcategory": "conic",
3327
+ "features": [
3328
+ "variables",
3329
+ "constraints",
3330
+ "objective",
3331
+ "data",
3332
+ "engine-settings"
3333
+ ],
3334
+ "variableCount": 6,
3335
+ "constraintCount": 9,
3336
+ "objectiveType": "minimize",
3337
+ "tags": [
3338
+ "conic",
3339
+ "minimize",
3340
+ "optimization",
3341
+ "socp barrier"
3342
+ ]
3343
+ },
3344
+ {
3345
+ "filePath": "optimization/Conic/AirlineHubConic3.json",
3346
+ "modelName": "AirlineHubConic3Example",
3347
+ "description": "Airline Hub Conic 3 RASON Optimization Example: This model minimizes the distance between several regional airports and a proposed hub location. The difference between this example and the original AirlineHubConicExample is that this example uses horizontal vectors. For a complete description of this model, see AirlineHubConic Example.",
3348
+ "modelType": "optimization",
3349
+ "subcategory": "conic",
3350
+ "features": [
3351
+ "variables",
3352
+ "constraints",
3353
+ "objective",
3354
+ "data",
3355
+ "engine-settings"
3356
+ ],
3357
+ "variableCount": 6,
3358
+ "constraintCount": 9,
3359
+ "objectiveType": "minimize",
3360
+ "tags": [
3361
+ "conic",
3362
+ "minimize",
3363
+ "optimization",
3364
+ "socp barrier"
3365
+ ]
3366
+ },
3367
+ {
3368
+ "filePath": "optimization/Conic/AirlineHubConic4.json",
3369
+ "modelName": "AirlineHubConic4Example",
3370
+ "description": "Airline Hub Conic 4 RASON Optimization Example: This model minimizes the distance between several regional airports and a proposed hub location. The difference between this example and the original AirlineHubConicExample is that this example illustrates how to 'slice' an array. For a complete description of this model, see AirlineHubConic Example.",
3371
+ "modelType": "optimization",
3372
+ "subcategory": "conic",
3373
+ "features": [
3374
+ "variables",
3375
+ "constraints",
3376
+ "objective",
3377
+ "data",
3378
+ "engine-settings"
3379
+ ],
3380
+ "variableCount": 4,
3381
+ "constraintCount": 9,
3382
+ "objectiveType": "minimize",
3383
+ "tags": [
3384
+ "conic",
3385
+ "minimize",
3386
+ "optimization",
3387
+ "socp barrier"
3388
+ ]
3389
+ },
3390
+ {
3391
+ "filePath": "optimization/Conic/AirlineHubConic5.json",
3392
+ "modelName": "AirlineHubConic5Example",
3393
+ "description": "Airline Hub Conic 5 RASON Optimization Example: This model minimizes the distance between several regional airports and a proposed hub location. The difference between this example and the original AirlineHubConicExample is that this example illustrates how to 'slice' an array. For a complete description of this model, see AirlineHubConic Example.",
3394
+ "modelType": "optimization",
3395
+ "subcategory": "conic",
3396
+ "features": [
3397
+ "variables",
3398
+ "constraints",
3399
+ "objective",
3400
+ "data",
3401
+ "engine-settings"
3402
+ ],
3403
+ "variableCount": 4,
3404
+ "constraintCount": 9,
3405
+ "objectiveType": "minimize",
3406
+ "tags": [
3407
+ "conic",
3408
+ "minimize",
3409
+ "optimization",
3410
+ "socp barrier"
3411
+ ]
3412
+ },
3413
+ {
3414
+ "filePath": "optimization/Conic/AirlineHubConic.json",
3415
+ "modelName": "AirlineHubConicExample",
3416
+ "description": "Conic Constraint Optimization Example RASON Model: This model minimizes the distance between several regional airports and a proposed hub location. In the original AirlineHub models, found within the Nonlinear examples, the Pythagorean Theorem was used to calculate the distance of each city to the proposed airport hub location. Since this distance calculation was nonlinear, a nonlinear engine was required to solve the model, such as the Standard GRG Engine. In this example, however, we will use 6 conic constraints (one for each regional airline location) to calculate the distance between the airline hub and the regional airports. Removing the nonlinear functions and replacing them with conic constraints results in a SOCP Convex model which can be solved faster and more reliably with the SOCP engine.",
3417
+ "modelType": "optimization",
3418
+ "subcategory": "conic",
3419
+ "features": [
3420
+ "variables",
3421
+ "constraints",
3422
+ "objective",
3423
+ "data",
3424
+ "engine-settings"
3425
+ ],
3426
+ "variableCount": 6,
3427
+ "constraintCount": 9,
3428
+ "objectiveType": "minimize",
3429
+ "tags": [
3430
+ "conic",
3431
+ "minimize",
3432
+ "optimization",
3433
+ "socp barrier"
3434
+ ]
3435
+ },
3436
+ {
3437
+ "filePath": "optimization/DataBinding/ProductMixCsv4.json",
3438
+ "modelName": "ProductMixCSV4",
3439
+ "description": "This RASON model is used in the RASON User Guide to illustrate how to export a model to Power BI and Tableau. Click the Help tab, then scroll down to Creating Your Own Application. Notice that there is a mixture of syntaxes used in setting up each model section to showcase the flexibility of RASON Decision Services!",
3440
+ "modelType": "optimization",
3441
+ "subcategory": "data-binding",
3442
+ "features": [
3443
+ "variables",
3444
+ "constraints",
3445
+ "objective",
3446
+ "formulas",
3447
+ "data",
3448
+ "datasources"
3449
+ ],
3450
+ "variableCount": 6,
3451
+ "constraintCount": 1,
3452
+ "objectiveType": null,
3453
+ "tags": [
3454
+ "data-binding",
3455
+ "optimization"
3456
+ ]
3457
+ },
3458
+ {
3459
+ "filePath": "optimization/DataBinding/ProductMixCsv.json",
3460
+ "modelName": "ProductMixCsvExample",
3461
+ "description": "RASON model example of using CSV table binding: The product mix example is used to illustrate how to bind table elements to a data source. Recall that the product mix example finds the optimal number of products to produce in order to maximize the total profit.",
3462
+ "modelType": "optimization",
3463
+ "subcategory": "data-binding",
3464
+ "features": [
3465
+ "variables",
3466
+ "constraints",
3467
+ "objective",
3468
+ "formulas",
3469
+ "data",
3470
+ "datasources"
3471
+ ],
3472
+ "variableCount": 1,
3473
+ "constraintCount": 1,
3474
+ "objectiveType": "maximize",
3475
+ "tags": [
3476
+ "data-binding",
3477
+ "maximize",
3478
+ "optimization"
3479
+ ]
3480
+ },
3481
+ {
3482
+ "filePath": "optimization/DataBinding/ProductMixExcel11.json",
3483
+ "modelName": "ProductMixExcel11Example",
3484
+ "description": "RASON model example of using Excel table binding: Recall that the product mix example finds the optimal number of products (optimal product mix) a business should produce in order to maximize total profit, given present inventory levels. In this example, final variable and constraint values are exported back to the Excel file.",
3485
+ "modelType": "optimization",
3486
+ "subcategory": "data-binding",
3487
+ "features": [
3488
+ "variables",
3489
+ "constraints",
3490
+ "objective",
3491
+ "formulas",
3492
+ "data",
3493
+ "datasources"
3494
+ ],
3495
+ "variableCount": 7,
3496
+ "constraintCount": 1,
3497
+ "objectiveType": null,
3498
+ "tags": [
3499
+ "data-binding",
3500
+ "optimization"
3501
+ ]
3502
+ },
3503
+ {
3504
+ "filePath": "optimization/DataBinding/ProductMixExcel1.json",
3505
+ "modelName": "ProductMixExcel1Example",
3506
+ "description": "RASON model example of binding to an Excel table: Recall that the product mix example finds the optimal number of products a business should produce (optimal product mix) in order to maximize total profit, given present inventory levels",
3507
+ "modelType": "optimization",
3508
+ "subcategory": "data-binding",
3509
+ "features": [
3510
+ "variables",
3511
+ "constraints",
3512
+ "objective",
3513
+ "formulas",
3514
+ "data",
3515
+ "datasources"
3516
+ ],
3517
+ "variableCount": 1,
3518
+ "constraintCount": 1,
3519
+ "objectiveType": "maximize",
3520
+ "tags": [
3521
+ "data-binding",
3522
+ "maximize",
3523
+ "optimization"
3524
+ ]
3525
+ },
3526
+ {
3527
+ "filePath": "optimization/DataBinding/ProductMixExcel2.json",
3528
+ "modelName": "ProductMixExcel2Example",
3529
+ "description": "RASON model example of using Excel table binding with sorted indexCols: The only difference between this example and the earlier ProductMixExcel1 example is that this example uses sortIndexCols set to true. If the sortIndexCols (or sort) property is used, all indexCols will be sorted alphabetically. (Note: The properties sort and sortIndexCols perform the same function.) Otherwise, the table will be sorted as entered. In the example below, the order for prods will be: speaker, stereo, tv. While the order for parts will be: chas, cone, elec, psup, tube.",
3530
+ "modelType": "optimization",
3531
+ "subcategory": "data-binding",
3532
+ "features": [
3533
+ "variables",
3534
+ "constraints",
3535
+ "objective",
3536
+ "formulas",
3537
+ "data",
3538
+ "datasources"
3539
+ ],
3540
+ "variableCount": 1,
3541
+ "constraintCount": 1,
3542
+ "objectiveType": "maximize",
3543
+ "tags": [
3544
+ "data-binding",
3545
+ "maximize",
3546
+ "optimization"
3547
+ ]
3548
+ },
3549
+ {
3550
+ "filePath": "optimization/DataBinding/ProductMixExcel.json",
3551
+ "modelName": "ProductMixExcelExample",
3552
+ "description": "RASON model example of binding to an Excel data source: Recall that the product mix example finds the optimal number of products a business should produce in order to maximize total profit, given present inventory levels",
3553
+ "modelType": "optimization",
3554
+ "subcategory": "data-binding",
3555
+ "features": [
3556
+ "variables",
3557
+ "constraints",
3558
+ "objective",
3559
+ "data",
3560
+ "datasources"
3561
+ ],
3562
+ "variableCount": 1,
3563
+ "constraintCount": 1,
3564
+ "objectiveType": "maximize",
3565
+ "tags": [
3566
+ "data-binding",
3567
+ "maximize",
3568
+ "optimization"
3569
+ ]
3570
+ },
3571
+ {
3572
+ "filePath": "optimization/DataBinding/ProductMixTab.json",
3573
+ "modelName": "ProductMixTableInlineExample",
3574
+ "description": "RASON example model which uses inline tables: In this version of the Product Mix example, data has been entered into two tables: parts and profits.",
3575
+ "modelType": "optimization",
3576
+ "subcategory": "data-binding",
3577
+ "features": [
3578
+ "variables",
3579
+ "constraints",
3580
+ "objective",
3581
+ "data"
3582
+ ],
3583
+ "variableCount": 1,
3584
+ "constraintCount": 5,
3585
+ "objectiveType": "maximize",
3586
+ "tags": [
3587
+ "data-binding",
3588
+ "maximize",
3589
+ "optimization"
3590
+ ]
3591
+ },
3592
+ {
3593
+ "filePath": "optimization/DataBinding/ProductMixTab1.json",
3594
+ "modelName": "ProductMixTableSparseInlineExample",
3595
+ "description": "RASON model example of using sparse inline tables: In this version of Product Mix, only the nonzero elements of the parts table are passed. This is called a sparse table. No parts have been renamed in this example.",
3596
+ "modelType": "optimization",
3597
+ "subcategory": "data-binding",
3598
+ "features": [
3599
+ "variables",
3600
+ "constraints",
3601
+ "objective",
3602
+ "data"
3603
+ ],
3604
+ "variableCount": 1,
3605
+ "constraintCount": 5,
3606
+ "objectiveType": "maximize",
3607
+ "tags": [
3608
+ "data-binding",
3609
+ "maximize",
3610
+ "optimization"
3611
+ ]
3612
+ },
3613
+ {
3614
+ "filePath": "optimization/DataBinding/ProductMixTab2.json",
3615
+ "modelName": "ProductMixTableSparsePivotExample",
3616
+ "description": "RASON model example of using sparse inline tables (pivoting): The difference between this model and ProductMixTab1 is that in this example, the indexSets section is used to create two index sets, part and prod. With the addition of these two indices, a pivot table can be utilized to setup the constraints in a more sustainable manner.",
3617
+ "modelType": "optimization",
3618
+ "subcategory": "data-binding",
3619
+ "features": [
3620
+ "variables",
3621
+ "constraints",
3622
+ "objective",
3623
+ "formulas",
3624
+ "data"
3625
+ ],
3626
+ "variableCount": 1,
3627
+ "constraintCount": 1,
3628
+ "objectiveType": "maximize",
3629
+ "tags": [
3630
+ "data-binding",
3631
+ "maximize",
3632
+ "optimization"
3633
+ ]
3634
+ },
3635
+ {
3636
+ "filePath": "optimization/Linear/Inventory.json",
3637
+ "modelName": "inventoryExample",
3638
+ "description": "RASON Inventory Planning Optimization Example: Example of non-smooth transformation. You are tasked with minimizing the inventory ordering and holding costs while ensuring there is enough inventory on hand to meet demand over a number of time periods, as well as with maintaining minimum inventory levels for each product. This inventory planning model was originally designed for linear programming, but to properly minimize holding costs, the objective was formulated using IF functions. When the modelSettings property 'transformNonSmooth' is set to True, RASON Decision Services will automatically transform this difficult, hard to solve nonsmooth model into a simple linear mixed integer model.",
3639
+ "modelType": "optimization",
3640
+ "subcategory": "linear",
3641
+ "features": [
3642
+ "variables",
3643
+ "constraints",
3644
+ "objective",
3645
+ "formulas"
3646
+ ],
3647
+ "variableCount": 9,
3648
+ "constraintCount": 12,
3649
+ "objectiveType": "minimize",
3650
+ "tags": [
3651
+ "linear",
3652
+ "minimize",
3653
+ "optimization"
3654
+ ]
3655
+ },
3656
+ {
3657
+ "filePath": "optimization/Linear/Matop.json",
3658
+ "modelName": "matopExample",
3659
+ "description": "RASON example model uses Frontline's MATOP function to solve a famous and difficult fixed-charge transportation optimization model. The optimal objective = 3712. In a fixed charge constraint, a binary variable is forced to 1 if the corresponding continuous variable is nonzero. In other words, if X >0 then Y = 1. From here the binary variable may be multiplied by a constant value to model a penalty or charge.",
3660
+ "modelType": "optimization",
3661
+ "subcategory": "linear",
3662
+ "features": [
3663
+ "variables",
3664
+ "constraints",
3665
+ "objective",
3666
+ "formulas",
3667
+ "data"
3668
+ ],
3669
+ "variableCount": 2,
3670
+ "constraintCount": 3,
3671
+ "objectiveType": "minimize",
3672
+ "tags": [
3673
+ "linear",
3674
+ "minimize",
3675
+ "optimization"
3676
+ ]
3677
+ },
3678
+ {
3679
+ "filePath": "optimization/Linear/ProductMix2.json",
3680
+ "modelName": "productMix2Example",
3681
+ "description": "Product Mix RASON Optimization Example 2: Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit. In this version of the Product Mix model, the data section now contains 2 arrays, rather than 6: D17:F17 - the profit per unit of each [TV, Stereo, Speaker] produced and D11:F15, a double array, - the number of each product required to produce each [TV, Stereo, Speaker]. In the first example, 6 separate arrays were used to supply the constraint coefficient values, or the number of parts required to produce each product. In this example, all values are passed in 1 array. The variables, constraints and objective sections all remain unchanged.",
3682
+ "modelType": "optimization",
3683
+ "subcategory": "linear",
3684
+ "features": [
3685
+ "variables",
3686
+ "constraints",
3687
+ "objective",
3688
+ "data"
3689
+ ],
3690
+ "variableCount": 1,
3691
+ "constraintCount": 5,
3692
+ "objectiveType": "maximize",
3693
+ "tags": [
3694
+ "linear",
3695
+ "maximize",
3696
+ "optimization"
3697
+ ]
3698
+ },
3699
+ {
3700
+ "filePath": "optimization/Linear/ProductMix3.json",
3701
+ "modelName": "productMix3Example",
3702
+ "description": "Product Mix RASON Optimization Example 3: Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit. In this version of the Product Mix model, sensitivity information is returned in the result. This information lets the user know which constraints are binding or non binding. If a constraint is binding, the left hand side of the constraint is equal to its upper or lower bound or both, in the case of an equality. This means that in order to improve the objective, the constraint(s) must be relaxed or moved away from the upper or lower bound. The Dual Value, or Shadow Price, is the change in the objective value of the optimal solution when the constraint is relaxed by one unit within the allowable increase or decrease.",
3703
+ "modelType": "optimization",
3704
+ "subcategory": "linear",
3705
+ "features": [
3706
+ "variables",
3707
+ "constraints",
3708
+ "objective",
3709
+ "data"
3710
+ ],
3711
+ "variableCount": 1,
3712
+ "constraintCount": 1,
3713
+ "objectiveType": "maximize",
3714
+ "tags": [
3715
+ "linear",
3716
+ "maximize",
3717
+ "optimization"
3718
+ ]
3719
+ },
3720
+ {
3721
+ "filePath": "optimization/Linear/ProductMix4.json",
3722
+ "modelName": "productMix4Example",
3723
+ "description": "Product Mix RASON Optimization Example 4: This version of the Product Mix example replaces the Excel range array names with improved readable names such as profits, parts, inventory, etc. Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit. ",
3724
+ "modelType": "optimization",
3725
+ "subcategory": "linear",
3726
+ "features": [
3727
+ "variables",
3728
+ "constraints",
3729
+ "objective",
3730
+ "data"
3731
+ ],
3732
+ "variableCount": 1,
3733
+ "constraintCount": 1,
3734
+ "objectiveType": "maximize",
3735
+ "tags": [
3736
+ "linear",
3737
+ "maximize",
3738
+ "optimization"
3739
+ ]
3740
+ },
3741
+ {
3742
+ "filePath": "optimization/Linear/ProductMixCsv1.json",
3743
+ "modelName": "productMixCsv1Example",
3744
+ "description": "Product Mix CSV 1 RASON Optimization Example: This example uses CSV table binding to read parameter values and save the final results. Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit.",
3745
+ "modelType": "optimization",
3746
+ "subcategory": "linear",
3747
+ "features": [
3748
+ "variables",
3749
+ "constraints",
3750
+ "objective",
3751
+ "formulas",
3752
+ "data",
3753
+ "datasources"
3754
+ ],
3755
+ "variableCount": 5,
3756
+ "constraintCount": 1,
3757
+ "objectiveType": null,
3758
+ "tags": [
3759
+ "data-binding",
3760
+ "linear",
3761
+ "optimization"
3762
+ ]
3763
+ },
3764
+ {
3765
+ "filePath": "optimization/Linear/ProductMixCsv2.json",
3766
+ "modelName": "productMixCSV2Example",
3767
+ "description": "Product Mix CSV2 RASON Optimization Example: This example uses CSV table binding to import parameter values and export (save) results. Notice that in this example, the x array within Variables, includes the indexCols property. Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit.",
3768
+ "modelType": "optimization",
3769
+ "subcategory": "linear",
3770
+ "features": [
3771
+ "variables",
3772
+ "constraints",
3773
+ "objective",
3774
+ "formulas",
3775
+ "data",
3776
+ "datasources"
3777
+ ],
3778
+ "variableCount": 6,
3779
+ "constraintCount": 1,
3780
+ "objectiveType": null,
3781
+ "tags": [
3782
+ "data-binding",
3783
+ "linear",
3784
+ "optimization"
3785
+ ]
3786
+ },
3787
+ {
3788
+ "filePath": "optimization/Linear/ProductMix.json",
3789
+ "modelName": "productMixExample",
3790
+ "description": "Product Mix RASON Optimization Example: Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit. Assume a company manufactures TVs, stereos and speakers, using a common parts inventory of power supplies, speaker cones, etc. Parts are in limited supply. Determine the most profitable mix of products to produce. See our Tutorial Online for step-by-step instructions on formulating this linear programming model. This RASON model was converted from a model created in Excel using Analytic Solver.",
3791
+ "modelType": "optimization",
3792
+ "subcategory": "linear",
3793
+ "features": [
3794
+ "variables",
3795
+ "constraints",
3796
+ "objective",
3797
+ "data"
3798
+ ],
3799
+ "variableCount": 1,
3800
+ "constraintCount": 5,
3801
+ "objectiveType": "maximize",
3802
+ "tags": [
3803
+ "linear",
3804
+ "maximize",
3805
+ "optimization"
3806
+ ]
3807
+ },
3808
+ {
3809
+ "filePath": "optimization/Linear/ProductMixSQL11.json",
3810
+ "modelName": "productMixSQL11Example",
3811
+ "description": "Product Mix SQL RASON Optimization Example: This example illustrates how to import data from an SQL table using the Product Mix example. Recall that the Product Mix example finds the optimal product mix that a company should manufacture in order to maximize gross profit.",
3812
+ "modelType": "optimization",
3813
+ "subcategory": "linear",
3814
+ "features": [
3815
+ "variables",
3816
+ "constraints",
3817
+ "objective",
3818
+ "formulas",
3819
+ "data",
3820
+ "datasources"
3821
+ ],
3822
+ "variableCount": 5,
3823
+ "constraintCount": 1,
3824
+ "objectiveType": null,
3825
+ "tags": [
3826
+ "data-binding",
3827
+ "linear",
3828
+ "optimization"
3829
+ ]
3830
+ },
3831
+ {
3832
+ "filePath": "optimization/Linear/Rowop.json",
3833
+ "modelName": "rowopExample",
3834
+ "description": "RASON example uses Frontline's ROWOP function to solve a famous and difficult fixed-charge transportation optimization model. The optimal objective = 3712. In a fixed charge constraint, a binary variable is forced to 1 if the corresponding continuous variable is nonzero. In other words, if X >0 then Y = 1. From here the binary variable may be multiplied by a constant value to model a penalty or charge.",
3835
+ "modelType": "optimization",
3836
+ "subcategory": "linear",
3837
+ "features": [
3838
+ "variables",
3839
+ "constraints",
3840
+ "objective",
3841
+ "formulas",
3842
+ "data"
3843
+ ],
3844
+ "variableCount": 2,
3845
+ "constraintCount": 3,
3846
+ "objectiveType": "minimize",
3847
+ "tags": [
3848
+ "linear",
3849
+ "minimize",
3850
+ "optimization"
3851
+ ]
3852
+ },
3853
+ {
3854
+ "filePath": "rason-features/Arrays_Loops_Tables/ArrayExamples/Loops/ProductMix5.json",
3855
+ "modelName": "ProductMix5",
3856
+ "description": "Solves the product mix example using constraints defined with a for statement and indexed arrays.",
3857
+ "modelType": "optimization",
3858
+ "subcategory": "loops",
3859
+ "features": [
3860
+ "variables",
3861
+ "constraints",
3862
+ "objective",
3863
+ "data"
3864
+ ],
3865
+ "isFeatureDemo": true,
3866
+ "variableCount": 1,
3867
+ "constraintCount": 1,
3868
+ "objectiveType": "maximize",
3869
+ "tags": [
3870
+ "loops",
3871
+ "maximize",
3872
+ "optimization"
3873
+ ]
3874
+ },
3875
+ {
3876
+ "filePath": "optimization/NonSmooth/Inventory2.json",
3877
+ "modelName": "Inventory2Example",
3878
+ "description": "Inventory2 Nonsmooth RASON Optimization Example: This example uses the same model as used in the Inventory example (under Examples -- Optimization -- Linear Optimizations) without the use of automatic transformation. Recall that this example minimizes the inventory ordering and holding costs while ensuring there is enough inventory on hand to meet demand over a number of time periods, as well as with maintaining minimum inventory levels for each product. As a result the nonsmooth engine, the Optquest Engine, will be used to solve the model. Note that nonsmooth models are much harder to solve and typically result in a slower solve time. Set transformationNonSmooth to True, below, to automatically transform the model into a linear model with a faster solve time.",
3879
+ "modelType": "optimization",
3880
+ "subcategory": "non-smooth",
3881
+ "features": [
3882
+ "variables",
3883
+ "constraints",
3884
+ "objective",
3885
+ "formulas"
3886
+ ],
3887
+ "variableCount": 3,
3888
+ "constraintCount": 10,
3889
+ "objectiveType": null,
3890
+ "tags": [
3891
+ "non-smooth",
3892
+ "optimization"
3893
+ ]
3894
+ },
3895
+ {
3896
+ "filePath": "optimization/NonLinear/AirlineHub2.json",
3897
+ "modelName": "AirlineHub2Example",
3898
+ "description": "Airline Hub 2 RASON Nonlinear Optimization Example: Same problem as AirlineHubExample but this example uses block constraints. (Recall that this RASON example finds the minimum distance between a proposed airline hub location and several regional cities.) This model still finds the location that minimizes the overall distance to 6 different airports",
3899
+ "modelType": "optimization",
3900
+ "subcategory": "nonlinear",
3901
+ "features": [
3902
+ "variables",
3903
+ "constraints",
3904
+ "objective",
3905
+ "data"
3906
+ ],
3907
+ "variableCount": 3,
3908
+ "constraintCount": 1,
3909
+ "objectiveType": "minimize",
3910
+ "tags": [
3911
+ "minimize",
3912
+ "nonlinear",
3913
+ "optimization"
3914
+ ]
3915
+ },
3916
+ {
3917
+ "filePath": "optimization/NonLinear/AirlineHub3.json",
3918
+ "modelName": "AirlineHub3Example",
3919
+ "description": "Airline Hub 3 RASON Nonlinear Optimization Example: Same problem as AirlineHubExample and AirlineHub2Example but this example specifies the dimension directly for the data and constraint arrays. (Recall that these two RASON examples find the minimum distance between a proposed airline hub location and several regional cities.) This model still finds the location that minimizes the overall distance to 6 different airports",
3920
+ "modelType": "optimization",
3921
+ "subcategory": "nonlinear",
3922
+ "features": [
3923
+ "variables",
3924
+ "constraints",
3925
+ "objective",
3926
+ "data"
3927
+ ],
3928
+ "variableCount": 3,
3929
+ "constraintCount": 1,
3930
+ "objectiveType": "minimize",
3931
+ "tags": [
3932
+ "minimize",
3933
+ "nonlinear",
3934
+ "optimization"
3935
+ ]
3936
+ },
3937
+ {
3938
+ "filePath": "optimization/NonLinear/AirlineHub.json",
3939
+ "modelName": "AirlineHubExample",
3940
+ "description": "Airline Hub Nonlinear RASON Optimization Example: Finds the hub location that minimizes the overall distance to 6 different airports. This example uses the distance formula to determine the distance between the projected hub and each of the 6 airports, SQRT((x1 - x0) + (y1 - y0)) The objective returns the coordinates of the prospective location.",
3941
+ "modelType": "optimization",
3942
+ "subcategory": "nonlinear",
3943
+ "features": [
3944
+ "variables",
3945
+ "constraints",
3946
+ "objective",
3947
+ "engine-settings"
3948
+ ],
3949
+ "variableCount": 3,
3950
+ "constraintCount": 6,
3951
+ "objectiveType": "minimize",
3952
+ "tags": [
3953
+ "grg nonlinear",
3954
+ "minimize",
3955
+ "nonlinear",
3956
+ "optimization"
3957
+ ]
3958
+ },
3959
+ {
3960
+ "filePath": "optimization/Quadratic/PortfolioOpt2.json",
3961
+ "modelName": "PortfolioOpt2Example",
3962
+ "description": "RASON Portfolio Opt 2 Example with Multiple Optimizations. This is similar to the original PortfolioOpt, a portfolio optimization model, but here we run 2 optimizations, using a different minimum variance value for each solve, using the optimization parameter PsiOptParam. PsiOptParam varies the Desired Return from 9.5% to 10% by setting the number of optimizations to 2 in modelSettings. PsiOptParam is introduced in the Parameters section and then called in the 'return' constraint. In the first optimization, the minimum variance = 9.5% and 10% in the 2nd optimization. The result will contain the final variable and objective function values for each optimization.",
3963
+ "modelType": "optimization",
3964
+ "subcategory": "quadratic",
3965
+ "features": [
3966
+ "variables",
3967
+ "constraints",
3968
+ "objective",
3969
+ "data"
3970
+ ],
3971
+ "psiFunctions": [
3972
+ "PsiOptParam"
3973
+ ],
3974
+ "variableCount": 1,
3975
+ "constraintCount": 2,
3976
+ "objectiveType": "minimize",
3977
+ "tags": [
3978
+ "minimize",
3979
+ "optimization",
3980
+ "probability-distribution",
3981
+ "quadratic"
3982
+ ]
3983
+ },
3984
+ {
3985
+ "filePath": "optimization/Quadratic/PortfolioOpt.json",
3986
+ "modelName": "PortfolioOptExample",
3987
+ "description": "Quadratic (QP) RASON example: This model finds the optimal allocation of funds to stocks that minimizes the portfolio risk, measured by portfolio Variance (a quadratic function), computed via a custom QUADPRODUCT function. This quadratic programming (QP) model can be solved with the GRG Nonlinear Solver, or more efficiently with the LP/Quadratic Solver or the SOCP Barrier Solver.",
3988
+ "modelType": "optimization",
3989
+ "subcategory": "quadratic",
3990
+ "features": [
3991
+ "variables",
3992
+ "constraints",
3993
+ "objective",
3994
+ "data"
3995
+ ],
3996
+ "variableCount": 1,
3997
+ "constraintCount": 2,
3998
+ "objectiveType": "minimize",
3999
+ "tags": [
4000
+ "minimize",
4001
+ "optimization",
4002
+ "quadratic"
4003
+ ]
4004
+ },
4005
+ {
4006
+ "filePath": "optimization/WithUncertainty/GasCompanyChance.json",
4007
+ "modelName": "GasCompanyChanceExample",
4008
+ "description": "RASON example model using chance constraints: A gas company buys gas and then sells it to its consumers. The consumer demand this year is expected to be 100 units and price is $5 per unit. Next year's gas price and demand will depend on the weather. In the 2nd year, the weather could be either very cold or warm. If the weather is very cold, demand will be 180 with price of $7.50. If the weather is warm, demand will be 100 with a price of $5.00. Demand and price are perfectly correlated since both depend on the weather. To capture this, we use the Beta distribution for the uncertain variable, D5, in the calculation of both the demand and the price in year 2. The gas company can buy gas this year at the current price of $5/unit and store it for use next year. If gas is stored, there will be an associated holding or storage cost of $1/unit per year. How much gas should the company purchase this year (before next year's demand is known) and next year (after next year's demand is known)? This example models this problem with a chance constraint, assuming that all three decisions are 'here and now'.",
4009
+ "modelType": "optimization",
4010
+ "subcategory": "stochastic",
4011
+ "features": [
4012
+ "variables",
4013
+ "constraints",
4014
+ "objective",
4015
+ "uncertain-variables",
4016
+ "formulas"
4017
+ ],
4018
+ "psiFunctions": [
4019
+ "PsiBeta"
4020
+ ],
4021
+ "variableCount": 2,
4022
+ "constraintCount": 2,
4023
+ "objectiveType": "min",
4024
+ "tags": [
4025
+ "min",
4026
+ "monte-carlo",
4027
+ "optimization",
4028
+ "probability-distribution",
4029
+ "stochastic"
4030
+ ]
4031
+ },
4032
+ {
4033
+ "filePath": "optimization/WithUncertainty/GasCompanyRecourse.json",
4034
+ "modelName": "GasCompanyRecourseExample",
4035
+ "description": "RASON example model with recourse variables: A gas company buys gas and then sells it to its consumers. The consumer demand this year is expected to be 100 units and price is $5 per unit. Next year's gas price and demand will depend on the weather: If Cold, Price = $7.50 with demand = 180, if Warm: Price = $5.00 with demand = 100. Demand and price are perfectly correlated since both depend on the weather. To capture this, we use the Beta distribution to calculate both the demand and the price in year 2. The gas company can buy gas this year at the current price of $5/unit and store it for use next year. If gas is stored for next year, there will be an associated holding or storage cost of $1/unit per year. How much gas should the company purchase this year (before next year's demand is known) and next year (after next year's demand is known)? This example models this problem with a 'wait and see' recourse variable. See GasCompanyChance to see this same model formulated with just a chance constraint.",
4036
+ "modelType": "optimization",
4037
+ "subcategory": "stochastic",
4038
+ "features": [
4039
+ "variables",
4040
+ "constraints",
4041
+ "objective",
4042
+ "uncertain-variables",
4043
+ "formulas",
4044
+ "data"
4045
+ ],
4046
+ "psiFunctions": [
4047
+ "PsiBeta"
4048
+ ],
4049
+ "variableCount": 2,
4050
+ "constraintCount": 2,
4051
+ "objectiveType": "min",
4052
+ "tags": [
4053
+ "min",
4054
+ "monte-carlo",
4055
+ "optimization",
4056
+ "probability-distribution",
4057
+ "stochastic"
4058
+ ]
4059
+ },
4060
+ {
4061
+ "filePath": "optimization/WithUncertainty/ProjectSelect2.json",
4062
+ "modelName": "ProjectSelect2Example",
4063
+ "description": "RASON Simulation Optimization Example with typical array names (i.e. no Excel range names): A company is considering eight different investment projects for the coming year. Each project's expected cash flow can be modeled as a PsiTriangular distribution with Minimum, Likely, and Maximum parameters. There is a 90% chance that each project chosen will be successful. The Initial Investment for each project can be found in the F block within 'formulas', below. Select the investments that will maximize the Expected Total Cash Flow while keeping within the $1.5M budget.",
4064
+ "modelType": "optimization",
4065
+ "subcategory": "stochastic",
4066
+ "features": [
4067
+ "variables",
4068
+ "constraints",
4069
+ "objective",
4070
+ "uncertain-variables",
4071
+ "formulas",
4072
+ "engine-settings"
4073
+ ],
4074
+ "psiFunctions": [
4075
+ "PsiTriangular",
4076
+ "PsiBinomial",
4077
+ "PsiMean"
4078
+ ],
4079
+ "variableCount": 1,
4080
+ "constraintCount": 1,
4081
+ "objectiveType": "maximize",
4082
+ "tags": [
4083
+ "evolutionary",
4084
+ "maximize",
4085
+ "monte-carlo",
4086
+ "optimization",
4087
+ "probability-distribution",
4088
+ "stochastic"
4089
+ ]
4090
+ },
4091
+ {
4092
+ "filePath": "optimization/WithUncertainty/ProjectSelect3.json",
4093
+ "modelName": "ProjectSelect3Example",
4094
+ "description": "RASON Simulation-optimization example with indexed assignments: A company is considering eight different investment projects for the coming year. Each project's expected cash flow can be modeled as a PsiTriangular distribution with Minimum, Likely, and Maximum parameters. There is a 90% chance that each project chosen will be successful. The Initial Investment for each project can be found in the f block in 'formulas', below. Select the investments that will maximize the Expected Total Cash Flow while keeping within the $1.5M budget. ",
4095
+ "modelType": "optimization",
4096
+ "subcategory": "stochastic",
4097
+ "features": [
4098
+ "variables",
4099
+ "constraints",
4100
+ "objective",
4101
+ "uncertain-variables",
4102
+ "formulas",
4103
+ "engine-settings"
4104
+ ],
4105
+ "psiFunctions": [
4106
+ "PsiTriangular",
4107
+ "PsiBinomial",
4108
+ "PsiMean"
4109
+ ],
4110
+ "variableCount": 1,
4111
+ "constraintCount": 1,
4112
+ "objectiveType": "maximize",
4113
+ "tags": [
4114
+ "evolutionary",
4115
+ "maximize",
4116
+ "monte-carlo",
4117
+ "optimization",
4118
+ "probability-distribution",
4119
+ "stochastic"
4120
+ ]
4121
+ },
4122
+ {
4123
+ "filePath": "optimization/WithUncertainty/ProjectSelect4.json",
4124
+ "modelName": "ProjectSelect4Example",
4125
+ "description": "Simulation-optimization RASON investment model example with formulas in array: A company is considering eight different investment projects for the coming year. Each project's expected cash flow can be modeled as a PsiTriangular distribution with Minimum, Likely, and Maximum parameters. There is a 90% chance that each project chosen will be successful. The Initial Investment for each project can be found in the f block within 'formulas', below. Select the investments that will maximize the Expected Total Cash Flow while keeping within the $1.5M budget. ",
4126
+ "modelType": "optimization",
4127
+ "subcategory": "stochastic",
4128
+ "features": [
4129
+ "variables",
4130
+ "constraints",
4131
+ "objective",
4132
+ "uncertain-variables",
4133
+ "formulas",
4134
+ "engine-settings"
4135
+ ],
4136
+ "psiFunctions": [
4137
+ "PsiBinomial",
4138
+ "PsiMean"
4139
+ ],
4140
+ "variableCount": 1,
4141
+ "constraintCount": 1,
4142
+ "objectiveType": "maximize",
4143
+ "tags": [
4144
+ "evolutionary",
4145
+ "maximize",
4146
+ "monte-carlo",
4147
+ "optimization",
4148
+ "probability-distribution",
4149
+ "stochastic"
4150
+ ]
4151
+ },
4152
+ {
4153
+ "filePath": "optimization/WithUncertainty/ProjectSelect.json",
4154
+ "modelName": "ProjectSelectExample",
4155
+ "description": "RASON Simulation Optimization Example with Excel ranges as array names: A company is considering eight different investment projects for the coming year. Each project's expected cash flow can be modeled as a PsiTriangular distribution with Minimum, Likely, and Maximum parameters. There is a 90% chance that each project chosen will be successful. The Initial Investment for each project can be found in F1:F8 block within 'formulas', below. Select the investments that will maximize the Expected Total Cash Flow while keeping within the $1.5M budget.",
4156
+ "modelType": "optimization",
4157
+ "subcategory": "stochastic",
4158
+ "features": [
4159
+ "variables",
4160
+ "constraints",
4161
+ "objective",
4162
+ "uncertain-variables",
4163
+ "formulas",
4164
+ "engine-settings"
4165
+ ],
4166
+ "psiFunctions": [
4167
+ "PsiTriangular",
4168
+ "PsiBinomial",
4169
+ "PsiMean"
4170
+ ],
4171
+ "variableCount": 1,
4172
+ "constraintCount": 1,
4173
+ "objectiveType": "maximize",
4174
+ "tags": [
4175
+ "evolutionary",
4176
+ "maximize",
4177
+ "monte-carlo",
4178
+ "optimization",
4179
+ "probability-distribution",
4180
+ "stochastic"
4181
+ ]
4182
+ },
4183
+ {
4184
+ "filePath": "rason-features/BoxIterators/Box_Fun_Loop_Iter_Sim_RASON.json",
4185
+ "modelName": "Box_Fun_Loop_Iter_Sim_Rason",
4186
+ "description": "Box Function example that calculates a monthly loan payment for three unique loans in three ways. 1. Using a box function 2. Using a box function loop and 3. Using a box iterator. This example combines all three above examples into 1: Simulation example with Box Function, with Box function Loop and with Box Iterator.",
4187
+ "modelType": "simulation",
4188
+ "subcategory": null,
4189
+ "features": [
4190
+ "uncertain-variables",
4191
+ "uncertain-functions",
4192
+ "formulas",
4193
+ "data",
4194
+ "engine-settings",
4195
+ "box-functions",
4196
+ "box-iterators"
4197
+ ],
4198
+ "isFeatureDemo": true,
4199
+ "psiFunctions": [
4200
+ "PsiNormal",
4201
+ "PsiOutput"
4202
+ ],
4203
+ "uncertainVariableCount": 7,
4204
+ "uncertainFunctionCount": 9,
4205
+ "distributions": [
4206
+ "PsiNormal",
4207
+ "PsiOutput"
4208
+ ],
4209
+ "samplingMethod": "Latin",
4210
+ "tags": [
4211
+ "box-function",
4212
+ "box-iterator",
4213
+ "latin",
4214
+ "monte-carlo",
4215
+ "probability-distribution",
4216
+ "simulation",
4217
+ "stochastic"
4218
+ ]
4219
+ },
4220
+ {
4221
+ "filePath": "rason-features/BoxIterators/Box_Fun_Loop_Sim_RASON.json",
4222
+ "modelName": "Box_Fun_Loop_SIM_Rason",
4223
+ "description": "Box Function Loop example that calculates a monthly loan payment for three unique loans.",
4224
+ "modelType": "simulation",
4225
+ "subcategory": null,
4226
+ "features": [
4227
+ "uncertain-variables",
4228
+ "uncertain-functions",
4229
+ "formulas",
4230
+ "data",
4231
+ "engine-settings",
4232
+ "box-functions"
4233
+ ],
4234
+ "isFeatureDemo": true,
4235
+ "psiFunctions": [
4236
+ "PsiNormal"
4237
+ ],
4238
+ "uncertainVariableCount": 4,
4239
+ "uncertainFunctionCount": 3,
4240
+ "distributions": [
4241
+ "PsiNormal"
4242
+ ],
4243
+ "samplingMethod": "Latin",
4244
+ "tags": [
4245
+ "box-function",
4246
+ "latin",
4247
+ "monte-carlo",
4248
+ "probability-distribution",
4249
+ "simulation",
4250
+ "stochastic"
4251
+ ]
4252
+ },
4253
+ {
4254
+ "filePath": "rason-features/BoxIterators/Box_Fun_Sim_RASON.json",
4255
+ "modelName": "Box_Fun_Sim_Rason",
4256
+ "description": "Box Function example that calculates a monthly loan payment for three unique loans.",
4257
+ "modelType": "simulation",
4258
+ "subcategory": null,
4259
+ "features": [
4260
+ "uncertain-variables",
4261
+ "uncertain-functions",
4262
+ "formulas",
4263
+ "data",
4264
+ "engine-settings",
4265
+ "box-functions"
4266
+ ],
4267
+ "isFeatureDemo": true,
4268
+ "psiFunctions": [
4269
+ "PsiNormal",
4270
+ "PsiOutput"
4271
+ ],
4272
+ "uncertainVariableCount": 3,
4273
+ "uncertainFunctionCount": 3,
4274
+ "distributions": [
4275
+ "PsiNormal",
4276
+ "PsiOutput"
4277
+ ],
4278
+ "samplingMethod": "Latin",
4279
+ "tags": [
4280
+ "box-function",
4281
+ "latin",
4282
+ "monte-carlo",
4283
+ "probability-distribution",
4284
+ "simulation",
4285
+ "stochastic"
4286
+ ]
4287
+ },
4288
+ {
4289
+ "filePath": "rason-features/BoxIterators/Box_Iter_SIM_RASON.json",
4290
+ "modelName": "Box_Iter_Sim_Rason",
4291
+ "description": "Box Iterator example that calculates a monthly loan payment for three unique loans.",
4292
+ "modelType": "simulation",
4293
+ "subcategory": null,
4294
+ "features": [
4295
+ "uncertain-variables",
4296
+ "uncertain-functions",
4297
+ "formulas",
4298
+ "data",
4299
+ "engine-settings",
4300
+ "box-iterators"
4301
+ ],
4302
+ "isFeatureDemo": true,
4303
+ "uncertainVariableCount": 1,
4304
+ "uncertainFunctionCount": 3,
4305
+ "samplingMethod": "Latin",
4306
+ "tags": [
4307
+ "box-iterator",
4308
+ "latin",
4309
+ "monte-carlo",
4310
+ "simulation",
4311
+ "stochastic"
4312
+ ]
4313
+ },
4314
+ {
4315
+ "filePath": "rason-features/BoxLambdaExamples/BoxFunSimulate.json",
4316
+ "modelName": "BoxFunctionSimulation",
4317
+ "description": "Simulation model containing a box function that calculates the predicted daily price of a stock. In the original example, GBM Simulation Example, the daily predicted stock price is calculated using a typical formula entered into the 'formulas' section. In this example, the predicted daily stock price is calculated using a custom, reusable Box Function. Box Functions are an easy, reliable method to replicate formulas in a RASON model. For more information on Box Functions, see Defining Custom Functions on the Help tab. ",
4318
+ "modelType": "simulation",
4319
+ "subcategory": null,
4320
+ "features": [
4321
+ "uncertain-variables",
4322
+ "uncertain-functions",
4323
+ "formulas",
4324
+ "data",
4325
+ "box-functions"
4326
+ ],
4327
+ "isFeatureDemo": true,
4328
+ "psiFunctions": [
4329
+ "PsiNormal"
4330
+ ],
4331
+ "uncertainVariableCount": 5,
4332
+ "uncertainFunctionCount": 5,
4333
+ "distributions": [
4334
+ "PsiNormal"
4335
+ ],
4336
+ "tags": [
4337
+ "box-function",
4338
+ "monte-carlo",
4339
+ "probability-distribution",
4340
+ "simulation",
4341
+ "stochastic"
4342
+ ]
4343
+ },
4344
+ {
4345
+ "filePath": "simulation/CandyStoreSalesUsingSIP.json",
4346
+ "modelName": "CandyStoreSales(Sim)",
4347
+ "description": "RASON model that uses a SIP (PsiSip) which uses a historical data point for each trial. Benjamin is the owner/operator of a candy store. His best selling products are chocolate bars, JuJu Beans, chocolate nuggets and eclairs. Using last year's sales data from each product, he has estimated his daily Gross Profit from these four products using four different SIPs (Stochastic Information Packets), one for each product.",
4348
+ "modelType": "simulation",
4349
+ "subcategory": null,
4350
+ "features": [
4351
+ "uncertain-variables",
4352
+ "uncertain-functions",
4353
+ "formulas",
4354
+ "data",
4355
+ "engine-settings"
4356
+ ],
4357
+ "psiFunctions": [
4358
+ "PsiSip"
4359
+ ],
4360
+ "uncertainVariableCount": 4,
4361
+ "uncertainFunctionCount": 5,
4362
+ "distributions": [
4363
+ "PsiSip"
4364
+ ],
4365
+ "samplingMethod": "Latin",
4366
+ "tags": [
4367
+ "latin",
4368
+ "monte-carlo",
4369
+ "probability-distribution",
4370
+ "simulation",
4371
+ "stochastic"
4372
+ ]
4373
+ },
4374
+ {
4375
+ "filePath": "simulation/CollegeFundGrowth1.json",
4376
+ "modelName": "CollegeFundGrowth1(Sim)",
4377
+ "description": "CollegeFundGrowth1 - RASON Model that simulates a college fund account, PsiMetalog distribution models the yearly market returns. Imagine a couple, Mark and Nicole, want to ensure that they have enough funds to send their sons Joseph and Benjamin to college after they graduate from high school. They have opened a 529 account at their local investment bank, but are unsure how much to invest each year to ensure that enough funds are available when needed. Mark and Nicole are projecting that the price for a private 4 year institution will be $75,000 per year. Nicole has fit a distribution to the historical returns from the S&P 500 using Analytic Solver. She is using this return to model the portfolio return for each year the 529 is in use. If the balance of the portfolio is negative, Nicole assumes she will borrow money to cover the cost of tuition at an 8% interest rate.",
4378
+ "modelType": "simulation",
4379
+ "subcategory": null,
4380
+ "features": [
4381
+ "uncertain-variables",
4382
+ "uncertain-functions",
4383
+ "formulas",
4384
+ "data",
4385
+ "engine-settings"
4386
+ ],
4387
+ "psiFunctions": [
4388
+ "PsiMetalog"
4389
+ ],
4390
+ "uncertainVariableCount": 25,
4391
+ "uncertainFunctionCount": 1,
4392
+ "distributions": [
4393
+ "PsiMetalog"
4394
+ ],
4395
+ "samplingMethod": "Latin",
4396
+ "tags": [
4397
+ "latin",
4398
+ "monte-carlo",
4399
+ "probability-distribution",
4400
+ "simulation",
4401
+ "stochastic"
4402
+ ]
4403
+ },
4404
+ {
4405
+ "filePath": "simulation/CollegeFundGrowth2.json",
4406
+ "modelName": "CollegeFundGrowth2(Sim)",
4407
+ "description": "RASON example that Simulates the market's effect on the balance of a college fund savings account: Mark and Nicole want to ensure that they have enough funds to send their sons Joseph and Benjamin to college after they graduate from high school. They have opened a 529 account at their local investment bank, but are unsure how much money they should invest each year to ensure that enough funds are available when needed. Mark and Nicole are projecting that the price for a private 4 year institution will be $75,000 per year. Nicole assumed the yearly portfolio return to follow a Normal distribution with mean of 10% and standard deviation of 20%. If the balance of the portfolio is negative, Nicole assumes she will borrow money to cover the cost of tuition at an 8% interest rate.",
4408
+ "modelType": "simulation",
4409
+ "subcategory": null,
4410
+ "features": [
4411
+ "uncertain-variables",
4412
+ "uncertain-functions",
4413
+ "formulas",
4414
+ "data",
4415
+ "engine-settings"
4416
+ ],
4417
+ "psiFunctions": [
4418
+ "PsiNormal",
4419
+ "PsiOutput"
4420
+ ],
4421
+ "uncertainVariableCount": 24,
4422
+ "uncertainFunctionCount": 24,
4423
+ "distributions": [
4424
+ "PsiNormal",
4425
+ "PsiOutput"
4426
+ ],
4427
+ "samplingMethod": "Latin",
4428
+ "tags": [
4429
+ "latin",
4430
+ "monte-carlo",
4431
+ "probability-distribution",
4432
+ "simulation",
4433
+ "stochastic"
4434
+ ]
4435
+ },
4436
+ {
4437
+ "filePath": "simulation/CollegeFundGrowthSIP.json",
4438
+ "modelName": "CollegeFundGrowthSIP",
4439
+ "description": "RASON example that uses Shared Information Probability resources (SIPs, also known as 'Stochastic Information Packets'), you can ensure that your group or organization uses consistent data about uncertain/risky variables across simulation or decision models, enabling model results to be meaningfully compared. In this example, the fitted distribution, from the College Fund Growth 1 Example model in Excel, has been deployed to the Probability Model for CollegeFundGrowthSIP, under RASON Examples -- Simulation. Recall that the College Fund Growth example simulates the life of a college 529 account from a child's birth to the child's graduation from college. This RASON example, calls the fitted distribution in the Probability Model to be used as the uncertain variables. This uncertain variable models the Portfolio Return for each year that the 529 is in existence.",
4440
+ "modelType": "simulation",
4441
+ "subcategory": null,
4442
+ "features": [
4443
+ "uncertain-variables",
4444
+ "uncertain-functions",
4445
+ "formulas",
4446
+ "data",
4447
+ "engine-settings"
4448
+ ],
4449
+ "psiFunctions": [
4450
+ "PsiLibSip"
4451
+ ],
4452
+ "uncertainVariableCount": 25,
4453
+ "uncertainFunctionCount": 1,
4454
+ "distributions": [
4455
+ "PsiLibSip"
4456
+ ],
4457
+ "samplingMethod": "Latin",
4458
+ "tags": [
4459
+ "latin",
4460
+ "monte-carlo",
4461
+ "probability-distribution",
4462
+ "simulation",
4463
+ "stochastic"
4464
+ ]
4465
+ },
4466
+ {
4467
+ "filePath": "simulation/GBMSimulationModel.json",
4468
+ "modelName": "GBMSimpleModel(Sim)",
4469
+ "description": "RASON example model using Simple Geometric Brownian Motion based Pricing Model: Data obtained from www.yahoo.com.",
4470
+ "modelType": "simulation",
4471
+ "subcategory": null,
4472
+ "features": [
4473
+ "uncertain-variables",
4474
+ "uncertain-functions",
4475
+ "formulas",
4476
+ "data",
4477
+ "engine-settings"
4478
+ ],
4479
+ "psiFunctions": [
4480
+ "PsiNormal",
4481
+ "PsiOutput"
4482
+ ],
4483
+ "uncertainVariableCount": 24,
4484
+ "uncertainFunctionCount": 24,
4485
+ "distributions": [
4486
+ "PsiNormal",
4487
+ "PsiOutput"
4488
+ ],
4489
+ "samplingMethod": "Latin",
4490
+ "tags": [
4491
+ "latin",
4492
+ "monte-carlo",
4493
+ "probability-distribution",
4494
+ "simulation",
4495
+ "stochastic"
4496
+ ]
4497
+ },
4498
+ {
4499
+ "filePath": "rason-features/BoxLambdaExamples/LambdaFunSimulate.json",
4500
+ "modelName": "LambdaFunSimulate",
4501
+ "description": "In this example, a LAMBDA Excel functon is used to create a custom, reusable function that can be called mulitiple times to calculate the predicted daily stock price. Notice that the decision varaibles, constraints and the objective function have not changed from the original GBM Simulation Model under Examples - Simulation.",
4502
+ "modelType": "simulation",
4503
+ "subcategory": null,
4504
+ "features": [
4505
+ "uncertain-variables",
4506
+ "uncertain-functions",
4507
+ "data",
4508
+ "box-functions"
4509
+ ],
4510
+ "isFeatureDemo": true,
4511
+ "psiFunctions": [
4512
+ "PsiNormal"
4513
+ ],
4514
+ "uncertainVariableCount": 5,
4515
+ "uncertainFunctionCount": 5,
4516
+ "distributions": [
4517
+ "PsiNormal"
4518
+ ],
4519
+ "tags": [
4520
+ "box-function",
4521
+ "monte-carlo",
4522
+ "probability-distribution",
4523
+ "simulation",
4524
+ "stochastic"
4525
+ ]
4526
+ },
4527
+ {
4528
+ "filePath": "rason-features/UserGuide/UGForecast.json",
4529
+ "modelName": "UGForecastSimExample",
4530
+ "description": "RASON Forecast Simulation Example - This example appears in the Defining Your Simulation MOdel chapter in the RASON User Guide. Imagine that you are the sales manager for a company that is planning to introduce a new product. You need to estimate the first year profit from this product (which depends on the number of unit sales), the price per unit sold, the unit manufacturing cost, and any fixed costs or overhead. You have been advised that the unit manufacturing cost will range between $4.50 and $8.50, with a most-likely cost of $6.50. Based on your market research, you believe it is equally likely that the market demand will be Slow, OK, or Hot.",
4531
+ "modelType": "simulation",
4532
+ "subcategory": null,
4533
+ "features": [
4534
+ "uncertain-variables",
4535
+ "uncertain-functions",
4536
+ "formulas",
4537
+ "data"
4538
+ ],
4539
+ "isFeatureDemo": true,
4540
+ "psiFunctions": [
4541
+ "PsiIntUniform",
4542
+ "PsiTriangular"
4543
+ ],
4544
+ "uncertainVariableCount": 2,
4545
+ "uncertainFunctionCount": 1,
4546
+ "distributions": [
4547
+ "PsiIntUniform",
4548
+ "PsiTriangular"
4549
+ ],
4550
+ "tags": [
4551
+ "monte-carlo",
4552
+ "probability-distribution",
4553
+ "simulation",
4554
+ "stochastic"
4555
+ ]
4556
+ },
4557
+ {
4558
+ "filePath": "rason-features/UserGuide/UGYieldManagement1.json",
4559
+ "modelName": "UGYieldManagement1Example",
4560
+ "description": "RASON Single Simulation Example: This model is discussed in the chapter, Defining a Simulation Model within the Rason User Guide (downloadable from the Help tab). This example is a simple airline revenue management model, also known as a yield management model. the subsequentexamples, UGYieldManagement2 and UGYieldManagement3, will transform this simple simulation model, first into a parameterized model in the next example and then a simulation optimization model in the third example. The example files that are discussed are: UGYieldManagement1.json (a simple simulation model), UGYieldManagement2.json (a model with multiple parameterized simulations) and UGYieldManagement3.json (a simulation optimization model). You can open each example by clicking RASON Examples on the Editor page, then Example models discussed in RASON User Guide.",
4561
+ "modelType": "simulation",
4562
+ "subcategory": null,
4563
+ "features": [
4564
+ "uncertain-variables",
4565
+ "uncertain-functions",
4566
+ "formulas",
4567
+ "data",
4568
+ "engine-settings"
4569
+ ],
4570
+ "isFeatureDemo": true,
4571
+ "psiFunctions": [
4572
+ "PsiLogNormal"
4573
+ ],
4574
+ "uncertainVariableCount": 1,
4575
+ "uncertainFunctionCount": 1,
4576
+ "distributions": [
4577
+ "PsiLogNormal"
4578
+ ],
4579
+ "samplingMethod": null,
4580
+ "tags": [
4581
+ "monte-carlo",
4582
+ "probability-distribution",
4583
+ "simulation",
4584
+ "stochastic"
4585
+ ]
4586
+ },
4587
+ {
4588
+ "filePath": "rason-features/UserGuide/UGYieldManagement2.json",
4589
+ "modelName": "UGYieldManagement2Example",
4590
+ "description": "RASON Parametric Simulation Model: In the simulation results for the original model, UGYieldMangement1, the mean or expected net revenue is about $20,000. The 10th percentile equals 19,950, which infers that if 110 tickets are sold, the revenue earned is almost as much as a full flight 90% of the time. (Full flight revenue = 100*200) This leads to the question, should we sell more tickets? How many tickets can we sell in order to increase revenue? One could simply enter various values for 'sold', each time recording the revenue value to see if it increases or decreases. However, entering the parameter PsiSimParam() allows multiple values to be entered and simulations performed, all at once!",
4591
+ "modelType": "simulation",
4592
+ "subcategory": null,
4593
+ "features": [
4594
+ "uncertain-variables",
4595
+ "uncertain-functions",
4596
+ "formulas",
4597
+ "data",
4598
+ "engine-settings"
4599
+ ],
4600
+ "isFeatureDemo": true,
4601
+ "psiFunctions": [
4602
+ "PsiSimParam",
4603
+ "PsiLogNormal"
4604
+ ],
4605
+ "uncertainVariableCount": 1,
4606
+ "uncertainFunctionCount": 1,
4607
+ "distributions": [
4608
+ "PsiSimParam",
4609
+ "PsiLogNormal"
4610
+ ],
4611
+ "samplingMethod": null,
4612
+ "tags": [
4613
+ "monte-carlo",
4614
+ "probability-distribution",
4615
+ "simulation",
4616
+ "stochastic"
4617
+ ]
4618
+ },
4619
+ {
4620
+ "filePath": "simulation/YieldManagement2(Sim).json",
4621
+ "modelName": "YieldManagement2SimExample",
4622
+ "description": "RASON Simulation example runs multi-simulations with simulation parameter, PsiSimParam(). The price for a flight ticket from San Francisco to Seattle is $200. Each plane can hold no more than 100 passengers. Usually, some passengers who have purchased a ticket are 'no-shows'. To protect against such no-shows, the airline would like to sell more than 100 tickets for each flight. Federal regulations require that any ticketed customer who is unable to board the plane due to overbooking is entitled to a compensation of 125% of the ticket value paid by the customer. Any no-show customer is refunded 50% of the ticket value paid by the customer. The number of no-shows is randomly distributed with a Lognormal distribution with mean of 10% of the Number of Tickets Sold and standard deviation of 6% of the Number of Tickets Sold. As in the simpler example, YieldManagementModel1, the only uncertainty is the number of no-shows, 'no_shows', depends on the parameter 'sold' which represents the number of tickets sold. However, in this example, we use the PsiSimParam() function to observe how the Expected Total Revenue (the uncertain function) varies as the number of tickets sold varies from 110 to 120. When you run multiple simulations at once, you can use the PsiSimParam() function to specify a list of values for a cell, one per simulation, where the value is held constant for all trials in a simulation. The PsiSimParam() function is located within the 'parameters' section. This function varies the Number of Tickets Sold from 110 to 120. The number of simulations to perform is set to 11 within 'modelSettings' tells RASON Decision Services to perform eleven simulations, each with 100 trials, due to the numTrials option setting. The Expected Revenue is computed using the Mean statistic, for each simulation.",
4623
+ "modelType": "simulation",
4624
+ "subcategory": null,
4625
+ "features": [
4626
+ "uncertain-variables",
4627
+ "uncertain-functions",
4628
+ "formulas",
4629
+ "data",
4630
+ "engine-settings"
4631
+ ],
4632
+ "psiFunctions": [
4633
+ "PsiSimParam",
4634
+ "PsiLogNormal"
4635
+ ],
4636
+ "uncertainVariableCount": 1,
4637
+ "uncertainFunctionCount": 2,
4638
+ "distributions": [
4639
+ "PsiSimParam",
4640
+ "PsiLogNormal"
4641
+ ],
4642
+ "samplingMethod": null,
4643
+ "tags": [
4644
+ "monte-carlo",
4645
+ "probability-distribution",
4646
+ "simulation",
4647
+ "stochastic"
4648
+ ]
4649
+ },
4650
+ {
4651
+ "filePath": "simulation/YieldManagement(Sim).json",
4652
+ "modelName": "YieldManagementSimExample",
4653
+ "description": "RASON Airline Revenue Management Model: The price for a flight ticket from San Francisco to Seattle is $200. Each plane can hold no more than 100 passengers. Usually, some passengers who have purchased a ticket are 'no-shows'. To protect against such no-shows, the airline would like to sell more than 100 tickets for each flight. Federal regulations require that any ticketed customer who is unable to board the plane due to overbooking is entitled to compensation of 125% of the ticket value paid by the customer. Any no-show customer is refunded 50% of the ticket value paid by the customer. The number of no-shows, 'no_shows', is randomly distributed with a Lognormal distribution with mean of 10% of the number of tickets sold, 'sold', and standard deviation of 6% of 'sold'. In this problem, the only uncertainty, 'no_shows', depends on the parameter 'sold'. (The ROUND function in the 'show-ups' formula, rounds the fractional value for 'no_shows' to a whole number.) The number of tickets sold is set to 110. Total Revenue (the uncertain function) is a random quantity, since it depends on the number of no-shows. the mean is returned in the results. This mean is the Expected Total Revenue for the flight. The distribution of Total Revenue will change with the Number of Tickets Sold. Enter a new value for 'sold' to see how the distribution of Total Revenue changes. Try to find an optimal number that will maximize the Total Expected Revenue.",
4654
+ "modelType": "simulation",
4655
+ "subcategory": null,
4656
+ "features": [
4657
+ "uncertain-variables",
4658
+ "uncertain-functions",
4659
+ "formulas",
4660
+ "data",
4661
+ "engine-settings"
4662
+ ],
4663
+ "psiFunctions": [
4664
+ "PsiLogNormal"
4665
+ ],
4666
+ "uncertainVariableCount": 1,
4667
+ "uncertainFunctionCount": 1,
4668
+ "distributions": [
4669
+ "PsiLogNormal"
4670
+ ],
4671
+ "samplingMethod": 2,
4672
+ "tags": [
4673
+ "monte-carlo",
4674
+ "probability-distribution",
4675
+ "simulation",
4676
+ "stochastic"
4677
+ ]
4678
+ }
4679
+ ]