Lines Matching refs:be
33 that can be explicitly called from within a program to set compile-time
95 spaces either, and tab characters cannot be used between the option
116 Comments can be placed in the `.petscrc` file by using `#` in the
121 Options prefixes allow specific objects to be controlled from the
133 which can also be used from the command line, e.g. `-options_file my_options.opts`.
201 Usually `pre` should be set to `NULL` (or `PETSC_NULL_CHARACTER`
205 methods used on the individual blocks can be controlled via the options
221 `PetscOptionsMonitorSet()` can be used to provide custom monitors.
238 - Passing in a zero (`0`) for the viewer causes the object to be
240 debugger but should be avoided in source code.
242 the object to be printed to the screen.
244 object to be drawn in a default X window.
246 object to be displayed graphically. See
258 - Vector and matrix objects can be passed to a running MATLAB process
359 The measurements of load balancing can also be done within the program
391 javascript files (they much be in `rootdirectory/js`).
403 PETSc programs may be debugged using one of the two options below.
410 Note that, in general, debugging MPI programs cannot be done in the
416 By default, the debugger will be started in a new
419 the debugger command `cont` should be used to continue execution of
423 correctly handle the MPI startup and should not be used. Not all
427 You can select a subset of the processes to be debugged (the rest just
443 to print a traceback. A new error handler can be put on the stack with
471 handlers can be set with the options `-on_error_abort` or
475 All PETSc calls can be traced (useful for determining where a program is
483 screen. This can also be set with the command
497 this can be prevented with the option `-no_signal_handler` that can be provided on the command line,
509 segmentation violation occurs to be printed. This is handled by them setting a special signal handl…
528 can be used within a program. A `flag` of `PETSC_FP_TRAP_ON` indicates that
529 floating-point exceptions should be trapped, while a value of
530 `PETSC_FP_TRAP_OFF` (the default) indicates that they should be
537 should be used to revert to the previous handling of floating point exceptions before the call to `…
540 These macros are used throughout the PETSc libraries and can be employed
555 Likewise, all memory allocations should be checked with
628 graphics packages. Instead, it is intended to be easy to use
645 This viewer may be passed to any of the `XXXView()` routines.
662 `PETSC_VIEWER_DRAW_SELF`, may be used at any time. Their initial use
663 will cause the appropriate window to be created.
665 Implementations using OpenGL, TikZ, and other formats may be selected
668 be convenient; see the `PetscDrawSetFromOptions()` man page.
674 and other windows. Alternatively, a shared colormap can be used via the
698 By default, graphics will be drawn in the entire window. To restrict the
706 drawing should be done, must satisfy
717 and 255) of the line. A list of predefined colors may be found in
745 Text can be drawn with commands
774 The argument `ncurves` indicates how many curves are to be drawn.
775 Points can be added to each of the curves with the command
782 for each curve. Several points for each curve may be added with
794 A line graph that is no longer needed can be destroyed with the command
830 will prevent any windows from being opened or any drawing actions to be
868 Many PETSc developers use Emacs, which can be used as a "simple" text editor or a comprehensive dev…
876 …e compilation commands in a file named `compile_commands.json`, which will be automatically picked…
878 It can also be used with any other editor that supports clangd, including VS Code and Vim.
886 Regardless of whether you use lsp-mode, it can be useful to use [GNU Global](https://www.gnu.org/so…
888 Tags for PETSc can be generated by running `make allgtags` from `$PETSC_DIR`, or one can generate t…
923 string in any of the PETSc files can be found with the command `M-x tags-search`.
935 This section lists helpful Vim commands for PETSc. Ones that configure Vim can be placed
936 in a `.vimrc` file in the top of the PETSc directory and will be loaded automatically.
939 a colon (such as `:help`) can be assigned to short sequences in "normal mode," which
947 The `tags` feature can be used to search PETSc files quickly and efficiently.
949 exists. If this file is not present, it should be generated by running `make
970 rather than its definition, which can be useful for refactoring. The command
1006 Autocompletion of long function names can be helpful when working with PETSc.
1012 available from external plugins that can be added to Vim, such as [SuperTab](https://github.com/erv…
1014 Along the same lines, plugins can be added that fill in the boilerplate
1024 `bear -- make -B` should be used as well to generate the file
1066 then build the project in Eclipse. The source code will be parsed by
1069 If you launch Eclipse from the Dock on Mac OS X, `.bashrc` will not be
1070 loaded (a known OS X behavior, for security reasons). This will be a
1073 executable can be found at
1106 index for PETSc that can be used with their own code, without compiling
1114 $\rightarrow$ Rebuild”. The index should now be built.
1127 license and may be obtained, either as part of the Qt SDK or as
1161 # NOTE: petsc.pc must be in the pkgconfig path. You might need to adjust PKG_CONFIG_PATH
1174 # Add all files that must be compiled
1179 # OTHER_FILES are ignored during compilation but will be shown in file panel in Qt Creator
1191 files and those related to PETSc (which may be found via
1196 - `CONFIG`: Configuration options to be used by `qmake`. Here, the
1200 here `petsc.pc`) to be passed to `pkgconfig`. Note that for this
1201 functionality to work, `petsc.pc` must be in path which might
1206 - `QMAKE_LINK`: Defines the proper linker to be used. Relevant if
1210 - `SOURCES`: Source files to be compiled.
1216 More options can be included in a `.pro` file; see