Skip to content
Snippets Groups Projects

Repository graph

You can move around the graph by using the arrow keys.
Select Git revision
  • bugfix/fix_rigidbodymotion_difference
  • decasteljau
  • feature/ARRN-mod
  • feature/HM-numericalBenchmark
  • feature/HarmonicmapsBenchmark
  • feature/SimoFoxWithLocalFEfunctions
  • feature/bendingIsometries
  • feature/bendingIsometries-PBFE-Stiefel
  • feature/harmonicmapsAddons
  • feature/introduceRetractionNotion
  • feature/riemannianTRaddons
  • feature/simofoxBook
  • fix-fd-gradient-scaling
  • fix_localrodassembler_compiler_error
  • issue/vtk-namespace
  • make_rod-eoc_run
  • master default
  • releases/2.0-1
  • releases/2.1-1
  • releases/2.10
20 results
Created with Raphaël 2.2.023Jan222119171413109514Dec1319Nov1087519Oct181473Sep2131Aug17151311May29Apr282726232221191528Mar2322181714131098726Feb191817161513121110965421Jan191323Oct2221191513824Sep19Aug526May17126530Apr2928272322212019181716865Feb211Jan30Dec282529Oct24Jul232111Jun96519May1218Apr9Mar87643Jan31Dec20Nov1523Oct22171612428Sep5Generalize the rod DtN map to the case with two coupling boundariesadd simple const access methods to the rod datahand the continuum Dirichlet values to the complex, not the Steklov-Poincare stepadd method to set the ignoreNodes after solver creationCreate rod by interpolating between two endpoints, which are expected to be already in the result containerdo not use a LocalGFEFunction for the interpolation. It is not working properly yetuse a map to store the continuum forcesChange interface of the Steklov-Poincare step class to allow for more than one couplingstore the reference interface orientations in the RodContinuumComplex, where they should beGeneralize the continuum Dirichlet-To-Neumann map.make mergeDirichletAndCouplingBoundaries work for more than one rod couplingrename method introduced in the last commitmove the merging of continuum Dirichlet and coupling boundaries into a separate methodGeneralize setup of the dirichletAndCouplingNodes field...Start adding support for more than one rod/continuum.hack-removal: don't hardwire the St.Venant-Kirchhoff materialcentralize all information a RodContinuumComplex keeps about a continuum in a special structcentralize all information a RodContinuumComplex keeps about a rod in a special structsupport for parallel computationsbugfix: properly implement setRotationbugfix: add the continuum Dirichlet boundary to the complexremove some debugging outputin exp: assert that the tangent vector is orthogonal to the quaternion unit spherebugfix: set proper Dirichlet nodes for the continuum problemadd simple access to continuum Dirichlet boundariessimplification: build only the leaf Dirichlet boundary, instead of all level onesbugfix: need call-by-reference instead of call-by-valueimplement the rotation part of 'setRotation'fix misplaced parenthesis in an assertionassert that projection onto a tangent space does the right thingupdate to current version of dirneucoupling.ccbugfix: rod interface boundary wasn't written to the RodContinuumComplexbugfix: use operator[] instead of find() if you want to force creation of a non-existant entry in a std::mapbugfix: the complex is a const referenceadd simple const access to various memberscleanup; use more tangent vectors to stay closer to differential geometrymove the 'nonlinear' continuum Dirichlet-to-Neumann map into a separate methoddon't store the continuum interface boundary in the Steklov-Poincare step -- use the one from the complex insteadstore the continuum interface boundary in the RodContinuumComplexmoved the nonlinear rod Dirichlet-to-Neumann map into a separate method