Manuals/calci/Exampleslp - Revision history

Sahiti at 11:30, 1 October 2018

2018-10-01T11:30:45Z

Sahiti at 11:30, 1 October 2018

2018-10-01T11:30:04Z

Sahiti at 11:23, 1 October 2018

2018-10-01T11:23:02Z

Sahiti at 08:23, 1 October 2018

2018-10-01T08:23:02Z

Sahiti at 08:22, 1 October 2018

2018-10-01T08:22:35Z

Sahiti at 08:21, 1 October 2018

2018-10-01T08:21:51Z

Sahiti at 08:19, 1 October 2018

2018-10-01T08:19:18Z

Sahiti at 08:18, 1 October 2018

2018-10-01T08:18:57Z

Sahiti at 08:18, 1 October 2018

2018-10-01T08:18:30Z

Sahiti: /* DESCRIPTION */

2018-10-01T08:18:05Z

DESCRIPTION

@@ Line 344: / Line 344: @@
 {| class="wikitable"
 |-
 ! !! Alloy1 !! Alloy2 !! Alloy3 !! Alloy4  !! Alloy5

@@ Line 343: / Line 343: @@
 alloys that should be blended to produce a new alloy at minimum cost.<br>
-        Alloy 1 Alloy 2 Alloy 3 Alloy 4 Alloy 5
+{| class="wikitable"
-%Tin         60 25 45 20 50
+|+Spreadsheet
-%Zinc        10 15 45 50 40
+|-
-%Lead        30 60 10 30 10
+! !! Alloy1 !! Alloy2 !! Alloy3 !! Alloy4  !! Alloy5
-Cost ($/lb.) 22 20 25 24 27
+|-
 <div id="z3lp7" style="font-size:16px">'''z3 code: Mining Problem'''</div>

← Older revision		Revision as of 11:23, 1 October 2018
Line 336:		Line 336:
	b: 66.66666667,		b: 66.66666667,
	a: 33.33333333 }</source>		a: 33.33333333 }</source>
		+
		+
		+	'''ExampleLP7: Mining Problem<br>'''
		+	The Metalco Company desires to blend a new alloy of 40% tin, 35% zinc, and 25% lead from several available alloys
		+	having the properties given in Table 1. Formulate a linear program whose solution would yield the proportions of these
		+	alloys that should be blended to produce a new alloy at minimum cost.<br>
		+
		+	Alloy 1 Alloy 2 Alloy 3 Alloy 4 Alloy 5
		+	%Tin 60 25 45 20 50
		+	%Zinc 10 15 45 50 40
		+	%Lead 30 60 10 30 10
		+	Cost ($/lb.) 22 20 25 24 27
		+
		+	<div id="z3lp7" style="font-size:16px">'''z3 code: Mining Problem'''</div>
		+	<source lang="cpp">
		+	var solver = require('javascript-lp-solver'),
		+	results,
		+	model = {
		+	"name": "Mining Problem",
		+	"optimize": "Cost",
		+	"opType": "min",
		+	"constraints": {
		+	"Tin": {
		+	"min": 40
		+	},
		+	"Zinc": {
		+	"min": 35
		+	},
		+	"Lead": {
		+	"min": 25
		+	}
		+	},
		+	"variables": {
		+	"Alloy1": {
		+	"Tin": 60,
		+	"Zinc": 10,
		+	"Lead": 30,
		+	"Cost": 22
		+	},
		+	"Alloy2": {
		+	"Tin": 25,
		+	"Zinc": 15,
		+	"Lead": 60,
		+	"Cost": 20
		+	},
		+	"Alloy3": {
		+	"Tin": 45,
		+	"Zinc": 45,
		+	"Lead": 10,
		+	"Cost": 25
		+	},
		+	"Alloy4": {
		+	"Tin": 20,
		+	"Zinc": 50,
		+	"Lead": 30,
		+	"Cost": 24
		+	},
		+	"Alloy5": {
		+	"Tin": 50,
		+	"Zinc": 40,
		+	"Lead": 10,
		+	"Cost": 27
		+	}
		+	},
		+	};
		+	console.log(solver.Solve(model));</source>
		+
		+	<div style="font-size:18px">'''Solution:'''</div>
		+	<source lang="cpp">
		+	{ feasible: true,
		+	result: 23.45652174,
		+	bounded: true,
		+	Alloy1: 0.04347826,
		+	Alloy3: 0.67391304,
		+	Alloy2: 0.2826087 }</source>

@@ Line 4: / Line 4: @@
 *Instead of using arrays to solve these problems, we could create a model in a JavaScript object, and solve it through the object's solve function.
 *Reflecting different domains like Engineering, Statistics, etc.
-*Testing how we can make better solutions to the standard problems compared to other software.<br><br>
+*Testing how we can make better solutions to the standard problems compared to other software.
 *The lp-format input syntax is a set of algebraic expressions and declarations in the following order:
   <objective function>

@@ Line 6: / Line 6: @@
 *Testing how we can make better solutions to the standard problems compared to other software.<br><br>
-*The lp-format input syntax is a set of algebraic expressions and "free", "int", "bin", "sec", "sos" declarations in the following order:
+*The lp-format input syntax is a set of algebraic expressions and declarations in the following order:
   <objective function>
   <constraint>*

@@ Line 14: / Line 14: @@
    to indicate whether you want it to be minimized or maximized. The case is not important, "Max:" or "MAX:" will work as well. Maximization is the default.
    Alternatives are minimise, minimize, maximise, Maximize. The objective function is required, but can be empty.
    <constraint> is an optional constraint name followed by a colon plus a linear combination of variables and constants or (just one) constraint name followed
    by a colon (a range) or (just one) variable name without a colon (a bound), followed by a relational operator, followed again by a linear combination of

@@ Line 18: / Line 18: @@
    by a colon (a range) or (just one) variable name without a colon (a bound), followed by a relational operator, followed again by a linear combination of
    variables and constants, ending with a semicolon. The relational operator can be any of the following: "<" "<=" "=" ">" ">=". There is no semantic difference
-   between "<" and "<=" nor between ">" and ">=" (even for integer variables!).
+   between "<" and "<=" nor between ">" and ">=" (even for integer variables!).<br>
 ==Examples==

@@ Line 10: / Line 10: @@
   <constraint>*
   <declaration>*
 where:
    <objective function> is a linear combination of optional variables and constants, ending with a semicolon, optionally preceded by "max: " or "min: "