| /petsc/doc/changes/ |
| H A D | 34.md | 19 - `PetscFList` and `PetscOList` have been changed to 28 etc., have been simplified to drop the string function name 34 `--with-c++-support` have been removed. A PETSc library built 81 -vec_view_binary, -vec_view_draw, -vec_view_lg have been replace 102 could have length zero on some processors because it could lead to 114 -mat_view_draw, -mat_view_contour have been replace by a more 120 - `MatGetArray()/MatRestoreArray()` have been remove d. Use 124 - MatGetRowIJ() and MatGetColumnIJ() have been made const-correct; 125 the index arrays have always been read-only. 127 They should never have been accessed after restoring. [all …]
|
| H A D | 35.md | 8 read in binary files that have all 128 bits stored in the file, to 33 `PetscMalloc7()`, `PetscNew()`, and `PetscNewLog()` have 36 and `PetscCalloc1()` through `PetscCalloc7()` have been added 86 setting the fields split. In all cases, the index sets should have 156 enumeration values have also been renamed. 185 `--download-cholmod` to download UMFPACK and CHOLMOD have been
|
| /petsc/doc/miscellaneous/ |
| H A D | codemanagement.md | 4 efficiency when developing PETSc application codes. We have learned to 5 use these techniques ourselves, and they have improved our efficiency 32 - `emacs` and `vim` have a feature to allow the user to compile 33 using make and have the editor automatically jump to the line of 74 names you don't have to remember what they represent since it is 82 - Realize that you **will** have to debug your code. **No one** writes 88 developing codes who have to wait 15 minutes after starting a run to 91 - Develop your code on the simplest machine to which you have access. 92 We have accounts on a variety of large parallel machines, but we
|
| /petsc/ |
| H A D | CONTRIBUTING | 22 have the right to submit it under the open-source license 27 license and I have the right under that license to submit that 34 person who certified (a), (b) or (c) and I have not modified
|
| /petsc/src/binding/petsc4py/ |
| H A D | DESCRIPTION.rst | 9 If you have a working MPI implementation and the ``mpicc`` compiler 15 Ensure you have NumPy installed::
|
| /petsc/src/ksp/ksp/tutorials/output/ |
| H A D | ex73_basic_neumann.out | 3 [size 4] DMCreateMatrix_ShellDA: operator does not have nullspace - attaching 6 [size 4] DMCreateMatrix_ShellDA: operator does not have nullspace - attaching 11 [size 1] DMCreateMatrix_ShellDA: operator does not have nullspace - attaching
|
| /petsc/src/sys/yaml/ |
| H A D | README.md | 11 * The emitter API and other output-related parts have been removed, 13 * `yaml_get_version()` and `yaml_get_version_string()` have been
|
| /petsc/lib/petsc/conf/ |
| H A D | test | 3 # Empty file for backward compatibility. The rules in this file have been moved to rules
|
| /petsc/doc/developers/contributing/ |
| H A D | index.md | 45 - If you have write access to the PETSc [GitLab repository](https://gitlab.com/petsc/petsc), use `g… 46 (or use a clone you already have). 52 - If you already have a clone on your machine of the PETSc repository you would like to reuse
|
| H A D | submittingmr.md | 11 …such as `Closes #123` in the MR’s description to automatically have the issue closed when the MR i… 35 …search=workflow%3A%3A) that indicate the state of the MR. Every MR should have exactly one of thes… 48 …king on the branch. Other developers not involved in the branch generally have no reason to look a… 89 …pipeline passes, new commits have been {any}`properly rearranged <sec_clean_commit_history>` if ne…
|
| H A D | developingmr.md | 32 The `main` branch contains everything in the release branch as well as new features that have passe… 92 …If any interfaces have changed, the commit should fix occurrences in PETSc itself and the message … 94 …We have defined several standard commit message tags you should use; this makes it easy to search … 156 It is better to clean up your commits regularly than to wait until you have a large number of them. 158 For example, if you have made three commits and the most recent two are fixes for the first, you co…
|
| H A D | pipelines.md | 51 A failure in running the job's tests will have `FAILED` and a list of the failed tests 69 After you have fixed a problem that appeared in a particular (set of) job(s) you may want to test y… 123 new changes to the branch you have pushed since that pipeline was started - it retries the
|
| /petsc/doc/manual/ |
| H A D | dmcommonality.md | 5 We have introduced a variety of seemingly very different `DM`. Here, we will try to explore the com… 37 …rid cells (also called elements). As with `DMDA` each type of entity must have the same number of … 40 …us which entity on the cell is being accessed. Since a staggered grid can have any problem-depende… 57 for an entity on the grid from its `point` value, since each `point` can have any number of values … 65 vectors or arrays for said points. If needed one can then have an inner iteration over the fields a… 73 …he entities are nodes and edges that connect two nodes, each of which can have any number of submo…
|
| H A D | dmbase.md | 5 The previous chapters have focused on the core numerical solvers in PETSc. However, numerical solve… 10 `DM` is an orphan initialism or orphan acronym, the letters have no meaning and never did. 20 In previous chapters, we have demonstrated some simple usage of `DM` to provide the input for the s…
|
| H A D | dt.md | 11 …an event at location in $[x, x+dx]$ is $P(x) dx$. This means that we must have the normalization c… 17 where :math:Omega is the domain for $x$. This requires that the PDF must have units which are the i…
|
| /petsc/doc/tutorials/meshing/ |
| H A D | guide_to_subsurface.md | 18 …-dimensional cells, and from the `celltype` label we see that those cells have celltype 9, meaning… 64 … conforming, as we do in this case. We would like different grid cells to have different levels of… 74 … a volume constraint, namely that cells with a certain label value should have a certain volume. Y… 82 Test 3 from `ex10` constrains the headwater cells (with marker 1) to have volume less than 0.01, an…
|
| /petsc/src/tao/leastsquares/tutorials/matlab/ |
| H A D | README | 2 Here is the list of problems where we have issues:
|
| /petsc/doc/faq/ |
| H A D | index.md | 35 have its **own** memory bandwidth of at least 2 or more gigabytes/second. Most modern 45 If you do not know this and can run MPI programs with mpiexec (that is, you don't have 55 If you have a batch system: 66 Even if you have enough memory bandwidth if the OS switches processes between cores 123 C++ without using such a large and more complicated language. It would have been natural and 124 reasonable to have coded PETSc in C++; we opted to use C instead. 170 7. **We have a rich, robust, and fast bug reporting system** 301 Assuming that the PETSc libraries have been successfully built for a particular 316 installing PETSc, in case you have missed a step. 327 `$PETSC_DIR/src/*/tests/output`. Once you have run the test examples, you may remove [all …]
|
| /petsc/doc/install/ |
| H A D | install_tutorial.md | 15 Or to specify compilers and have PETSc download and install [MPICH](https://www.mpich.org/) and [BL… 55 terminal". Being a programmable solver suite, PETSc does not have a 65 Before beginning, make sure you have the following pre-requisites installed and up to 82 While it is recommended that you have functional C++ and Fortran compilers installed, 171 additional options or packages in the future, you will have to reconfigure your PETSc 194 have the following general structure as its output: 313 You now have a working PETSc installation and are ready to start using the library!
|
| H A D | download.md | 21 any questions they may have directly to the development team, to be notified of new 51 applications that have not been updated to the latest release. We urge you, whenever 63 or if you already have a local clone of PETSc Git repository
|
| H A D | install.md | 28 If there is a system for which we do not yet have such a `configure` script and/or 34 - If you do not have a Fortran compiler or [MPICH](https://www.mpich.org/) installed 185 recommend you have PETSc download and install the packages, rather than you installing 193 - Some packages have bug fixes, portability patches, and upgrades for dependent 194 packages that have not yet been included in an upstream release, and hence may not 206 If you are behind a firewall and cannot use a proxy for the downloads or have a very slow 272 `--with-PACKAGENAME-dir`. Architectures like Microsoft Windows might have issues 325 Sadly, IBM's [ESSL] does not have all the routines of [BLAS/LAPACK] that some 617 - You must first ensure you have loaded appropriate modules for the compilers etc that you 655 Use `--with-openmp-kernels` to have some PETSc numerical routines use OpenMP to speed up their comp… [all …]
|
| /petsc/doc/developers/ |
| H A D | articles.md | 3 Many articles have been written about the design of PETSc. We mention
|
| H A D | style.md | 27 - have an appended `_Private` (for example, `StashValues_Private`) 29 - have an appended `_Subtype` (for example, `MatMultSeq_AIJ`). 52 08. Options database keys are lower case, have an underscore between 56 09. Specific `XXXType` values (for example, `MATSEQAIJ`) do not have 85 Though `size_t` is unsigned and hence can have values larger than those that can be stored 103 …names end in `_c`. Since not all installed MPI implementations have such support, use `MPIU_XXX()`… 183 05. Functions in PETSc examples, including `main()` should have `PetscFunctionBeginUser` as the fir… 189 08. All PETSc function calls must have their return value checked for errors using the 317 04. Subroutines that would normally have a `void **` argument to return 336 It's OK to have [all …]
|
| /petsc/src/snes/tutorials/output/ |
| H A D | ex19_failure_size.out | 3 [0]PETSC ERROR: Product of two integers 2 1610612736 overflow, either you have an invalidly large i…
|
| /petsc/src/ksp/pc/impls/gamg/ |
| H A D | geo.c | 322 PetscBool have = PETSC_TRUE; in triangulateAndFormProl() local 325 … if (PetscRealPart(alpha[tt]) > (1.0 + EPS) || PetscRealPart(alpha[tt]) < -EPS) have = PETSC_FALSE; in triangulateAndFormProl() 331 haveit = have; in triangulateAndFormProl() 351 PetscBool have = PETSC_TRUE; in triangulateAndFormProl() local 353 for (tt = 0; tt < 3 && have; tt++) { in triangulateAndFormProl() 354 … if (PetscRealPart(alpha[tt]) > 1.0 + EPS || PetscRealPart(alpha[tt]) < -EPS) have = PETSC_FALSE; in triangulateAndFormProl() 361 haveit = have; in triangulateAndFormProl()
|