| /petsc/src/binding/petsc4py/docs/source/ |
| H A D | install.rst | 37 When installing from source, the petsc4py complete testsuite can be run as::
46 Specific tests can be run using the command-line option ``-k``, e.g.::
50 to run all the tests provided in :file:`tests/test_optdb.py`.
52 For other command-line options, run::
56 If not otherwise specified, all tests will be run in sequential mode.
57 To run all the tests with the same number of MPI processes, for example
58 ``4``, run::
|
| H A D | contributing.rst | 18 For Python code, run::
33 If you add a new :file:`test_xxx.py`, you can run the tests using::
45 standard <documentation_standards>`. To check for compliance, run::
|
| /petsc/src/binding/petsc4py/demo/legacy/poisson2d/ |
| H A D | makefile | 10 test: run clean
12 .PHONY:run
13 run: target
|
| /petsc/src/binding/petsc4py/demo/legacy/binary-io/ |
| H A D | makefile | 10 test: run clean
12 .PHONY:run
13 run: target
|
| /petsc/src/benchmarks/ |
| H A D | benchmarkExample.py | 98 def run(self, numProcs = 1, log = True, **opts): member in PETScExample
350 for run in sizes:
351 rsizes = np.array(sizes[run])
352 …data.extend([rsizes, errors[run], rsizes, (errors[run][0]*rsizes[0]*2)*rsizes**(meshExp[run]/-2.0)…
353 legends.extend(['Experiment '+run, r'Synthetic '+run+r' $\alpha = '+str(meshExp[run])+'$'])
367 for run in times:
368 rtimes = np.array(times[run])
369 data.extend([rtimes, errors[run], rtimes, (errors[run][0]*rtimes[0]*2)*rtimes**(timeExp[run])])
370 legends.extend(['Experiment '+run, 'Synthetic '+run+' exponent '+str(timeExp[run])])
384 for run in times:
[all …]
|
| /petsc/src/binding/petsc4py/demo/legacy/kspsolve/ |
| H A D | makefile | 10 test: run clean
12 .PHONY:run
13 run: run_1 run_2 target
|
| /petsc/src/binding/petsc4py/demo/legacy/bratu3d/ |
| H A D | makefile | 10 test: run clean
12 .PHONY:run
13 run: run_fd run_mf target
|
| /petsc/src/binding/petsc4py/demo/legacy/perftest/ |
| H A D | makefile | 10 test: run clean
12 .PHONY:run
13 run: run_py run_cc target
|
| /petsc/src/binding/petsc4py/demo/legacy/bratu2d/ |
| H A D | makefile | 16 test: run clean
18 .PHONY:run
19 run: run_py run_f90 target
|
| /petsc/src/binding/petsc4py/demo/legacy/wrap-f2py/ |
| H A D | makefile | 10 test: run clean
18 .PHONY:run
19 run: build target
|
| /petsc/src/binding/petsc4py/demo/legacy/wrap-cython/ |
| H A D | makefile | 10 test: run clean
18 .PHONY:run
19 run: build target
|
| /petsc/src/binding/petsc4py/demo/legacy/poisson3d/ |
| H A D | makefile | 15 test: run clean
17 .PHONY:run
18 run: run_py run_cc target
|
| /petsc/src/tao/unconstrained/tutorials/ |
| H A D | adjointreads.m | 19 % run('PDEadjoint/optimize06.m')
29 % run('tss.m')
48 run(file)
70 % run(file)
122 % run('PDEadjoint/optimize00.m')
124 % run('PDEadjoint/optimize04.m')
137 % run('fd.m')
141 % run('PDEadjoint/optimize01.m')
|
| /petsc/src/binding/petsc4py/demo/legacy/wrap-swig/ |
| H A D | makefile | 10 test: run clean
18 .PHONY:run
19 run: build target
|
| /petsc/doc/manual/ |
| H A D | tests.md | 51 node (via the batch system) and run the tests on that node (this assumes
67 system. The tests are run in `$PETSC_DIR/$PETSC_ARCH/tests` with
72 For example, test `vec_vec_tutorials-ex6`, which can be run e.g. with
84 These shell scripts can be run independently in those directories, and
85 take arguments to show the commands run, change arguments, etc. Use the
88 Often, you want to run only a subset of tests. Our makefiles use
109 It is useful before invoking the tests to see what targets will be run.
116 To see all of the test targets which would be run, this command can be
136 Include at the bottom of the test code a formatted comment indicating what tests should be run, see
137 {any}`test_harness`. Also select a directory where you wish the tests to be compiled and run, say `…
[all …]
|
| /petsc/src/binding/petsc4py/ |
| H A D | tox.ini | 2 # in multiple virtualenvs. This configuration file will run the
4 # "pip install tox" and then run "tox" from this directory.
|
| /petsc/src/dm/tests/ |
| H A D | ex12.m | 3 % From MATLAB run ex12(np)
10 % to create these run ./configure --with-matlab
|
| /petsc/ |
| H A D | gmakefile.test | 244 # - if run with MACOS_FIREWALL=1
320 # Targets to run tests in test-$pkg.$lang and delete the executables, language by language
322 # List of raw test run targets
332 # Targets to run tests and remove executables, by package-lang pairs.
405 else # No filter - run them all, but delete the executables as we go
408 showreport = "-s" # Only show full report when all tests are run
457 -@echo " check - run a basic check that the libraries are built correctly and can be used"
460 -@echo " getmpiexec - print the mpiexec to use to run PETSc programs"
467 -@echo " petsc4pytest - run the entire petsc4py test suite"
468 -@echo " alltests - run the entire PETSc test suite"
[all …]
|
| H A D | setup.py | 206 builder.PETScMaker().run()
223 install.Installer().run()
259 def run(self): member in cmd_install
276 _install.run(self)
|
| /petsc/lib/petsc/bin/ |
| H A D | petscmpiexec | 80 run=$(grep "MPIEXEC " "${PETSC_DIR}/${PETSC_ARCH}/lib/petsc/conf/petscvariables" | grep -v "#MPIEXE…
83 trun=$(echo "${run}" | sed -e "s,\\$MPI_BUILD_HOME,${MPI_BUILD_HOME},")
|
| /petsc/doc/developers/contributing/ |
| H A D | pipelines.md | 23 :::{figure} /images/developers/run-paused-pipeline.png
48 A job is a run of the {any}`PETSc test harness<test_harness>` and consists of many "examples".
49 Each test is a run of an example with a particular set of command line options
75 …then prompt you to push the branch of the MR, once pushed the listed jobs will automatically be run
82 …roperly formatted you will see an error from `make checkbadSource`. Always run `make checkbadSourc…
|
| /petsc/doc/developers/ |
| H A D | buildsystem.md | 60 can then use this object to access the results of the tests run by the
66 can be manipulated by the test environment. A compile or link can be run
95 Most systems, such as Autoconf and CMake, do not actually run tests in a
127 package root, which contains all the Python necessary to run (in addition
129 `configure.py`, which is executed to run the configure process, and a
170 The `configure()` method of the module will be run by the `Framework`
207 process, and a script to recreate the configure run.
225 modules for the configure run, using the `setupDependencies()` method.
281 for a configure run. It maintains a graph of all the configure modules
283 initiates the run, compiles the results, and handles the final output.
[all …]
|
| H A D | testing.md | 7 …d comments at the bottom of the tutorials and test source files that describes the tests to be run.
8 …arses the tutorial and test source files and generates the makefiles and shell scripts. This is run
9 automatically by the make system and rarely is run directly.
17 describe tests and subtests required to run executables associated with
52 - one or more `mpiexec` tests that run the executable
75 To run these tests one must first clone the datafiles repository and then set the environmental var…
81 inserted to describe the test(s) to be run. The elements of the test are
111 - A reference file with the *expected output from the test run*,
112 the output from the test run is compared with it (with a difftool).
137 to run.
[all …]
|
| /petsc/src/sys/tests/output/ |
| H A D | ex30_8.out | 1 # This program was run with logging synchronization. #
|
| /petsc/src/tao/leastsquares/tutorials/ |
| H A D | cs1.c | 111 PetscInt run; in ProcessOptions() local
118 run = ctx->tType; in ProcessOptions()
119 …"-test_type", "The coverage test type", "cs1.c", testTypes, 3, testTypes[ctx->tType], &run, NULL)); in ProcessOptions()
120 ctx->tType = (TestType)run; in ProcessOptions()
|