| /petsc/src/ksp/ksp/tutorials/output/ |
| H A D | ex70_1.out | 13 .... project 23 .... project 33 .... project 43 .... project 53 .... project 63 .... project 73 .... project 83 .... project 93 .... project 103 .... project
|
| H A D | ex70_1_matis.out | 13 .... project 23 .... project 33 .... project 43 .... project 53 .... project 63 .... project 73 .... project 83 .... project 93 .... project 103 .... project
|
| H A D | ex70_fetidp_saddlepoint.out | 14 .... project 26 .... project 38 .... project 50 .... project
|
| H A D | ex70_fetidp_saddlepoint_lumped.out | 14 .... project 26 .... project 38 .... project 50 .... project
|
| H A D | ex70_fetidp_lumped.out | 14 .... project 26 .... project 38 .... project 50 .... project
|
| H A D | ex70_fetidp.out | 14 .... project 26 .... project 38 .... project 50 .... project
|
| /petsc/src/binding/petsc4py/docs/ |
| H A D | index.rst | 36 + Previous source releases: https://pypi.org/project/petsc4py/ 41 If PETSc for Python been significant to a project that leads to an 43 project. 64 This project was partially supported by the
|
| /petsc/share/petsc/ |
| H A D | CMakeLists.txt | 18 # Dummy project to determine compiler names and version 19 project(detect_compilers LANGUAGES) 40 project(ex1)
|
| /petsc/ |
| H A D | CONTRIBUTING | 19 By making a contribution to this project, I certify that: 37 (d) I understand and agree that this project and the contribution 41 this project or the open-source license(s) involved.
|
| /petsc/src/binding/petsc4py/docs/source/ |
| H A D | citing.rst | 4 If PETSc for Python has been significant to a project that leads to an 6 project.
|
| /petsc/src/binding/petsc4py/conf/ |
| H A D | epydoc.cfg | 76 # The documented project's name. 79 # The documented project's URL. 86 # HTML code for the project link in the navigation bar. If left 87 # unspecified, the project link will be generated based on the 88 # project's name and URL.
|
| /petsc/src/dm/impls/plex/tutorials/ |
| H A D | ex8.c | 35 PetscBool view_coord = PETSC_FALSE, tensor = PETSC_TRUE, project = PETSC_FALSE; in main() local 41 …-project_coordinates", "Call DMSetCoordinateDisc() explicitly", "ex8.c", project, &project, NULL)); in main() 49 if (project) { in main()
|
| /petsc/src/binding/petsc4py/ |
| H A D | DESCRIPTION.rst | 27 If PETSc for Python been significant to a project that leads to an 29 project.
|
| /petsc/systems/Apple/OSX/examples/PETSc cocoa example/PETSc cocoa example/ |
| H A D | PETSc cocoa example-Prefix.pch | 2 …eader for all source files of the 'PETSc cocoa example' target in the 'PETSc cocoa example' project
|
| /petsc/systems/Apple/iOS/examples/Basic/ |
| H A D | examples_Prefix.pch | 2 // Prefix header for all source files of the 'iphone' target in the 'iphone' project
|
| /petsc/systems/Apple/iOS/examples/testopengl/ |
| H A D | examples_Prefix.pch | 2 // Prefix header for all source files of the 'iphone' target in the 'iphone' project
|
| /petsc/doc/manualpages/MANSECHeaders/ |
| H A D | DMSwarm | 3 …le data, movement, and interface with meshes. It also can conservatively project fields between th…
|
| /petsc/config/BuildSystem/ |
| H A D | pythonpath.py | 4 import project
|
| /petsc/lib/petsc/bin/maint/petsclinter/ |
| H A D | pyproject.toml | 1 [project]
|
| /petsc/src/sys/perfstubs/ |
| H A D | timer_f.h | 10 ! line or in a config.h file, however your project does it
|
| /petsc/doc/install/ |
| H A D | license.md | 48 > By making a contribution to this project, I certify that: 63 > 4. I understand and agree that this project and the contribution 67 > this project or the open source license(s) involved.
|
| H A D | windows.md | 175 We cannot provide Microsoft Visual Studio project files for users as they are specific to 178 different for each build of PETSc. So if you need a project file for use with PETSc - 181 1. Create an empty project file with one of the examples, say 192 are also present in the project file in the correct notation.
|
| /petsc/doc/manual/ |
| H A D | other.md | 877 You can use the same procedure when building examples or your own project. 1044 install the EGit plugin. When importing the project, select the 1045 wizard “Import as general project”. 1046 2. Right-click on the project (or the “File” menu on top) and select 1049 project type as “Shared Library”. 1050 3. Right-click on the C project and open the “Properties” panel. Under 1066 then build the project in Eclipse. The source code will be parsed by 1082 1. Right-click on your C project and select “Properties 1107 PETSc source into their project. 1109 1. In the user project source directory, create a symlink to the PETSc [all …]
|
| /petsc/doc/developers/contributing/ |
| H A D | submittingmr.md | 6 Alternatively, use [GitLab's web interface](https://docs.gitlab.com/ee/user/project/merge_requests/… 10 …include a [closing pattern](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#de… 70 …ful feature is the ["insert suggestion"](https://docs.gitlab.com/ee/user/project/merge_requests/re…
|
| /petsc/doc/developers/ |
| H A D | buildsystem.md | 78 requires `libstdc++`, but they are working with a C project, no 176 self.framework.header = self.arch.arch+'/include/'+self.project+'conf.h' 177 self.framework.makeMacroHeader = self.arch.arch+'/conf/'+self.project+'variables' 178 self.framework.makeRuleHeader = self.arch.arch+'/conf/'+self.project+'rules' 197 self.project = self.Project.lower() 247 The `projectdir` and `arch` modules define the project root
|