| /petsc/doc/developers/ |
| H A D | communication.md | 17 Comments and questions regarding PETSc design and development should go to <mailto:petsc-dev@mcs.an…
25 General questions regarding the use of PETSc can, as usual, go to <mailto:petsc-users@mcs.anl.gov> …
|
| H A D | meetings-developers.md | 8 …- In 2023 we used EventBright, Barry set it up and had the money go straight to his bank account. …
|
| H A D | style.md | 593 The Fortran interface files supplied manually by the developer go into the
595 go into directories in the \$PETSC_ARCH/ftn\`\` directory tree.
|
| H A D | documentation.md | 210 - Decide where in `doc/images` a new image should go. Use the structure of the `doc/` tree as a gui…
|
| /petsc/src/tao/unconstrained/tutorials/ |
| H A D | adjointreads.m | 37 % plot(xg,Grad,'go-','Markersize',10); drawnow
71 % plot(xg,Init_ts,'go-','Markersize',10); drawnow;
|
| /petsc/share/petsc/saws/ |
| H A D | readme | 7 Example usage: after starting each example below go to localhost:8080 in browser
|
| /petsc/doc/changes/ |
| H A D | 232.md | 43 -ksp_default_converged_initial_residual_norm to go back to the pre
|
| H A D | 231.md | 108 interface now go into the same library]
|
| H A D | 312.md | 97 communication code. One can use -vecscatter_type mpi1 to go back
|
| /petsc/src/dm/impls/swarm/tests/ |
| H A D | ex7.c | 216 PetscErrorCode go() in go() function
342 PetscCall(go()); in main()
|
| /petsc/doc/install/ |
| H A D | download.md | 104 will go to 3.22.x - and petsc-3.21, petsc-3.20, etc., will not get any additional patch updates.
|
| /petsc/config/BuildSystem/ |
| H A D | RDict.py | 402 are running. For more information about rebase, go to http://www.cygwin.com')
409 are running. For more information about rebase, go to http://www.cygwin.com\n')
|
| /petsc/lib/petsc/bin/maint/petsclinter/petsclinter/ |
| H A D | README.rst | 52 fairly vital that imports **do not** go backwards, otherwise you will introduce a bunch of
|
| /petsc/ |
| H A D | .mailmap | 55 Marius Buerkle <marius.buerkle@aist.go.jp>
|
| H A D | gmakefile.test | 198 # Test modules go in the same directory as the target *.o
405 else # No filter - run them all, but delete the executables as we go
|
| /petsc/src/ts/tests/ |
| H A D | ex30.c | 459 PetscErrorCode go(TS ts, Vec X, const PetscInt num_vertices, const PetscInt a_Np, const PetscInt di… in go() function
1079 PetscCall(go(ts, X, num_vertices, Np, dim, v_target, g_target, shift, use_uniform_particle_grid)); in main()
|
| /petsc/config/BuildSystem/config/packages/ |
| H A D | MPI.py | 178 compiles go through - but one might get run-time errors. Either\n\
|
| /petsc/doc/manual/ |
| H A D | performance.md | 112 requests for memory attached to a different CPU socket need to go
|
| H A D | other.md | 504 Once the first PETSc signal handler has been pushed it is impossible to go back to
|
| H A D | ksp.md | 1334 reported). The number of non-zeros can go up very high, say about 300
|
| H A D | tao.md | 1942 checking if a function is locally quadratic; if so, go do a gradient
|
| /petsc/doc/tutorials/physics/ |
| H A D | guide_to_stokes.md | 350 At this point, we could just go back and check the code. However, PETSc will also print out the dif…
|
| /petsc/doc/faq/ |
| H A D | index.md | 558 To change where all PETSc `stdout` and `stderr` go, (you can also reassign
|
| /petsc/doc/ |
| H A D | petsc.bib | 1241 url = {http://www.jstage.jst.go.jp/article/msjmag/32/2_1/32_50/_article},
|