Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I INMOST
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Terekhov
  • INMOST
  • Wiki
  • 5400 Interval Permutation

5400 Interval Permutation · Changes

Page history
abcd authored Jan 19, 2015 by Kirill Terekhov's avatar Kirill Terekhov
Hide whitespace changes
Inline Side-by-side
5400-Interval-Permutation.md
View page @ f3bd8801
......@@ -40,10 +40,14 @@ For solver type argument the values have the following meaning:
##CMake tests
This test will seed solver_test000_serial_* tests for all activated solvers into CMake. Those test will check that solvers correctly get input and correctly output solution.
This test will generate solver_test000_serial_* tests for all activated solvers in CMake.
Those tests will check that solvers correctly get input and correctly output solution.
If USE_MPI is activated and CMake have variable ${MPIEXEC} set up correctly then the test will seed solver_test000_parallel_* tests. There test will check that solvers get input in parallel and correctly output solution as well as the solver will check correct functioning of permutation of local intervals. PETSc solver will avoid permutation test since it cannot handle the situation.
If USE_MPI is activated and CMake have variable ${MPIEXEC} set up correctly then the test will seed
solver_test000_parallel_* tests. These tests will check that solvers get input in parallel and correctly
output solution as well as the solver will check correct functioning of permutation of local intervals.
PETSc solver will avoid permutation test since it cannot handle the situation.
##Source
......
Clone repository
  • 0100 Compilation
  • 0200 Compilation Windows
  • 0201 Obtain MSVC
  • 0202 Obtain MSMPI
  • 0203 Compilation INMOST Windows
  • 0204 Compilation ParMETIS Windows
  • 0205 Compilation Zoltan Windows
  • 0206 Compilation PETSc Windows
  • 0207 Compilation Trilinos Windows
  • 0400 Compilation Linux
  • 0401 Install MPI
  • 0402 Compilation INMOST Linux
  • 0403 Compilation PETSc Linux
  • 0404 Compilation Trilinos Linux
  • 0405 Compilation ParMETIS Linux
View All Pages