Hi all,
How do you specify the surface ID's in the solver.inp file for calculating Wall Shear Stress? Where can I get/set this information for the particular face that I'm interested in?
Thanks!
A question about solver.inp file
- Justin Tran
- Posts: 109
- Joined: Mon Sep 30, 2013 4:10 pm
Re: A question about solver.inp file
Hi Akash,
In the solver.inp file, there is a command called "Surface ID's for Force calculation". Here, you can specify which surfaces you want wall shear stress calculations. The default setting is to specify the entire exterior surface of the domain for force calculation (i.e. surface ID 1).
Hope that helps!
In the solver.inp file, there is a command called "Surface ID's for Force calculation". Here, you can specify which surfaces you want wall shear stress calculations. The default setting is to specify the entire exterior surface of the domain for force calculation (i.e. surface ID 1).
Hope that helps!
- Akash Gupta
- Posts: 16
- Joined: Thu Jun 09, 2016 6:58 am
Re: A question about solver.inp file
Thank you for the answer, Justin!
I did exactly as you suggested but I repeatedly got this ouput from the solver:
Then I figured out the problem, I was directly copying the command from the appendix in SimVascular documentation (at:http://simvascular.github.io/docsFlowSolver.html). It turns out the apostrophe character in the "Surface ID's for Force Calculation:" command in the appendix is not an ASCII character. In fact, this forum wouldn't let me paste the command from my solver.inp file because of the same problem!
Once I replace the apostrophe with a regular apostrophe, the simulation ran just fine!
I did exactly as you suggested but I repeatedly got this ouput from the solver:
The number of processes is 24.
Solver Input Files listed as below:
------------------------------------
Local Config: solver.inp
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
Default Input File: Not Setup.
Parameter Values setup as below:
----------------------------------------------
Time Varying Boundary Conditions From File: True
BCT File Type: DAT
Number of BCT Files: 2
BCT Matching Type: Global Node ID
BCT Time Scale Factor: 1.0
Equation of State: Incompressible
Time Step Size: 0.001
Number of Timesteps: 1664
Viscous Control: Viscous
Number of Timesteps between Restarts: 52
Print Average Solution: True
Print Error Indicators: False
Number of Force Surfaces: 1
Input exception: required input variable not set: Surface ID's for Force Calculation
Input error detected:
Input Directive not understood
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
error during reading ascii input
Then I figured out the problem, I was directly copying the command from the appendix in SimVascular documentation (at:http://simvascular.github.io/docsFlowSolver.html). It turns out the apostrophe character in the "Surface ID's for Force Calculation:" command in the appendix is not an ASCII character. In fact, this forum wouldn't let me paste the command from my solver.inp file because of the same problem!
Once I replace the apostrophe with a regular apostrophe, the simulation ran just fine!
- Justin Tran
- Posts: 109
- Joined: Mon Sep 30, 2013 4:10 pm
Re: A question about solver.inp file
Hi Akash,
That is great news! Glad you got it working. Those ASCII character bugs are a pain to debug, and often the last thing I think about!
That is great news! Glad you got it working. Those ASCII character bugs are a pain to debug, and often the last thing I think about!