Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #1086
Closed
Open
Issue created Feb 23, 2017 by James Willenbring@jmwilleOwner

Panzer: access to field managers

Created by: rppawlo

@trilinos/panzer @eric-c-cyr Currently there is no clean way in the AssemblyEngine object to change/redirect MDField memory in between the workset evaluations. We have worked around this in a couple of ways in application codes. With some minor changes to panzer, we could make this operation easier to implement.

Options:

  1. Creating a field with memory for all worksets and then writing evaluators that use a workset index. field(workset_index,cell,point). Just need to add a workset index to the Workset object if it is not already there.
  2. Storing a vector of mdfields (one per workset) and using a setUnmanagedField() on the field manager. The AssemblyEngine hides the loops over worksets. We would have to allow users to inject calls within the assembly engine (probably via an observer or expanding the Evaluator interface) to allow for this.
Assignee
Assign to
Time tracking