SimVascular / SimVascular/svOneDSolver
Features to Add: Code Execution
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 22
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
These are features we should add for the future.
-
Graceful failures with incorrect input files (#19). Include error message and exits the code (without a segmentation fault) when the user provides an invalid input file.
-
Improve File I/O (#24). Writing out the data seems to be a bottleneck in the code runtime, so improvements to this could speed up simulations. Additionally, the VTK outputs could be converted from ascii to binary to produce smaller output files.
-
Clean up printed output (#26). Many lines are printed to the screen - we should decide what is necessary and what should be put into an output.txt file instead.
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 reading the referenced issues #19, #24, and #26, since this issue groups three separate future features. Identify the scope and completion criteria for graceful invalid-file failures, faster or binary file output, and cleaner printed output; the payload names no files, tests, or entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100