Pseudo solutions may not be LP feasible. Duals/reduced costs are not
available (the LP solver failed at this node).
Do not add "user cuts" here (that strengthen LP solution but don't change
feasible region), add only "lazy constraints" (cut off integer solutions).
TODO(user): maybe this can be abstracted away.
[[["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-08-06 UTC."],[[["`ScipConstraintHandlerContext` provides methods for interacting with SCIP solver within constraint handlers."],["It allows access to current node information, the SCIP solver instance, and the current solution."],["Users can retrieve the value of variables and the total number of nodes processed."],["It helps in distinguishing between pseudo and true solutions to apply appropriate constraints."]]],["The `ScipConstraintHandlerContext` class provides methods for interacting with the SCIP solver. Key actions include retrieving the `CurrentNodeId` and `NumNodesProcessed`, accessing the underlying `SCIP*` solver instance. `VariableValue` gets the value of a variable. `is_pseudo_solution` checks if the solution is a pseudo solution where duals/reduced costs are not available, and suggests only adding lazy constraints. The class can be created with an instance of `SCIP`, a solution and a boolean.\n"]]
