Skip to content
Snippets Groups Projects
Select Git revision
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • develop default protected
  • feature/composite-scheme
  • hyperplastic
  • feature/local-dt-fsi
  • feature/kinetic-schemes
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • feature/escobar-smoother
  • feature/hypoelasticity-clean
  • feature/hypoelasticity
  • feature/Navier-Stokes
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
32 results

CMakeLists.txt

Blame
    • Stéphane Del Pino's avatar
      34459135
      Replace SparseMatrixDescriptor by CRSMatrixDescriptor · 34459135
      Stéphane Del Pino authored
      The new class is meant to be much faster
      - it requires an estimation of the number values per row
      - if the number of stored values per line exceeds the reserved one, an
      a special storage zone (per row) is used.
      
      It is important to give a precise estimation of the number of values
      per rows:
      - if the provided expected number of values is too small with regard
      to the real number of values stored for a given row, then building
      performances can be noticeably affected
      - if the provided expected number of values per row corresponds
      exactly to the effective number of stored values, then the
      construction of the CRSMatrix costs nothing.
      
      In the later case, one benefits from a significant CPU and memory
      costs reduction.
      34459135
      History
      Replace SparseMatrixDescriptor by CRSMatrixDescriptor
      Stéphane Del Pino authored
      The new class is meant to be much faster
      - it requires an estimation of the number values per row
      - if the number of stored values per line exceeds the reserved one, an
      a special storage zone (per row) is used.
      
      It is important to give a precise estimation of the number of values
      per rows:
      - if the provided expected number of values is too small with regard
      to the real number of values stored for a given row, then building
      performances can be noticeably affected
      - if the provided expected number of values per row corresponds
      exactly to the effective number of stored values, then the
      construction of the CRSMatrix costs nothing.
      
      In the later case, one benefits from a significant CPU and memory
      costs reduction.