Expression Constraints
Internal Table Name: AggregateExpressionConstraints
Name
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: ExpressionName
Type: Short Text (100)
This field is the name of the expression constraint.
Coefficient 1
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: Coefficient1
Type: Short Text (100)
Use this field to apply a multiplier to the expression you enter in Expression 1.
Expression 1
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: Expression1
Type: Short Text (100)
Enter the name of the first expression in the expression constraint record. This will be one of the following:
- The Name from a Flow Constraint, Inventory Constraint, Production Constraint
- The Name from an Expression Constraint
You can define Expression 1 or Expression 2 or both, as needed.
Handling invalid expressions:
-
If Expression 1 is invalid, it will cause Expression 2 defined in the Expression Constraint to be invalid.
-
Similarly if Expression 2 is invalid, it will cause Expression 1 defined in the Expression Constraint to be invalid.
Once an expression is deemed to be invalid, it is invalid in all Expression Constraint records. For example, assume the following records where Expression 1 (No_Prod) in the Test 3 record is invalid:
Name | Coefficient 1 | Expression 1 | Coefficient 2 | Expression 2 | Constraint Type | Constraint Value | Status |
---|---|---|---|---|---|---|---|
Test1 | 1 | All_Flow | -1 | All_Prod | Min | 1 | Include |
Test2 | 2 | All_Prod | -2 | All_Process | Min | 2 | Include |
Test3 | 3 | No_Prod | -3 | All_Inv | Min | 3 | Include |
Test4 | 4 | All_Flow | -4 | All_Inv | Min | 4 | Include |
In this case, the invalid Expression 1 results in Expression 2 (All_Inv) being invalid in Test3. Since All_Inv is now invalid, the Test4 Expression Constraint is also considered invalid. Neither Test3 nor Test4 will be written when the model is run.
Coefficient 2
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: Coefficient2
Type: Short Text (100)
Use this field to apply a multiplier to the expression you enter in Expression 2.
Expression 2
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: Expression2
Type: Short Text (100)
Enter the name of the second expression in the expression constraint record. This will be one of the following:
- The Name from a Flow Constraint, Inventory Constraint, Production Constraint
- The Name from an Expression Constraint
You can define Expression 1 or Expression 2 or both, as needed.
Handling invalid expressions:
-
If Expression 1 is invalid, it will cause Expression 2 defined in the Expression Constraint to be invalid.
-
Similarly if Expression 2 is invalid, it will cause Expression 1 defined in the Expression Constraint to be invalid.
Once an expression is deemed to be invalid, it is invalid in all Expression Constraint records. For example, assume the following records where Expression 1 (No_Prod) in the Test 3 record is invalid:
Name | Coefficient 1 | Expression 1 | Coefficient 2 | Expression 2 | Constraint Type | Constraint Value | Status |
---|---|---|---|---|---|---|---|
Test1 | 1 | All_Flow | -1 | All_Prod | Min | 1 | Include |
Test2 | 2 | All_Prod | -2 | All_Process | Min | 2 | Include |
Test3 | 3 | No_Prod | -3 | All_Inv | Min | 3 | Include |
Test4 | 4 | All_Flow | -4 | All_Inv | Min | 4 | Include |
In this case, the invalid Expression 1 results in Expression 2 (All_Inv) being invalid in Test3. Since All_Inv is now invalid, the Test4 Expression Constraint is also considered invalid. Neither Test3 nor Test4 will be written when the model is run.
Constraint Type
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: ExpressionType
Type: Short Text (100)
One of Min, Cond Min, Max, Fixed, Define.
Enter the type of expression constraint:
- Min – The value specified in the Constraint Value must be reached.
- Max – The value specified in the Constraint Value cannot be exceeded.
- Fixed – The value specified in the Constraint Value must be used.
- Cond Min – The value specified in the Constraint Value must be reached or none at all.
- Define – Network Optimization does not use the Constraint Value to satisfy the constraint. This setting can be used when you are nesting Expression Constraints.
Default: Min
Constraint Value
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: ExpressionRequirement
Type: Short Text (100)
For all Constraint Types other than Define, enter the value that acts as the constraint; that is, the minimum, maximum or fixed value.
Status
Technology: NO
Table: AggregateExpressionConstraints
Internal Name: ExpressionStatus
Type: Short Text (25)
One of Include, Exclude.
Select one of:
- Include – to include the expression constraint during optimization.
- Exclude – to exclude the expression constraint during optimization.
Default: Include
Last modified: Wednesday May 15, 2024