Lines Matching full:blocks
65 // blocks from a Problem after adding them.
107 // squares problem containing 3 parameter blocks of sizes 3, 4 and 5
144 // Problem. If you only remove parameter blocks from the Problem
148 // residual blocks that depend on it. The increase in memory usage is an
174 // parameter blocks it expects. The function checks that these match
175 // the sizes of the parameter blocks listed in parameter_blocks. The
180 // The user has the option of explicitly adding the parameter blocks
183 // blocks if they are not present, so calling AddParameterBlock
196 // regardless of how many residual blocks refer to them.
276 // residual blocks that depend on the parameter are also removed, as
306 // Set the local parameterization for one of the parameter blocks.
315 // Number of parameter blocks in the problem. Always equals
320 // sizes of all the parameter blocks.
323 // Number of residual blocks in the problem. Always equals
328 // sizes of all of the residual blocks.
340 // parameter blocks currently in the problem. After this call,
351 // The set of parameter blocks for which evaluation should be
353 // blocks occur in the gradient vector and in the columns of the
356 // blocks. Generally speaking the parameter blocks will occur in
358 // may change if the user removes any parameter blocks from the
362 // used to add parameter blocks to the Problem. These parameter
367 // The set of residual blocks to evaluate. This vector determines
371 // blocks. If this vector is empty, then it is assumed to be equal
372 // to a vector containing ALL the residual blocks. Generally
373 // speaking the residual blocks will occur in the order in which
375 // user removes any residual blocks from the problem.
378 // Even though the residual blocks in the problem may contain loss
390 // residual blocks and parameter blocks are used is controlled by
414 // is the sum of the sizes of all the parameter blocks. If a
