| /petsc/src/sys/error/ |
| H A D | adebug.c | 219 char program[PETSC_MAX_PATH_LEN], display[256], hostname[64]; in PetscAttachDebugger() local 232 if (PetscUnlikely(PetscGetProgramName(program, sizeof(program)))) { in PetscAttachDebugger() 236 if (PetscUnlikely(!program[0])) { in PetscAttachDebugger() 284 args[1] = program; in PetscAttachDebugger() 298 args[3] = program; in PetscAttachDebugger() 311 args[3] = program; in PetscAttachDebugger() 347 PetscCall(PetscGetFullPath(program, fullprogram, sizeof(fullprogram))); in PetscAttachDebugger() 377 args[j++] = program; in PetscAttachDebugger() 386 args[j++] = program; in PetscAttachDebugger() 400 args[j++] = program; in PetscAttachDebugger() [all …]
|
| /petsc/src/sys/dll/ |
| H A D | dl.c | 319 char program[PETSC_MAX_PATH_LEN], found[8 * PETSC_MAX_PATH_LEN]; in PetscDLLibraryAppend() local 331 PetscCall(PetscStrncpy(program, path, sizeof(program))); in PetscDLLibraryAppend() 332 PetscCall(PetscStrlen(program, &len)); in PetscDLLibraryAppend() 333 if (program[len - 1] == '/') { in PetscDLLibraryAppend() 334 PetscCall(PetscStrlcat(program, "*.", sizeof(program))); in PetscDLLibraryAppend() 336 PetscCall(PetscStrlcat(program, "/*.", sizeof(program))); in PetscDLLibraryAppend() 338 PetscCall(PetscStrlcat(program, PETSC_SLSUFFIX, sizeof(program))); in PetscDLLibraryAppend() 340 PetscCall(PetscLs(comm, program, found, 8 * PETSC_MAX_PATH_LEN, &dir)); in PetscDLLibraryAppend() 402 char program[PETSC_MAX_PATH_LEN], found[8 * PETSC_MAX_PATH_LEN]; in PetscDLLibraryPrepend() local 414 PetscCall(PetscStrncpy(program, path, sizeof(program))); in PetscDLLibraryPrepend() [all …]
|
| /petsc/share/petsc/matlab/ |
| H A D | launch.m | 1 function result = launch(program,np,opt) 3 % launch(program,np) 4 % Starts up PETSc program 10 % in a separate terminal starting the PETSc program manually, for example petscmpiexec -n 1 ./ex1 -… 25 %command = ['petscmpiexec -np ' int2str(np) ' ' program opt ' &']; 26 command = [ program opt ' &'];
|
| H A D | PetscBinaryRead.m | 23 % 'indices','int64' indicates the PETSc program was built with --with-64-bit-indices 25 % 'precision','float32' indicates the PETSc program was built with --with-precision=single
|
| /petsc/src/sys/fileio/ |
| H A D | mpiuopen.c | 156 PetscErrorCode PetscPOpen(MPI_Comm comm, const char machine[], const char program[], const char mod… in PetscPOpen() argument 180 PetscCall(PetscStrlen(program, &len)); in PetscPOpen() 182 if (program[i] == '\"') command[cnt++] = '\\'; in PetscPOpen() 183 command[cnt++] = program[i]; in PetscPOpen() 189 PetscCall(PetscStrncpy(command, program, sizeof(command))); in PetscPOpen()
|
| H A D | ftest.c | 243 char *f, program[PETSC_MAX_PATH_LEN]; in PetscLs() local 247 PetscCall(PetscStrncpy(program, "ls ", sizeof(program))); in PetscLs() 248 PetscCall(PetscStrlcat(program, dirname, sizeof(program))); in PetscLs() 250 PetscCall(PetscPOpen(comm, NULL, program, "r", &fp)); in PetscLs()
|
| /petsc/src/snes/tests/output/ |
| H A D | ex18f90_1.out | 1 Start of Fortran2003 test program 11 End of Fortran2003 test program
|
| /petsc/src/sys/tests/output/ |
| H A D | ex30_8.out | 1 # This program was run with logging synchronization. #
|
| /petsc/doc/manual/ |
| H A D | matlab.md | 10 a running PETSc program to a MATLAB process where you may 14 not interactively, but from a script or the PETSc program (this uses 31 This causes the PETSc program to print the vectors and matrices every 91 as the PETSc program) and then sends matrices or vectors via 99 start the MATLAB program manually or use the PETSc command 102 start your PETSc program from MATLAB via `launch()`.
|
| H A D | profiling.md | 25 program’s conclusion. These statistics are comprehensive and concise 32 program’s performance. See {any}`sec_PetscInfo` 35 `-info`, is useful to see where a program is hanging without 47 output or an ASCII file at the conclusion of a program. See `PetscLogView()` for all the possible 139 output generated by the `-log_view` option. The program that generated 143 and then solves the resulting linear system; the program then repeats 431 global flop counter for the entire program. 439 within a program. One can independently monitor several "stages" of code 456 stages within an program. 477 `-log_view` for a program that employs several profiling stages. In [all …]
|
| H A D | getting_started.md | 89 **Note to Python Programmers**: To program with PETSc in Python, you need to enable Python bindings 125 others, the following command initiates a program that uses eight 141 running any PETSc program with the option `-help`. 143 - `-log_view` - summarize the program’s performance (see {any}`ch_profiling`) 158 - `-info` - print a great deal of information about what the program 179 character string that will be printed if the program is run with the 209 need not program much message passing directly with MPI, but they must 215 program and calls `MPI_Finalize()` if `PetscInitialize()` began 239 ! within the main program 282 Each PETSc program must specify an include file corresponding to the [all …]
|
| H A D | performance.md | 531 is to run a program with the option `-info`. The symbolic 571 conclusion of a program. If all memory has been freed no message 575 call `PetscMallocDump()` elsewhere in a program. 577 is `-malloc_view`, which reports memory usage in all routines at the conclusion of the program. 582 these routines elsewhere in a program. 587 for the total memory used by the program. Note that 590 program). 592 not just the memory used by `PetscMalloc()`, at the conclusion of the program. 688 program, one should always leave at least a ten percent margin 695 same physical processor nodes on which a program is being profiled, [all …]
|
| H A D | other.md | 25 given program, simply specify the option `-help` at 33 that can be explicitly called from within a program to set compile-time 177 Any subroutine in a PETSc program can add entries to the database with 359 The measurements of load balancing can also be done within the program 420 the program within the debugger. Rerunning the program through the 475 All PETSc calls can be traced (useful for determining where a program is 510 when the program is started up. This feature is useful for debugging without needing to start up a … 528 can be used within a program. A `flag` of `PETSC_FP_TRAP_ON` indicates that 610 The program 672 external program’s mangling of the colormap. Unfortunately, this may [all …]
|
| /petsc/src/binding/petsc4py/docs/source/ |
| H A D | install.rst | 9 You can use :program:`pip` to install :mod:`petsc4py` and its dependencies:: 28 your build host, then before invoking :program:`pip`, set the
|
| H A D | petsc_options.rst | 10 In order to use command-line options in a petsc4py program, it is important to initialize the modul…
|
| /petsc/doc/miscellaneous/ |
| H A D | saws.md | 4 allow a client program to read (and change when desired) variables in
|
| H A D | funding.md | 26 - The DOE/FE ACTI program, late 1990's
|
| /petsc/src/ts/tutorials/ |
| H A D | extchem.example.1 | 6 # them in this directory (otherwise the program will automatically obtain them for you).
|
| H A D | h2_10sp.inp | 5 # them in this directory (otherwise the program will automatically obtain them for you).
|
| /petsc/lib/petsc/bin/maint/abi-compliance-checker/ |
| H A D | LICENSE | 60 any free program. We wish to make sure that a company cannot 61 effectively restrict the users of a free program by obtaining a 73 When a program is linked with a library, whether statically or using 105 users' freedom, it does ensure that the user of a program that is 107 that program using a modified version of the Library. 119 program which contains a notice placed by the copyright holder or 144 running a program using the Library is not restricted, and output from 145 such a program is covered only if its contents constitute a work based 148 and what the program that uses the Library does. 176 table of data to be supplied by an application program that uses [all …]
|
| H A D | INSTALL | 82 This command will install the abi-compliance-checker program into the
|
| /petsc/doc/faq/ |
| H A D | index.md | 86 Check `man taskset` for details. Make sure to set affinity for **your** program, 87 **not** for the `mpiexec` program. 181 human-readable format. This is why your program cannot, for example, look directly 183 - Polymorphism makes changing program behavior as easy as possible, and further 184 abstracts the *intent* of your program from what is *written* in code. You call 197 ### How come when I run the same program on the same number of processes I get a "different" answer? 550 The above is compiled and linked as if it was a console program. The linker will search 581 program. 759 matrix in parallel in your "real" PETSc program with `MatLoad()`. 1149 and forth between an interactive MATLAB session and a running PETSc program. See [all …]
|
| /petsc/doc/tutorials/ |
| H A D | handson.md | 146 - <a href="PETSC_DOC_OUT_ROOT_PLACEHOLDER/src/snes/tutorials/ex19.c.html#line94">main program sourc… 297 - <a href="PETSC_DOC_OUT_ROOT_PLACEHOLDER/src/ts/tutorials/ex11.c.html#line1403">main program sourc…
|
| /petsc/doc/changes/ |
| H A D | 38.md | 192 help string and then exits the program 211 Correspondingly SERERRA() and CHKERRA() should be used in 'program
|
| H A D | 2016.md | 109 useful to see where a program is hanging without running in the
|