Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • M mfront-wrapper
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • navier-fenics
  • mfront-wrapper
  • Issues
  • #9
Closed
Open
Issue created Mar 09, 2020 by Jeremy BLEYER@jeremy.bleyerOwner

Handle plate models

For plate models, we want to integrate the behaviour at NG = nG x mG Gauss points in total where nG is the number of Gauss points on the plate 2D mesh and mG the number of Gauss points across the thickness.

We need a mechanism to handle the case of non-matching values between NG (used to load the behaviour) and nG the number of Gauss points for the 2D mesh. In addition to just reshaping the appropriate arrays, we can have different expressions for the same gradient depending on the z-coordinate, the integration weights in the form may also be different from one z-Gauss point to another.

Possible syntax:

problem.register_gradient("Strain", [sym(grad(u-zi*theta)) for zi in z_Gauss], weights=w_Gauss)
Assignee
Assign to
Time tracking