Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • hyteg hyteg
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hyteg
  • hyteghyteg
  • Merge requests
  • !403

Merged
Created Mar 31, 2021 by Marcus Mohr@mohrDeveloper

Formally correct 3D implementation for two operators

  • Overview 0
  • Commits 2
  • Pipelines 1
  • Changes 6

The P2P1BlendingTaylorhoodStokesOperator and P2P1SurrogateTaylorhoodStokesOperator are formally implemented to work in 3D. However, due to missing 3D implementations of their underlying operators they can currently not be used in that setting. The formal implementation uses

  • P2ToP1ConstantDivzOperator div_z;
  • P1ToP2ConstantDivTzOperator divT_z;

Which the merge will formally replace by the corresponding blending/surrogate operator. This way is IMHO cleaner and the operators should work in 3D out-of-the-box, once the underlying operators get extended to 3D.

Cheers
Marcus

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: mohr/minor_fix