Lines Matching refs:object

8 functions provided would be attached to the appropriate solver object,
10 object and `TS` callbacks to the `TS` object. This is not the case.
12 `DM` object associated with the solver object. This is also not the
14 `DMXXX` object (`XXX` is `KSP`, `SNES`, or `TS`) that is
15 attached to the `DM` that is attached to the `XXX` solver object.
19 `XXX`/`DM` objects share a common `DMXXX` object.
28 objects share a common `DMKSP` object. The code to access the inner
29 `DMKSP` object is
38 To obtain a new DMKSP object for which you can change the callback
48 This results in the object organization as indicated in the following figure
56 The `DMKSP` object is essentially the list of callback functions and
83 user are passed down to the inner `DMKSP` object. For each user level
103 the `DMXXX` object via `DMGetDMXXXWrite(DM,DMXXX*)` and sets the
104 function callback and its context into the `DMXXX` object.
121 the object unless the `DM` associated with the `DMXXX` object is the
122 original `DM` that the `DMXXX` object was created with. This can be
169 attach to the `DM` object two functions that are automatically called
170 when the object is coarsened or refined. The hooks
206 The `TS` object manages its callback functions in a way similar to
208 implementations so in theory the `DMTS` object is currently unneeded.