@frontlinesystems/rason-mcp-server 2026.5.1 → 2026.5.3

package/examples/rason-features/ReferenceGuide/RGProductMixExcel11.json

@@ -1,117 +1,117 @@
-{
-  "modelName": "RGProductMixExcel11",
-  "modelDescription": "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.) ",
-  "modelType": "optimization",
-  "datasources": {
-    "comment": "Imports data from outside datasources.",
-    "parts_data": {
-      "comment": "Imports the parts data.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!G2:I12",
-      "indexCols": [ "parts", "prods" ],
-      "valueCols": [ "qty" ],
-      "direction": "import"
-    },
-    "invent_data": {
-      "comment": "Imports the inventory data.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!N2:O6",
-      "indexCols": [ "parts" ],
-      "valueCols": [ "inventory" ],
-      "direction": "import"
-    },
-    "profit_data": {
-      "comment": "Imports the profit per unit data.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!K2:L4",
-      "indexCols": [ "prods" ],
-      "valueCols": [ "profits" ],
-      "direction": "import"
-    },
-    "vars_data": {
-      "comment": "The vars_data data source performs a dual function by first importing the decision variable initial values from the Excel file ProductMixExcel.xlsx and then saving the final variable values back to that same file. The first property, type, specifies the type of file where the data is being imported/exported ('Excel'), the second property, connection, specifies the file name within quotes ('ResultVarsInit.txt') and the third property, selection, specifies where the final variable values will be appended ('Sheet1!Q2:R4'). We could pass a defined name here rather than a cell address. The fourth and fifth properties (indexCols and valueCols) are required for importing the initial variable values. The property, indexCols specifies the dimension(s) (or column(s)) to be imported and the property, valueCols, specifies the value column to be imported. Within variables, the x array definition uses the valueCol property to pass the initial variable values and the binding property to 'bind' to the vars_data data source. Since only one output property (finalValue:[]) is present within the x array definition, only the final variable values will be appended to the original cell address, Q2:R4. The last property, 'direction', indicates that the file will be both imported and exported hence the setting 'import/export'. Note:  If the 'initials' column heading in Excel is replaced with  'finalValue'. RASON will both read the initial variable values from cells R2:R4 and overwrite these values with the final variable values after the model is solved.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!Q2:R4",
-      "indexCols": [ "prods" ],
-      "valueCols": [ "initials" ],
-      "direction": "import/export"
-    },
-    "fcns_data": {
-      "comment": "The fcns_data datasource exports the final constraint values to the Excel file, ProductMixExcel.xlsx.  The first property, type: 'Excel', specifies the type of file where the data is being imported/exported, in this instance an Excel file. The second property, connection, specifies the file name within quotes ('ProductMixExce.xlsx'). The 3rd property, selection: 'Sheet1!U2:U6', gives the location, within the ProductMixExcel.xlsx workbook, where the final constraint values will be saved. Alternatively, we could pass a defined name here. The 4th property, indexCols, indexes the data by the 'prods' column (or dimension). The binding property within the c constraint definition binds the constraint block c to the fcns_data datasource. One output property (finalValue:[]) is included in the c definition. The RASON interpreter will append the final constraint values to the original selection. The last property, 'direction', indicates that the file will be exported. (The default setting for the direction property is 'import'.) For a complete list of results that may be written to a writeable data source, see the constraints section discussion within the RASON Reference Guide.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!U2:U6",
-      "indexCols": [ "parts" ],
-      "direction": "export"
-    },
-    "obj_data": {
-      "comment": "The obj_data datasource exports the final objective value to ProductMixExcel.xlsx.  The first property, type, specifies the file type ('Excel'), the second property, connection, specifies the file name ('ResultObj.txt') and the third property, selection, specifies where the final objective value will be written ('Sheet1!X1'). The binding property within the total objective definition the objective definition to the obj_data data source. Since only the finalValue result property is present within the objective definition, only the final value of the objective function (a single value) will be saved to ProductMixExcel!X2. The last property, 'direction', indicates that the file will be exported. For a complete list of results that may be written to a writeable data source, see the objective section discussion within the RASON Reference Guide.",
-      "type": "excel",
-      "connection": "ProductMixExcel.xlsx",
-      "selection": "Sheet1!X2",
-      "direction": "export"
-    }
-  },
-  "data": {
-    "comment": "Binds the datasources to data component.",
-    "parts2": {
-      "comment": "Binds the values in the qty column in the parts_data datasource to parts2 data component.",
-      "binding": "parts_data",
-      "valueCol": "qty"
-    },
-    "invent": {
-      "comment": "Binds the values in the inventory column in the invent_data datasource to invent data component.",
-      "binding": "invent_data",
-      "valueCol": "inventory"
-    },
-    "profit": {
-      "comment": "Binds the values in the profits column in the profit_data datasource to profit data component.",
-      "binding": "profit_data",
-      "valueCol": "profits"
-    }
-  },
-  "formulas": {
-    "comment": "Use this section to calculate intermediate formulas to be used within the constraints and objective sections.",
-    "piv_parts": {
-      "comment": "Calculates the amount of parts used to produce all three products.",
-      "formula": "PIVOT(parts2, { 'prods' }, { 'parts' })"
-    }
-  },
-  "variables": {
-    "comment": "Decision Variables",
-    "x": {
-      "comment": "The amount of products to produce, x[1] = TVs, x[2] = Stereos, x[3] = Speakers",
-      "dimensions": [ "prods" ],
-      "binding": "vars_data",
-      "valueCol": "initials",
-      "lower": 0,
-      "finalValue": [],
-      "indexValue": []
-    }
-  },
-  "constraints": {
-    "comment": "Constraints",
-    "c": {
-      "comment": "Generates 5 constraints that calculate the number of parts used in creating the three products, then sets each constraint equal to the amount of each part in inventory.",
-      "dimensions": [ "parts" ],
-      "binding": "fcns_data",
-      "formula": "MMULT(piv_parts, x) - invent",
-      "upper": 0,
-      "finalValue": []
-    }
-  },
-  "objective": {
-    "comment": "objective function",
-    "total": {
-      "comment": "Calculates the profit by multiplying the profit per unit of each product by the final variable values.",
-      "binding": "obj_data",
-      "formula": "sumproduct(x, profit)",
-      "type": "maximize",
-      "finalValue": []
-    }
-  }
-}
+{
+  "modelName": "RGProductMixExcel11",
+  "modelDescription": "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.) ",
+  "modelType": "optimization",
+  "datasources": {
+    "comment": "Imports data from outside datasources.",
+    "parts_data": {
+      "comment": "Imports the parts data.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!G2:I12",
+      "indexCols": [ "parts", "prods" ],
+      "valueCols": [ "qty" ],
+      "direction": "import"
+    },
+    "invent_data": {
+      "comment": "Imports the inventory data.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!N2:O6",
+      "indexCols": [ "parts" ],
+      "valueCols": [ "inventory" ],
+      "direction": "import"
+    },
+    "profit_data": {
+      "comment": "Imports the profit per unit data.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!K2:L4",
+      "indexCols": [ "prods" ],
+      "valueCols": [ "profits" ],
+      "direction": "import"
+    },
+    "vars_data": {
+      "comment": "The vars_data data source performs a dual function by first importing the decision variable initial values from the Excel file ProductMixExcel.xlsx and then saving the final variable values back to that same file. The first property, type, specifies the type of file where the data is being imported/exported ('Excel'), the second property, connection, specifies the file name within quotes ('ResultVarsInit.txt') and the third property, selection, specifies where the final variable values will be appended ('Sheet1!Q2:R4'). We could pass a defined name here rather than a cell address. The fourth and fifth properties (indexCols and valueCols) are required for importing the initial variable values. The property, indexCols specifies the dimension(s) (or column(s)) to be imported and the property, valueCols, specifies the value column to be imported. Within variables, the x array definition uses the valueCol property to pass the initial variable values and the binding property to 'bind' to the vars_data data source. Since only one output property (finalValue:[]) is present within the x array definition, only the final variable values will be appended to the original cell address, Q2:R4. The last property, 'direction', indicates that the file will be both imported and exported hence the setting 'import/export'. Note:  If the 'initials' column heading in Excel is replaced with  'finalValue'. RASON will both read the initial variable values from cells R2:R4 and overwrite these values with the final variable values after the model is solved.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!Q2:R4",
+      "indexCols": [ "prods" ],
+      "valueCols": [ "initials" ],
+      "direction": "import/export"
+    },
+    "fcns_data": {
+      "comment": "The fcns_data datasource exports the final constraint values to the Excel file, ProductMixExcel.xlsx.  The first property, type: 'Excel', specifies the type of file where the data is being imported/exported, in this instance an Excel file. The second property, connection, specifies the file name within quotes ('ProductMixExce.xlsx'). The 3rd property, selection: 'Sheet1!U2:U6', gives the location, within the ProductMixExcel.xlsx workbook, where the final constraint values will be saved. Alternatively, we could pass a defined name here. The 4th property, indexCols, indexes the data by the 'prods' column (or dimension). The binding property within the c constraint definition binds the constraint block c to the fcns_data datasource. One output property (finalValue:[]) is included in the c definition. The RASON interpreter will append the final constraint values to the original selection. The last property, 'direction', indicates that the file will be exported. (The default setting for the direction property is 'import'.) For a complete list of results that may be written to a writeable data source, see the constraints section discussion within the RASON Reference Guide.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!U2:U6",
+      "indexCols": [ "parts" ],
+      "direction": "export"
+    },
+    "obj_data": {
+      "comment": "The obj_data datasource exports the final objective value to ProductMixExcel.xlsx.  The first property, type, specifies the file type ('Excel'), the second property, connection, specifies the file name ('ResultObj.txt') and the third property, selection, specifies where the final objective value will be written ('Sheet1!X1'). The binding property within the total objective definition the objective definition to the obj_data data source. Since only the finalValue result property is present within the objective definition, only the final value of the objective function (a single value) will be saved to ProductMixExcel!X2. The last property, 'direction', indicates that the file will be exported. For a complete list of results that may be written to a writeable data source, see the objective section discussion within the RASON Reference Guide.",
+      "type": "excel",
+      "connection": "ProductMixExcel.xlsx",
+      "selection": "Sheet1!X2",
+      "direction": "export"
+    }
+  },
+  "data": {
+    "comment": "Binds the datasources to data component.",
+    "parts2": {
+      "comment": "Binds the values in the qty column in the parts_data datasource to parts2 data component.",
+      "binding": "parts_data",
+      "valueCol": "qty"
+    },
+    "invent": {
+      "comment": "Binds the values in the inventory column in the invent_data datasource to invent data component.",
+      "binding": "invent_data",
+      "valueCol": "inventory"
+    },
+    "profit": {
+      "comment": "Binds the values in the profits column in the profit_data datasource to profit data component.",
+      "binding": "profit_data",
+      "valueCol": "profits"
+    }
+  },
+  "formulas": {
+    "comment": "Use this section to calculate intermediate formulas to be used within the constraints and objective sections.",
+    "piv_parts": {
+      "comment": "Calculates the amount of parts used to produce all three products.",
+      "formula": "PIVOT(parts2, { 'prods' }, { 'parts' })"
+    }
+  },
+  "variables": {
+    "comment": "Decision Variables",
+    "x": {
+      "comment": "The amount of products to produce, x[1] = TVs, x[2] = Stereos, x[3] = Speakers",
+      "dimensions": [ "prods" ],
+      "binding": "vars_data",
+      "valueCol": "initials",
+      "lower": 0,
+      "finalValue": [],
+      "indexValue": []
+    }
+  },
+  "constraints": {
+    "comment": "Constraints",
+    "c": {
+      "comment": "Generates 5 constraints that calculate the number of parts used in creating the three products, then sets each constraint equal to the amount of each part in inventory.",
+      "dimensions": [ "parts" ],
+      "binding": "fcns_data",
+      "formula": "MMULT(piv_parts, x) - invent",
+      "upper": 0,
+      "finalValue": []
+    }
+  },
+  "objective": {
+    "comment": "objective function",
+    "total": {
+      "comment": "Calculates the profit by multiplying the profit per unit of each product by the final variable values.",
+      "binding": "obj_data",
+      "formula": "sumproduct(x, profit)",
+      "type": "maximize",
+      "finalValue": []
+    }
+  }
+}

package/examples/rason-features/ReferenceGuide/RGProductMixSQL11.json

@@ -1,108 +1,108 @@
-{
-  "modelName": "RGProductMixSQL11",
-  "modelDescription": "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.",
-  "modelType": "optimization",
-  "datasources": {
-    "comment": "Imports data from outside datasources. ValueCols must follow indexCols in selections",
-    "parts_data": {
-      "comment": "Imports the parts data.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "SELECT Parts as parts, Products as prods, Qty as qty FROM Parts ORDER BY ID",
-      "indexCols": [ "parts", "prods" ],
-      "valueCols": [ "qty" ],
-      "direction": "import"
-    },
-    "invent_data": {
-      "comment": "Imports the inventory data.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "SELECT Parts as parts, Inventory as inventory FROM Inventory ORDER BY ID",
-      "indexCols": [ "parts" ],
-      "valueCols": [ "inventory" ],
-      "direction": "import"
-    },
-    "profit_data": {
-      "comment": "Imports the profit per unit data.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "SELECT Products as prods, Profit as profit FROM Profits ORDER BY ID",
-      "indexCols": [ "prods" ],
-      "valueCols": [ "profit" ],
-      "direction": "import"
-    },
-    "vars_data": {
-      "comment": "The vars_data data source performs a dual function by first importing the decision variable initial values from the Access database and then saving the final variable values back to that same file. The first property, type, specifies the type of file where the data is being imported/exported ('msaccess'), the second property, connection, specifies the file name within quotes ('ProductMixAccess.accdb') and the third property, selection, imports two fields from the Profits table in order by ID ('SELECT Products, Initials FROM Profits ORDER BY ID). The 4th property, indexCols, indexes the data by the prods dimension while the 5th property, valueCols, imports the actual numerical data. The direction property ensures that the initial variable values are imported and the final variable values are exported using direction: 'import/export'. Within variables, the x array definition uses the valueCol property to pass the initial variable values and the binding property to bind to the vars_data data source. The final variable values (requested using the output property finalValues:[] within the x array definition) will be appended to the Profits table.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "SELECT Products as prods, Initials as initials FROM Profits ORDER BY ID",
-      "indexCols": [ "prods" ],
-      "valueCols": [ "initials" ],
-      "direction": "import/export"
-    },
-    "fcns_data": {
-      "comment": "The fcns_data datasource, exports the final constraint values to the Access data base file, ProductMixAccess.accdb. The first property, type: 'msaccess', specifies the type of file where the data is being imported/exported. Alternatively, 'access' or 'odbc' could have been passed instead of 'msaccess'. The second property, connection, specifies the file name within quotes ('ProductMixAcess.accdb'). The 3rd property, selection: 'ResultFcns', creates a table within the Access database, where the final constraint values will be saved. The direction property ensures that the file is 'exported'. Within the c constraint definition, the constraint block is bound to the fcns_data data source by the binding property. The output property, finalValue:[], will export the final constraint values to the ResultsFcns table within the file, ProductMixAccess.accdb.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "ResultFcns",
-      "direction": "export"
-    },
-    "obj_data": {
-      "comment": "The obj_data datasource exports the final objective value to ProductMixAccess.accdb. Again the first property, type, specifies the file type ('msaccess'), the second property, connection, specifies the file name ('ProductMixAccess.accdb') and the third property, selection, specifies the table where the final objective value will be written ('ResultObj').  The direction property ensures that the file is 'exported'. The binding property within the total objective definition 'binds' the objective to the obj_data source. The output property, finalValue:[], exports the final objective function value to the ResultObj table within the file ProductMixAccess.accdb.",
-      "type": "odbc",
-      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
-      "selection": "ResultObj",
-      "direction": "export"
-    }
-  },
-  "data": {
-    "comment": "Binds the datasources to data component.",
-    "profit": {
-      "comment": "Binds the values in the profits column in the profit_data datasource to profit data component. If valueCol property is missing, RASON assumes the value column is the last column in the table.",
-      "binding": "profit_data"
-    },
-    "invent": {
-      "comment": "Binds the values in the inventory column in the invent_data datasource to invent data component.",
-      "binding": "invent_data"
-    },
-    "parts2": {
-      "comment": "Binds the values in the qty column in the parts_data datasource to parts2 data component.",
-      "binding": "parts_data"
-    }
-  },
-  "formulas": {
-    "comment": "Use this section to calculate intermediate formulas to be used within the constraints and objective sections.",
-    "piv_parts": {
-      "formula": "PIVOT(parts2, { 'prods' }, { 'parts' })"
-    }
-  },
-  "variables": {
-    "comment": "Decision Variables",
-    "x": {
-      "comment": "The amount of products to produce, x[1] = TVs, x[2] = Stereos, x[3] = Speakers",
-      "dimensions": [ "prods" ],
-      "valuecol": "initials",
-      "lower": 0,
-      "finalValue": []
-    }
-  },
-  "constraints": {
-    "comment": "Constraints",
-    "c": {
-      "comment": "Generates 5 constraints that calculate the number of parts used in creating the three products, then sets each constraint equal to the amount of each part in inventory.",
-      "dimensions": [ "parts" ],
-      "formula": "MMULT(piv_parts, x)",
-      "upper": "invent",
-      "finalValue": []
-    }
-  },
-  "objective": {
-    "comment": "objective function",
-    "total": {
-      "comment": "Calculates the profit by multiplying the profit per unit of each product by the final variable values.",
-      "formula": "sumproduct(x, profit)",
-      "type": "maximize",
-      "finalValue": []
-    }
-  }
-}
+{
+  "modelName": "RGProductMixSQL11",
+  "modelDescription": "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.",
+  "modelType": "optimization",
+  "datasources": {
+    "comment": "Imports data from outside datasources. ValueCols must follow indexCols in selections",
+    "parts_data": {
+      "comment": "Imports the parts data.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "SELECT Parts as parts, Products as prods, Qty as qty FROM Parts ORDER BY ID",
+      "indexCols": [ "parts", "prods" ],
+      "valueCols": [ "qty" ],
+      "direction": "import"
+    },
+    "invent_data": {
+      "comment": "Imports the inventory data.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "SELECT Parts as parts, Inventory as inventory FROM Inventory ORDER BY ID",
+      "indexCols": [ "parts" ],
+      "valueCols": [ "inventory" ],
+      "direction": "import"
+    },
+    "profit_data": {
+      "comment": "Imports the profit per unit data.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "SELECT Products as prods, Profit as profit FROM Profits ORDER BY ID",
+      "indexCols": [ "prods" ],
+      "valueCols": [ "profit" ],
+      "direction": "import"
+    },
+    "vars_data": {
+      "comment": "The vars_data data source performs a dual function by first importing the decision variable initial values from the Access database and then saving the final variable values back to that same file. The first property, type, specifies the type of file where the data is being imported/exported ('msaccess'), the second property, connection, specifies the file name within quotes ('ProductMixAccess.accdb') and the third property, selection, imports two fields from the Profits table in order by ID ('SELECT Products, Initials FROM Profits ORDER BY ID). The 4th property, indexCols, indexes the data by the prods dimension while the 5th property, valueCols, imports the actual numerical data. The direction property ensures that the initial variable values are imported and the final variable values are exported using direction: 'import/export'. Within variables, the x array definition uses the valueCol property to pass the initial variable values and the binding property to bind to the vars_data data source. The final variable values (requested using the output property finalValues:[] within the x array definition) will be appended to the Profits table.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "SELECT Products as prods, Initials as initials FROM Profits ORDER BY ID",
+      "indexCols": [ "prods" ],
+      "valueCols": [ "initials" ],
+      "direction": "import/export"
+    },
+    "fcns_data": {
+      "comment": "The fcns_data datasource, exports the final constraint values to the Access data base file, ProductMixAccess.accdb. The first property, type: 'msaccess', specifies the type of file where the data is being imported/exported. Alternatively, 'access' or 'odbc' could have been passed instead of 'msaccess'. The second property, connection, specifies the file name within quotes ('ProductMixAcess.accdb'). The 3rd property, selection: 'ResultFcns', creates a table within the Access database, where the final constraint values will be saved. The direction property ensures that the file is 'exported'. Within the c constraint definition, the constraint block is bound to the fcns_data data source by the binding property. The output property, finalValue:[], will export the final constraint values to the ResultsFcns table within the file, ProductMixAccess.accdb.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "ResultFcns",
+      "direction": "export"
+    },
+    "obj_data": {
+      "comment": "The obj_data datasource exports the final objective value to ProductMixAccess.accdb. Again the first property, type, specifies the file type ('msaccess'), the second property, connection, specifies the file name ('ProductMixAccess.accdb') and the third property, selection, specifies the table where the final objective value will be written ('ResultObj').  The direction property ensures that the file is 'exported'. The binding property within the total objective definition 'binds' the objective to the obj_data source. The output property, finalValue:[], exports the final objective function value to the ResultObj table within the file ProductMixAccess.accdb.",
+      "type": "odbc",
+      "connection": "Driver={SQL Server};Server=tcp:solver.database.windows.net,1433;Database=Rason;Uid=rasonread;Pwd=Rason1234;Encrypt=yes;TrustServerCertificate=no;Connection Timeout=30;",
+      "selection": "ResultObj",
+      "direction": "export"
+    }
+  },
+  "data": {
+    "comment": "Binds the datasources to data component.",
+    "profit": {
+      "comment": "Binds the values in the profits column in the profit_data datasource to profit data component. If valueCol property is missing, RASON assumes the value column is the last column in the table.",
+      "binding": "profit_data"
+    },
+    "invent": {
+      "comment": "Binds the values in the inventory column in the invent_data datasource to invent data component.",
+      "binding": "invent_data"
+    },
+    "parts2": {
+      "comment": "Binds the values in the qty column in the parts_data datasource to parts2 data component.",
+      "binding": "parts_data"
+    }
+  },
+  "formulas": {
+    "comment": "Use this section to calculate intermediate formulas to be used within the constraints and objective sections.",
+    "piv_parts": {
+      "formula": "PIVOT(parts2, { 'prods' }, { 'parts' })"
+    }
+  },
+  "variables": {
+    "comment": "Decision Variables",
+    "x": {
+      "comment": "The amount of products to produce, x[1] = TVs, x[2] = Stereos, x[3] = Speakers",
+      "dimensions": [ "prods" ],
+      "valuecol": "initials",
+      "lower": 0,
+      "finalValue": []
+    }
+  },
+  "constraints": {
+    "comment": "Constraints",
+    "c": {
+      "comment": "Generates 5 constraints that calculate the number of parts used in creating the three products, then sets each constraint equal to the amount of each part in inventory.",
+      "dimensions": [ "parts" ],
+      "formula": "MMULT(piv_parts, x)",
+      "upper": "invent",
+      "finalValue": []
+    }
+  },
+  "objective": {
+    "comment": "objective function",
+    "total": {
+      "comment": "Calculates the profit by multiplying the profit per unit of each product by the final variable values.",
+      "formula": "sumproduct(x, profit)",
+      "type": "maximize",
+      "finalValue": []
+    }
+  }
+}

package/examples/rason-features/UserGuide/UGAirlineHubCSV.json

@@ -1,67 +1,67 @@
-{
-  "modelName": "UGAirlineHubCSV",
-  "modelDescription": "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.",
-  "modelType": "optimization",
-  "engineSettings": {
-    "comment": "Since this model is nonlinear, the GRG Nonlinear engine is selected as the solving engine.",
-    "engine": "GRG Nonlinear"
-  },
-  "datasources": {
-    "comment": "The dataSources section defines a source from which the data values will be imported, in this case a comma-separated-value (CSV) file named AirlineHubData.csv.  The data source defines an index column, CITIES, which is used to dimension the array of constraints, c.",
-    "city_data": {
-      "type": "csv",
-      "connection": "AirlineHubData.csv",
-      "indexCols": [ "cities" ],
-      "valueCols": [ "dx", "dy" ],
-      "direction": "import"
-    }
-  },
-  "variables": {
-    "comment": "This example contains three decision variables x, y and z. The x and y variables will hold the final x and y coordinates of the proposed firehouse location. The third variable, z, will be minimized in the objective function. Since the finalValue property is present, the final value of each variable will be returned in the results.",
-    "x": {
-      "comment": "The x coordinate of the proposed airport location. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
-      "value": 1.0,
-      "finalValue": []
-    },
-    "y": {
-      "comment": "The y coordinate of the proposed airport location. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
-      "value": 1.0,
-      "finalValue": []
-    },
-    "z": {
-      "comment": "The z variable that will be minimized in the objective function. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
-      "value": 1.0,
-      "finalValue": []
-    }
-  },
-  "data": {
-    "comment": "In the data section of the model, we bind the names dx and dy to 1-dimensional arrays from the corresponding value columns dx and dy. This model can be used to solve many different instances of this facility location problem, for a variable number of cities.",
-    "dx": {
-      "comment": "x coordinates of each city bound to the dx data array.",
-      "binding": "city_data",
-      "valueCol": "dx"
-    },
-    "dy": {
-      "comment": "y coordinates of each city bound to the dy data array.",
-      "binding": "city_data",
-      "valueCol": "dy"
-    }
-  },
-  "constraints": {
-    "c": {
-      "comment": "There will be 1 constraint per city regional airport. The distance formula is used to calculate the distance bewteen the proprosed hub's location and the city regional airport.",
-      "dimensions": [ "cities", 1 ],
-      "upper": 0,
-      "formula": "sqrt((x - dx)^2 + (y - dy)^2) - z"
-    }
-  },
-  "objective": {
-    "comment": "The objective function minimizes the z variable creating a squashing effect that pushes the distances between the proposed airling hub and the distance between each city airport to be as small as possible.",
-    "obj": {
-      "comment": "Since the finalValue property is present, the final value of the objective function will be returned in the results. Note that the final value for the z variable and the objective will be equal.",
-      "type": "minimize",
-      "formula": "z",
-      "finalValue": []
-    }
-  }
-}
+{
+  "modelName": "UGAirlineHubCSV",
+  "modelDescription": "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.",
+  "modelType": "optimization",
+  "engineSettings": {
+    "comment": "Since this model is nonlinear, the GRG Nonlinear engine is selected as the solving engine.",
+    "engine": "GRG Nonlinear"
+  },
+  "datasources": {
+    "comment": "The dataSources section defines a source from which the data values will be imported, in this case a comma-separated-value (CSV) file named AirlineHubData.csv.  The data source defines an index column, CITIES, which is used to dimension the array of constraints, c.",
+    "city_data": {
+      "type": "csv",
+      "connection": "AirlineHubData.csv",
+      "indexCols": [ "cities" ],
+      "valueCols": [ "dx", "dy" ],
+      "direction": "import"
+    }
+  },
+  "variables": {
+    "comment": "This example contains three decision variables x, y and z. The x and y variables will hold the final x and y coordinates of the proposed firehouse location. The third variable, z, will be minimized in the objective function. Since the finalValue property is present, the final value of each variable will be returned in the results.",
+    "x": {
+      "comment": "The x coordinate of the proposed airport location. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
+      "value": 1.0,
+      "finalValue": []
+    },
+    "y": {
+      "comment": "The y coordinate of the proposed airport location. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
+      "value": 1.0,
+      "finalValue": []
+    },
+    "z": {
+      "comment": "The z variable that will be minimized in the objective function. Since the finalValue property is present, the final value of the objective function will be returned in the results.",
+      "value": 1.0,
+      "finalValue": []
+    }
+  },
+  "data": {
+    "comment": "In the data section of the model, we bind the names dx and dy to 1-dimensional arrays from the corresponding value columns dx and dy. This model can be used to solve many different instances of this facility location problem, for a variable number of cities.",
+    "dx": {
+      "comment": "x coordinates of each city bound to the dx data array.",
+      "binding": "city_data",
+      "valueCol": "dx"
+    },
+    "dy": {
+      "comment": "y coordinates of each city bound to the dy data array.",
+      "binding": "city_data",
+      "valueCol": "dy"
+    }
+  },
+  "constraints": {
+    "c": {
+      "comment": "There will be 1 constraint per city regional airport. The distance formula is used to calculate the distance bewteen the proprosed hub's location and the city regional airport.",
+      "dimensions": [ "cities", 1 ],
+      "upper": 0,
+      "formula": "sqrt((x - dx)^2 + (y - dy)^2) - z"
+    }
+  },
+  "objective": {
+    "comment": "The objective function minimizes the z variable creating a squashing effect that pushes the distances between the proposed airling hub and the distance between each city airport to be as small as possible.",
+    "obj": {
+      "comment": "Since the finalValue property is present, the final value of the objective function will be returned in the results. Note that the final value for the z variable and the objective will be equal.",
+      "type": "minimize",
+      "formula": "z",
+      "finalValue": []
+    }
+  }
+}