Lines Matching refs:any

11 - {any}`ch_vectors` (`Vec`);
12 - (generally sparse) {any}`ch_matrices` (`Mat`)
13 - {any}`ch_ksp` (`KSP`);
16 - {any}`ch_snes` (`SNES`);
17 - {any}`ch_ts` for solving time-dependent (nonlinear) PDEs, including
20 - scalable {any}`ch_tao` including a rich set of gradient-based optimizers,
22 - {any}ch_regressor (`PetscRegressor)`
23 - {any}`ch_dmbase` code for managing interactions between mesh data structures and vectors,
40 of PETSc. {any}`fig_library` is a diagram of some
79 useful for exploring the PETSc source code. Details of this feature are provided in {any}`sec_devel…
85 {any}`ch_fortran` provides a discussion of the differences between
118 See {any}`handson` to immediately jump in and run PETSc code.
141 running any PETSc program with the option `-help`.
143 - `-log_view` - summarize the program’s performance (see {any}`ch_profiling`)
148   {any}`detecting_memory_problems`,
151   {any}`detecting_memory_problems`,
154   {any}`sec_debugging`, for more information on
176 directory. {any}`sec_options` provides details
244 ! within any subroutine
250 a complete error traceback. See {any}`sec_error2` for more details on PETSc error handling.
294 See {any}`sec_fortran_includes`
301 As shown in {any}`sec_simple`, the user can
307 of the options database may be found in {any}`sec_options`.
342 in Chapter {any}`ch_vectors`.
350 {any}`sec_complex` discusses the use of complex
396 {any}`ch_matrices` discusses various matrix formats as
419 database, which is discussed in {any}`sec_options`. Through this database, the
422 routines, etc. (see, e.g., {any}`sec_profiling_programs`).
424 {any}`ch_ksp` describes in detail the `KSP` package,
432 {any}`ch_snes` describes the nonlinear
448 {any}`sec_fortran_errors` for details regarding error checking
516 …mple, Intel AVX-like instructions ({any}`sec_cpu_simd`) and Unix threads, often managed by using O…
517 …lso support the lower two levels via kernel functions ({any}`sec_gpu_kernels`) and streams ({any}`…
519 CPUs and/or GPUs and using MPI for communication ({any}`sec_mpi`).
539 Recall that the user must specify a communicator upon creation of any
563 {any}`sec_simple`. Note that the user interface
567 {any}`sec_simple` and
626 …d linear solvers may be accessed from a sequential or non-MPI OpenMP program, see {any}`sec_pcmpi`.
674 configuration process. See {any}`sec_writing_application_codes` for
697 activity. {any}`ch_profiling` provides details about
762 `$PETSC_DIR/src/<library>/tutorials` where `<library>` denotes any
785   >    set for any of these approaches.
812   >    set for any of these approaches.
874 represent any of these objects. Objects are created with
903 The abstract class `TS` can embody any ODE/DAE integrator scheme.
922 The object's type (implementation class) or subclass can also be changed at any time simply by call…
980 Note that we leveraged this functionality in the MPI example above ({any}`sec_mpi`) by calling `Mat…
1078 See {any}`fig_taocallbacks` for a cartoon on callbacks in `Tao`.