[EPIC] Mesh infrastructure changes
Open
Nobody has claimed this yet.
EPIC
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
We are going to reorganize the mesh infrastructure to provide better separation between concepts.
Proposed object instantiation hierarchy
Issues in this EPIC
- Conceptually split
NodeManagerinto aVertexManagercontaining coordinate data/operators and aNodeManagerfor holding field data.
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 existing NodeManager concepts and the proposed object-instantiation hierarchy in this epic. Determine how coordinate data/operators differ from field data, then assess the related issues before separating VertexManager and NodeManager responsibilities. Done means the conceptual split is implemented and the epic checklist is complete.
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