Initializing help system before first use

problem.addCuts

Purpose
Adds cuts directly to the matrix at the current node. The cuts will automatically be added to the cut pool. Cuts added to a node will automatically be inherited on any descendant node, unless explicitly deleted with a call to problem.delCuts.
Topic areas
Cuts, Optimizer
Synopsis
problem.addCuts(cuttype, rowtype, rhs, start, colind, cutcoef)
Arguments
cuttype 
Integer array containing the user assigned cut types. The cut types can be any integer chosen by the user, and are used to identify the cuts in other cut manager routines using user supplied parameters. The cut type can be interpreted as an integer or a bitmap - see problem.delCuts.
rowtype 
Character array containing the row types:
L 
indicates a ≤ row;
G 
indicates a ≥ row;
E 
indicates an = row.
rhs 
Double array containing the right hand side elements for the cuts.
start 
Integer array containing offset into the colind and cutcoef arrays indicating the start of each cut. This array has one entry for each cut, plus one more entry indicating where an additional cut would start, if it were present.
colind 
Integer array containing the column indices in the cuts.
cutcoef 
Double array containing the matrix values for the cuts.
Further information
1. The columns and elements of the cuts must be stored contiguously in the colind and cutcoef arrays passed to problem.addCuts. The starting point of each cut must be stored in the start array. To determine the length of the final cut, the start array must have one more element than the number of cuts, with the last element containing the position in colind and cutcoef where an extra cut would start, if it were present. This last entry denotes the number of nonzeros in the added cuts.
2. The cuts added to the matrix are always added at the end of the matrix and the number of rows is always set to the original number rows plust the number of cuts added. If n cuts have been added, then the rows 0,..., ROWS- n- 1 are the original rows, whilst the rows ROWS- n,..., ROWS- 1 are the added cuts. The number of cuts can be found by consulting the CUTS problem attribute.
3. This function should be called only from within callback functions set by either problem.addNodeLPSolvedCallback, problem.addOptnodeCallback, problem.addPreIntsolCallback or problem.addPrenodeCallback.
4. Argument colind may contain xpress.var objects instead of indices.
Related topics
problem.addRows, problem.delCPCuts, problem.delCuts, problem.getCPCutList, problem.getCutList, problem.loadCuts, problem.storeCuts, the Optimizer Reference Manual.

Parent Topic Methods of the class problem

© 2001-2026 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation ("FICO"). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.