| /petsc/src/sys/perfstubs/ |
| H A D | pstimer.c | 236 void ** objects = (void**)calloc(num_tools_registered, sizeof(void*)); in ps_timer_create_() local
238 for (i = 0 ; i < num_tools_registered ; i++) objects[i] = timer_create_functions[i](timer_name); in ps_timer_create_()
239 return (void*)(objects); in ps_timer_create_()
245 void ps_timer_destroy_(void *objects) { in ps_timer_destroy_() argument
247 free(objects); in ps_timer_destroy_()
259 void ** objects = (void**)(timer); in ps_timer_start_() local
261 for (i = 0; i < num_tools_registered ; i++) timer_start_functions[i](objects[i]); in ps_timer_start_()
273 void ** objects = (void**)(timer); in ps_timer_stop_() local
275 for (i = 0; i < num_tools_registered ; i++) timer_stop_functions[i](objects[i]); in ps_timer_stop_()
308 void ** objects = (void**)calloc(num_tools_registered, sizeof(void*)); in ps_create_counter_() local
[all …]
|
| /petsc/src/binding/petsc4py/conf/ |
| H A D | epydoc.cfg | 3 # The list of objects to document. Objects can be named using
5 # Alases for this option include "objects" and "values".
35 # Whether or not parsing should be used to examine objects.
38 # Whether or not introspection should be used to examine objects.
54 # The format for showing inheritance objects.
114 # Use the records in this file to resolve objects in the API named NAME.
115 #external-api-file: epydoc:api-objects.txt
|
| /petsc/lib/petsc/bin/ |
| H A D | PetscBinaryIO.py | 440 objects = []
446 objects.append(self.readVec(fid))
448 objects.append(self.readIS(fid))
450 objects.append(self.readMat(fid,mattype))
452 objects.append(self.readReal(fid))
461 return tuple(objects)
464 def writeBinaryFile(self, fid, objects): argument
479 for petscobj in objects:
|
| /petsc/doc/developers/ |
| H A D | objects.md | 84 All PETSc objects (derived from the base class `PetscObject`) have the following common header stru…
170 error checking. Each different class of objects has its value for
245 object has any other objects composed with it, the `PetscObjectDestroy()` function is called on the…
277 Since the object composition allows one to compose PETSc objects
278 with PETSc objects, PETSc provides the
297 <a href="PETSC_DOC_OUT_ROOT_PLACEHOLDER/src/sys/objects/olist.c.html">src/sys/objects/olist.c</a>
309 from which linked lists of composed objects may be constructed. The
310 routines to manipulate these elementary objects are
324 <a href="PETSC_DOC_OUT_ROOT_PLACEHOLDER/src/sys/objects/inherit.c.html">src/sys/objects/inherit.c</…
379 functions into PETSc objects, it is also used to allow registration of
[all …]
|
| H A D | design.md | 9 objects
|
| /petsc/doc/manualpages/doctext/ |
| H A D | doctextcommon.txt | 9 Operations using the _same_ `PetscDeviceContext` which access objects or memory regions
30 Operations using _separate_ `PetscDeviceContext`s which access _separate_ objects or
49 objects themselves are always valid (though their member variables `PetscFoo->data`
|
| /petsc/doc/manualpages/MANSECHeaders/ |
| H A D | BM | 3 Benchmark (`BM`) objects manage running PETSc benchmarks
|
| H A D | PF | 3 PETSc functions (`PF` objects) are used to compute grid functions, element functions, etc.
|
| H A D | AO | 3 Application Orderings (`AO`) are objects that manage mappings between different global orderings. U…
|
| H A D | DMPRODUCT | 3 The `DMPRODUCT` subclass of `DM` represents a (local) Cartesian product of other `DM` objects.
|
| H A D | IS | 3 `IS` objects are used to index into vectors and matrices and to setup vector scatters. Users guide …
|
| H A D | Viewer | 4 PETSc viewers `PetscViewer` print, display, and export information and data from PETSc objects in a…
|
| H A D | Characteristic | 3 `Characteristic` objects are used to manage parallel Semi-Lagrangian methods (method of characteris…
|
| H A D | Mat | 3 PETSc matrices (`Mat` objects) are used to store Jacobians and other sparse matrices
|
| H A D | DM | 3 `DM` objects are used to manage communication between the algebraic structures in PETSc (`Vec` and …
|
| /petsc/doc/changes/ |
| H A D | 215.md | 55 - Turned off logging of objects and actions by default - saves
57 - Reduce memory usage for DA and SDA objects
|
| H A D | 2022.md | 34 - Changed the internal structure of the PETSc objects. This will not
44 These allow the user to attach objects and functions to any PETSc
172 - If you have stored PETSc objects in Fortran integer arrays, such
180 - PETSc objects can now be passed between C and Fortran directly.
183 `PetscFortranObjectToCObject()` to translate the objects between
|
| H A D | 213.md | 12 - updates to DA - which delays allocation of internal objects until
|
| /petsc/share/petsc/matlab/ |
| H A D | PetscBinaryRead.m | 24 …urn a MATLAB cell array containing the first cnt objects in the file, use 10,000 to read in all ob…
27 % Examples: A = PetscBinaryRead('myfile','cell',10000); read all objects in file
28 % A = PetscBinaryRead(1024,'cell',2); read two objects from socket
|
| /petsc/src/binding/petsc4py/docs/source/ |
| H A D | overview.rst | 50 may be chosen at runtime. Those objects are managed through handles to
55 a particular family of objects and the operations one would like to
56 perform on these objects. These components provide the functionality
|
| /petsc/src/binding/petsc4py/src/petsc4py/PETSc/ |
| H A D | cyclicgc.pxi | 60 """Clean up unused PETSc objects.
84 """Print summary of the garbage PETSc objects.
|
| /petsc/src/snes/tutorials/output/ |
| H A D | ex19_10.out | 57 Solver info for each split is in the following KSP objects:
68 Local solver information for first block is in the following KSP and PC objects on rank 0:
114 Local solver information for first block is in the following KSP and PC objects on rank 0:
160 Local solver information for first block is in the following KSP and PC objects on rank 0:
206 Local solver information for first block is in the following KSP and PC objects on rank 0:
|
| H A D | ex19_9.out | 64 Solver info for each split is in the following KSP objects:
75 Local solver information for first block is in the following KSP and PC objects on rank 0:
121 Local solver information for first block is in the following KSP and PC objects on rank 0:
167 Local solver information for first block is in the following KSP and PC objects on rank 0:
213 Local solver information for first block is in the following KSP and PC objects on rank 0:
|
| /petsc/src/ksp/ksp/tutorials/output/ |
| H A D | ex84_1.out | 64 Solver info for each split is in the following KSP objects:
75 Local solver information for first block is in the following KSP and PC objects on rank 0:
121 Local solver information for first block is in the following KSP and PC objects on rank 0:
196 Solver info for each split is in the following KSP objects:
207 Local solver information for first block is in the following KSP and PC objects on rank 0:
253 Local solver information for first block is in the following KSP and PC objects on rank 0:
|
| /petsc/lib/petsc/bin/maint/abi-compliance-checker/ |
| H A D | README.md | 19 …red objects of a library. The ABI dump for a library can also be created by the ABI Dumper tool (h…
|