| /petsc/systems/Apple/iOS/examples/SwiftExample/SwiftExample/ |
| H A D | AppDelegate.swift | 33 …func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObjec… in application() function 40 func applicationWillResignActive(application: UIApplication) { in applicationWillResignActive() 45 func applicationDidEnterBackground(application: UIApplication) { in applicationDidEnterBackground() 50 func applicationWillEnterForeground(application: UIApplication) { in applicationWillEnterForeground() 54 func applicationDidBecomeActive(application: UIApplication) { in applicationDidBecomeActive() 58 func applicationWillTerminate(application: UIApplication) { in applicationWillTerminate()
|
| /petsc/src/binding/petsc4py/src/petsc4py/PETSc/ |
| H A D | AO.pyx | 4 """The application ordering types.""" 22 """Display the application ordering. 41 """Destroy the application ordering. 58 """Return a basic application ordering using two orderings. 70 The application ordering. 107 """Return a memory scalable application ordering using two orderings. 122 The application ordering. 159 """Return an application mapping using two orderings. 170 The application ordering. 201 """Return the application ordering type. [all …]
|
| /petsc/share/petsc/ |
| H A D | CMakeLists.txt | 2 # This is a SAMPLE CMakeLists.txt suitable for direct use with a new PETSc application or 3 # you can add fragments of the material below to an existing application's CMakeLists.txt 38 # tells CMake to build the application ex1 from the source file ex1.c
|
| /petsc/systems/Apple/iOS/examples/testopengl/Classes/ |
| H A D | iphoneAppDelegate.m | 21 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)laun…
|
| /petsc/systems/Apple/iOS/examples/Basic/Classes/ |
| H A D | iphoneAppDelegate.m | 21 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)laun…
|
| /petsc/doc/manual/ |
| H A D | about_this_manual.md | 7 building blocks for implementing large-scale application codes 12 solvers**, **time integrators**, and **optimizers** that may be used in application codes 25 of many application codes simpler than “rolling them” yourself. 36 This approach can provide modest improvements in the application time
|
| H A D | versionchecking.md | 31 provide tools to help manage one's application to be robust to such changes. 42 way for `lt`, `le`, `gt`, and `ge`. This allows your application configure script, or `makefile` or… 43 to check if the PETSc version is compatible with application even before beginning to compile your …
|
| H A D | tao.md | 131 can be used to set the algorithm TAO uses to solve the application. The 145 requires quotation marks in an application program, but quotation marks 176 In all the optimization solvers, the application must provide a `Vec` 182 the application object by using the 188 routine. When using this routine, the application should initialize the 191 store the solution. Elsewhere in the application, this solution vector 192 can be retrieved from the application object by using the 199 argument and sets it to the solution vector used in the application. 209 Writing a TAO application may require use of an *application context*. 210 An application context is a structure or object defined by an [all …]
|
| H A D | getting_started.md | 63 enables the application programmer to begin using the software 532 employ MPI routines as needed throughout an application code. However, 607 For application codes that use certain external packages, including BLAS/LAPACK, SuperLU_DIST, MUMP… 608 …igure option `--with-openmp`. The number of OpenMP threads used in the application can be controll… 768 To develop an application program that uses PETSc, we suggest the following: 774 > 1. Make a directory for your source code: for example, `mkdir $HOME/application` 777 > example, `cd $HOME/application` 783 …> 4. Select an application build process. The `PETSC_DIR` (and `PETSC_ARCH` if the `--prefix=direc… 799 … read the comments on usage, and change the name of the application from ex1 to your application e… 804 > 6. Start to modify the program to develop your application. [all …]
|
| H A D | dmnetwork.md | 12 The general flow of an application code using `DMNETWORK` is as 22 is specific application data at a vertex/edge of the network required 115 application.
|
| H A D | dmcommonality.md | 45 …es desired for the application. For example, for a discretization with cell-centered pressures and… 63 a particular entity. For example, when using the finite element method, the application iterates al…
|
| H A D | profiling.md | 6 application programs. The PETSc routines automatically log 8 can also log information about application codes for a complete picture 16 such as monitoring application codes and tips for accurate profiling. 332 application as any MPI application, and follow the MPI implementation’s 371 information by profiling their application codes as well. The basic 589 PETSc application programmers can access the wall clock time directly 714 mpiexec -n 1 rocprofv3 --marker-trace -o file_name -- ./path/to/application -log_roctx 750 100.0 26 1,838 1 41322 1838424 .TAU application
|
| H A D | other.md | 541 by the application programmer as well. When an error is first detected, 567 macro in their application codes; however, users can take advantage of 586 PETSc supports the use of complex numbers in application programs 691 of the window. The application program can change the window coordinates 741 `-draw_pause` `n`, which causes the PETSc application to pause `n` 743 the application should pause until receiving mouse input from the user. 765 usually not used directly by the application programmer. Instead, the 1119 For further examples of using Eclipse with a PETSc-based application, 1149 # The name of the application executable 1187 - `TARGET`: The name of the application executable. [all …]
|
| /petsc/doc/miscellaneous/ |
| H A D | saws.md | 5 the server (PETSc) application). 18 `http://localhost:8080` or, if you are running your application on a
|
| H A D | codemanagement.md | 4 efficiency when developing PETSc application codes. We have learned to 79 written for an application will be visited **over and over** again,
|
| /petsc/src/binding/petsc4py/docs/source/ |
| H A D | overview.rst | 9 PETSc is intended for use in large-scale application projects 13 independently developed application modules, which often most 19 and nonlinear equation solvers that are easily used in application 21 mechanisms needed within parallel application codes, such as simple
|
| /petsc/doc/overview/ |
| H A D | index.md | 5 equation solvers, ODE integrators, and optimization algorithms** for application codes written in
|
| /petsc/doc/manualpages/MANSECHeaders/ |
| H A D | SNES | 7 …the solution of its linear systems. `SNES` users can also set `KSP` options directly in application
|
| /petsc/systems/Apple/OSX/examples/PETSc cocoa example/PETSc cocoa example/ |
| H A D | AppDelegate.m | 44 // Insert code here to initialize your application
|
| /petsc/doc/developers/ |
| H A D | objects.md | 5 that is completely private from the application code. The application 44 Its own, application-public, include file `include/petsc<class>.h`. 54 An abstract interface that defines the application-callable functions 78 from the application code. This capability is extremely important 80 or recompiling the application code.
|
| /petsc/doc/changes/ |
| H A D | 2017.md | 86 routines linked into an application code. This can decrease the 136 problems for large-scale application codes, we've added several 161 application codes, but can take advantage of this feature if
|
| H A D | 216.md | 105 - ADIC: ad_GRAD_MAX is now set in the application and compiled into
|
| H A D | index.md | 13 application codes from a particular version to the most recent
|
| /petsc/lib/petsc/bin/maint/abi-compliance-checker/ |
| H A D | LICENSE | 125 prepared so as to be conveniently linked with application programs 176 table of data to be supplied by an application program that uses 179 in the event an application does not supply such function or 185 application. Therefore, Subsection 2d requires that any 186 application-supplied function or table used by this function must 187 be optional: if the application does not supply it, the square 295 Library will not necessarily be able to recompile the application 397 through that system in reliance on consistent application of that
|
| /petsc/systems/Apple/OSX/examples/PETSc cocoa example/PETSc cocoa example.xcodeproj/ |
| H A D | project.pbxproj | 22 …a example.app */ = {isa = PBXFileReference; explicitFileType = wrapper.application; includeInIndex… 131 productType = "com.apple.product-type.application";
|