| /petsc/share/petsc/datafiles/meshes/ |
| H A D | gmsh-3d-ascii.msh2 | 5 test: comment line 1 9 test: comment line 1 10 test: comment line 2 21 test: comment line 1 25 test: comment line 1 26 test: comment line 2
|
| H A D | gmsh-3d-binary.msh2 | 5 test: comment line 1 9 test: comment line 1 10 test: comment line 2 22 test: comment line 1 26 test: comment line 1 27 test: comment line 2
|
| /petsc/config/ |
| H A D | petsc_harness.sh | 153 comment=$3 154 if test -n "$comment"; then 155 comment=" # ${comment}" 158 tap_message="${notornot} ok ${test_label}${comment}" 238 comment="" 241 comment="${cmd}" 243 petsc_report_tapoutput "" "$tlabel" "$comment" 247 comment="Exceeded timeout limit of $MPIEXEC_TIMEOUT s" 249 comment="Error code: ${cmd_res}" 251 petsc_report_tapoutput "not" "$tlabel" "$comment"
|
| H A D | testparse.py | 416 comment=("" if len(ln.split("#"))>0 else " ".join(ln.split("#")[1:]).strip()) 417 if comment: comments.append(comment)
|
| /petsc/lib/petsc/bin/ |
| H A D | extract.py | 21 for comment in list_of_comments: 22 if comment[0:2] == "//": 23 comment_to_write = comment[2:] 25 comment_to_write = comment[2:-2]
|
| /petsc/src/binding/petsc4py/ |
| H A D | .cython-lint.toml | 5 "E261", # at least two spaces before inline comment
|
| /petsc/doc/developers/contributing/ |
| H A D | submittingmr.md | 29 - GitLab does not allow you to set labels, so `@`-mention one of the developers in a comment so the… 68 Reviewers comment on the MR, either 70 …m/ee/user/project/merge_requests/reviews/suggestions.html) button in the comment box, to suggest a… 71 - or in the overview if it is a general comment. When introducing a new topic (thread) in reviewing… 75 thread; do not introduce a new thread or a comment.
|
| /petsc/doc/developers/ |
| H A D | style.md | 229 11. Use classic block comments (`/* There must be a space before the first word in the comment and … 232 12. Do not put a `*` at the beginning or end of each line of a multi-line comment. 331 non-comment line of the file. There must be no leading or trailing empty (non-comment) 392 directives with a comment containing (or explaining) either the boolean condition or 576 a formatted comment of a function that will be used for documentation and a Fortran interface. 578 …a formatted comment of a function that will be used only for documentation, not to generate a Fort… 580 a formatted comment of an enum used for documentation only. 583 a formatted comment for a data type such as 587 a formatted comment for a string type such as 591 a formatted comment of a CPP macro or enum value for documentation. [all …]
|
| H A D | testing.md | 80 At the end of each test file, a marked comment block is
|
| /petsc/share/petsc/ |
| H A D | Makefile.basic.user | 69 # Access compile targets here. However if you manage them yourself (rarely needed) comment out the…
|
| /petsc/src/ksp/ksp/tutorials/ |
| H A D | ex49.c | 297 static PetscErrorCode DMDAViewGnuplot2d(DM da, Vec fields, const char comment[], const char prefix[… in DMDAViewGnuplot2d() argument 316 PetscCall(PetscFPrintf(PETSC_COMM_SELF, fp, "### %s (processor %1.4d) ### \n", comment, rank)); in DMDAViewGnuplot2d() 360 static PetscErrorCode DMDAViewCoefficientsGnuplot2d(DM da, Vec fields, const char comment[], const … in DMDAViewCoefficientsGnuplot2d() argument 378 PetscCall(PetscFPrintf(PETSC_COMM_SELF, fp, "### %s (processor %1.4d) ### \n", comment, rank)); in DMDAViewCoefficientsGnuplot2d()
|
| H A D | ex43.c | 350 static PetscErrorCode DMDAViewGnuplot2d(DM da, Vec fields, const char comment[], const char prefix[… in DMDAViewGnuplot2d() argument 368 PetscCall(PetscFPrintf(PETSC_COMM_SELF, fp, "### %s (processor %1.4d) ### \n", comment, rank)); in DMDAViewGnuplot2d() 413 static PetscErrorCode DMDAViewCoefficientsGnuplot2d(DM da, Vec fields, const char comment[], const … in DMDAViewCoefficientsGnuplot2d() argument 430 PetscCall(PetscFPrintf(PETSC_COMM_SELF, fp, "### %s (processor %1.4d) ### \n", comment, rank)); in DMDAViewCoefficientsGnuplot2d()
|
| /petsc/doc/manual/ |
| H A D | tests.md | 136 Include at the bottom of the test code a formatted comment indicating what tests should be run, see
|
| /petsc/doc/community/ |
| H A D | governance.md | 38 PETSc should be on the mailing list). If no-one bothers to comment on the mailing list
|
| /petsc/doc/changes/ |
| H A D | 34.md | 17 - In PETSc options files, the comment characters `!` and `%` are
|
| /petsc/src/sys/tests/linter/output/ |
| H A D | testValidFunctionDocStrings.patch | 205 /* a random comment above a function */
|
| /petsc/doc/community/meetings/2025/ |
| H A D | index.md | 21 [comment]: # (Intro: Python, Linear/Nonlinear Solver, GPU)
|
| /petsc/doc/faq/ |
| H A D | index.md | 1159 also the next comment that shows how to create numpy arrays in the Cython and pass them
|
| /petsc/doc/ |
| H A D | petsc.bib | 11479 comment = {Preprint \# ANL/MCS-P1612-0409},
|