Stay organized with collectionsSave and categorize content based on your preferences.
Status
Status of the solution. Before solving a problem the status will beNOT_SOLVED;
afterwards it will take any of the other values depending if it successfully found a solution and
if the solution is optimal.
To call an enum, you call its parent class, name, and property. For example,LinearOptimizationService.Status.OPTIMAL.
Properties
Property
Type
Description
OPTIMAL
Enum
Status when an optimal solution has been found.
FEASIBLE
Enum
Status when a feasible (not necessarily optimal) solution has been found.
INFEASIBLE
Enum
Status when the current model is unfeasible (has no solution).
UNBOUNDED
Enum
Status when the current model is unbound.
ABNORMAL
Enum
Status when it failed to find a solution for unexpected reasons.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-12-02 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eStatus\u003c/code\u003e property indicates the state of a Linear Optimization solution, initially set to \u003ccode\u003eNOT_SOLVED\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAfter attempting to solve the problem, the status changes to reflect if a solution was found and if it is optimal (\u003ccode\u003eOPTIMAL\u003c/code\u003e, \u003ccode\u003eFEASIBLE\u003c/code\u003e, \u003ccode\u003eINFEASIBLE\u003c/code\u003e, \u003ccode\u003eUNBOUNDED\u003c/code\u003e, \u003ccode\u003eABNORMAL\u003c/code\u003e, \u003ccode\u003eMODEL_INVALID\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003eAccessing the status enum values is done using the format: \u003ccode\u003eLinearOptimizationService.Status.[property name]\u003c/code\u003e, such as \u003ccode\u003eLinearOptimizationService.Status.OPTIMAL\u003c/code\u003e.\u003c/p\u003e\n"]]],["The document outlines the `Status` of a solution within a system, initially `NOT_SOLVED` before any problem-solving attempt. After solving, the status changes to reflect the outcome. Possible statuses include `OPTIMAL` (best solution found), `FEASIBLE` (a solution exists, but may not be the best), `INFEASIBLE` (no solution), `UNBOUNDED` (model is unlimited), `ABNORMAL` (failed for unexpected reasons), and `MODEL_INVALID` (invalid model). Enums are accessed using `ParentClass.Name.Property`, like `LinearOptimizationService.Status.OPTIMAL`.\n"],null,["# Enum Status\n\nStatus\n\nStatus of the solution. Before solving a problem the status will be `NOT_SOLVED`;\nafterwards it will take any of the other values depending if it successfully found a solution and\nif the solution is optimal.\n\nTo call an enum, you call its parent class, name, and property. For example, `\nLinearOptimizationService.Status.OPTIMAL`. \n\n### Properties\n\n| Property | Type | Description |\n|-----------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|\n| `OPTIMAL` | `Enum` | Status when an optimal solution has been found. |\n| `FEASIBLE` | `Enum` | Status when a feasible (not necessarily optimal) solution has been found. |\n| `INFEASIBLE` | `Enum` | Status when the current model is unfeasible (has no solution). |\n| `UNBOUNDED` | `Enum` | Status when the current model is unbound. |\n| `ABNORMAL` | `Enum` | Status when it failed to find a solution for unexpected reasons. |\n| `MODEL_INVALID` | `Enum` | Status when the model is invalid. |\n| `NOT_SOLVED` | `Enum` | Status when [LinearOptimizationEngine.solve()](/apps-script/reference/optimization/linear-optimization-engine#solve()) has not been called yet. |"]]
