SimVascular / SimVascular/svOneDSolver

Output only text and move VTK to a post-processor

Open
#119 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
22
Forks
27
PR merge metrics
No merged PRs in 30d

Description

Problem

We can currently choose between text and VTK output. VTK output creates a visualization of tubes in 3D space that deform over time with arrays for pressure and flow rate. This visualization is nice but requires the user to choose the preferred post-processing method before running the simulation. Thus, there is only output possible, and it has to be known a priori. Furthermore, the input node*coord is currently mandatory but only required for VTK post-processing.

Solution

Remove VTK output from the solver and move it to a post-processor that can visualize text output in VTK.

Additional context

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct and Contributing Guidelines

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the solver's current text and VTK output paths, including where nodecoord is required. Then define the post-processor boundary and how it reads text output to produce the existing tube visualization with pressure and flow-rate arrays. Done means the solver emits text without requiring nodecoord, while a separate post-processor can recreate the VTK output.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
data-visualization
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.