Lines Matching full:residual
64 // A ResidualBlockId is an opaque handle clients can use to remove residual
70 // as "residuals"), where each residual is a function of some subset
79 // r_ij is residual number i, component j; the residual is a
81 // example, in a structure from motion problem a residual
84 // camera, point pair. The residual would have two
93 // residual depends only on a small number number of parameters, even
102 // residual will depend only on 9 parameters (3 for the point, 6 for
108 // respectively and two residual terms of size 2 and 6:
148 // residual blocks that depend on it. The increase in memory usage is an
172 // Add a residual block to the overall cost function. The cost
194 // them in another residual block. The destructor takes care to call
196 // regardless of how many residual blocks refer to them.
275 // problem (similar to cost/loss functions in residual block removal). Any
276 // residual blocks that depend on the parameter are also removed, as
283 // WARNING: Removing a residual or parameter block will destroy the implicit
289 // Remove a residual block from the problem. Any parameters that the residual
291 // residual block will not get deleted immediately; won't happen until the
294 // WARNING: Removing a residual or parameter block will destroy the implicit
323 // Number of residual blocks in the problem. Always equals
327 // The size of the residual vector obtained by summing over the
328 // sizes of all of the residual blocks.
367 // The set of residual blocks to evaluate. This vector determines
370 // assumed to be equal to the vector containing all the residual
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
