Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • shell-support-localintegralstiffness
  • feature/ARRN-mod
  • feature/simofoxBook
  • releases/2.10
  • issue/vtk-namespace
  • feature/bendingIsometries
  • feature/HM-numericalBenchmark
  • feature/bendingIsometries-PBFE-Stiefel
  • feature/HarmonicmapsBenchmark
  • feature/harmonicmapsAddons
  • feature/riemannianTRaddons
  • feature/SimoFoxWithLocalFEfunctions
  • simofoxgradHess
  • decasteljau
  • feature/introduceRetractionNotion
  • use-dune-parmg-for-global-indices
  • make_rod-eoc_run
  • fix_localrodassembler_compiler_error
  • use_dune_add_test
20 results
Compare
user avatar
[bugfix] The solver must always use the global Dirichlet vector
Oliver Sander authored 
Even if there is only one processor.  Because even then the local
and global vectors differ in their ordering.

[[Imported from SVN: r9757]]
6384b92d
History
user avatar 6384b92d
History
Name Last commit Last update
..
coupling
parallel
Makefile.am
adolcnamespaceinjections.hh
averagedistanceassembler.hh
averageinterface.hh
cosseratenergystiffness.hh
cosseratstrain.hh
cosseratvtkwriter.hh
geodesicdifference.hh
geodesicfeassembler.hh
geodesicfefunctionadaptor.hh
gfedifferencenormsquared.hh
globalgeodesicfefunction.hh
globalgfetestfunction.hh
globalgfetestfunctionbasis.hh
gramschmidtsolver.hh
harmonicenergystiffness.hh
hyperbolichalfspacepoint.hh
linearalgebra.hh
localgeodesicfeadolcstiffness.hh
localgeodesicfefunction.hh
localgeodesicfestiffness.hh
localgfetestfunctionbasis.hh
localprojectedfefunction.hh
maxnormtrustregion.hh
orthogonalmatrix.hh
pktop1mgtransfer.hh
quaternion.hh
realtuple.hh
riemanniantrsolver.cc
riemanniantrsolver.hh
rigidbodymotion.hh
rodassembler.cc
rodassembler.hh
rodfactory.hh
rodlocalstiffness.hh
rodreader.hh
rodwriter.hh
rotation.hh
skewmatrix.hh
svd.hh
symmetricmatrix.hh
targetspacertrsolver.cc
targetspacertrsolver.hh
tensor3.hh
tensorssd.hh
unitvector.hh