Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation does not mention that you need to install svSolver #33

Open
ktbolt opened this issue Feb 18, 2020 · 0 comments
Open

Documentation does not mention that you need to install svSolver #33

ktbolt opened this issue Feb 18, 2020 · 0 comments
Assignees
Labels

Comments

@ktbolt
Copy link
Contributor

ktbolt commented Feb 18, 2020

The Quick Guide Simulation section does not mention that you need to install svSolver to run a simulation.

The Simulation Guide section wrongly states

Notice: To get full functions from the Simulation tool, it uses three solvers: Presolver (svPre), Flowsolver (svSolver), Postsolver (svPost). Normally, SimVascular already includes the solvers and can find them automatically. Users don’t need to set up the solvers. However, in case SimVascular can’t find them while users are using the Simulation tool, refer to Solver Configuration.

There are not three solvers and they are not included in SV.

In the Simulation Guide/Configurating Solvers (Optional) section contradicts the above section and does hint that you may need to install svSolver.

SimVascular solvers(presolver, flowsolver, postsolver) are used as individual executable programs. They are called by SV Simulation tool to create data files, run simulation, and convert results to files in VTK formats. Normally those solvers are installed separately. However, SimVascular can automatically find those solvers. In case your SimVascular can’t find them, or you want to use different solvers, you need to explicitly tell SimVascular where to find or how to use them.

I will add a section (not optional) that states that svSolver needs to be installed and how to install it.

@ktbolt ktbolt added the bug label Feb 18, 2020
@ktbolt ktbolt self-assigned this Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant