Angular Velocity as an inlet condition

Provides a system for patient-specific cardiovascular modeling and simulation.
POST REPLY
User avatar
Rohan Shad
Posts: 3
Joined: Thu Nov 15, 2018 4:16 pm

Angular Velocity as an inlet condition

Post by Rohan Shad » Wed Jan 23, 2019 7:26 pm

I was wondering if there's a way to set up angular velocity as an inlet boundary condition? For example when trying to model the natural rotational component of cardiac flow through the aortic valve, do I edit parameters in the "initial velocities" section in the simulation sidebar?

My understanding is that the parameters in "initial velocities" are for x, y, z, components of velocity, and my inlet flow file can only dictate the flow rate for my boundary condition.

User avatar
Weiguang Yang
Posts: 110
Joined: Mon Apr 07, 2008 2:17 pm

Re: Angular Velocity as an inlet condition

Post by Weiguang Yang » Thu Jan 24, 2019 11:05 am

You can try to modify bct.dat to set up velocity components for each inlet node.
The first line in bct.dat tells you how many nodes on inlet faces.
Starting from the second line, for each node i, nodal coordinates, velocity components and time are listed as follows,
x_i, y_i, z_i, n
u1_i, v1_i, w1_i, t1
u2_i,v2_i,w2_i,t2
....
un_i,vn_i,wn_i,tn
where n is the number of time points in a cardiac cycle, say n=100.

User avatar
Rohan Shad
Posts: 3
Joined: Thu Nov 15, 2018 4:16 pm

Re: Angular Velocity as an inlet condition

Post by Rohan Shad » Thu Jan 24, 2019 12:22 pm

Thanks for responding Weiguang,

So would the workflow for this look something like:
Open bct.vtp in Paraview > Identify node IDs > manually calculate u / v / w components for the angular velocity for each node >write to bct.dat file?

For very dense meshes, this method would probably become very tedious very quickly..

Rohan

POST REPLY