Re-factoring of the kernel infrastructure for coupled problems.
Open
Nobody has claimed this yet.
type: cleanup / refactor
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
After merge of #2194
Describe the issue
Re organize the kernel infrastructure to address changes in requirements:
- Remove the
KernelBasehierarchy structure with a more independent strategy. Potentially implementation is done in static member functions in the kernel class, and callable from coupled kernels. - For the coupled problem, address the problem with the quadrature based over-allocation of cell data (i.e. porosity) for different constitutive models, and executing both cases in a single kernel.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the changes from #2194 and the existing KernelBase hierarchy. Trace how coupled kernels handle quadrature-based cell data and constitutive models. Done means replacing the hierarchy with the intended independent strategy and addressing over-allocation while executing the coupled cases together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100