Make ExaConstit a callable library
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 70
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
While working with a number of workflow tools, it is starting to seem like it might be useful to make ExaConstit into a callable library. I don't imagine this requiring too many changes. The big thing would be that we would want to take in the same arguments we do now as well as an `MPI_Comm` argument.
Long term this action might also allow us to drive things from Python and feed data back there as well. However, we would need to break things down quite a bit more to get to that state and do some major refactoring.
Just to put some context into things, we're currently exploring https://emews.github.io/ as a ways to parameterize models on machines like Summit and Frontier.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by locating the current command-line entry point and its argument handling, then determine the API boundary needed to accept those arguments plus an MPI_Comm; done means ExaConstit can be invoked as a library without relying on the command-line workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100