You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suppose this is not really an issue, but I didn't know where to ask (depending on the answer, perhaps this could turn into an issue). Most of the examples in the repo are of external flows, so it is not clear to me how (or if) I can setup a simulation for flow in a curved pipe where the normal vectors of the input/output surfaces/planes may not be on the same line, for example. It seems you need to have the plane of the inlets/outlets be orthogonal because a structured grid is used, which I understand is fundamental to the method. Is there no way around this with some tricks with the SDF maybe?
The text was updated successfully, but these errors were encountered:
While you can do internal flow simulations with a Cartesian grid method like Waterlily, it's typically not the best approach. The flow in a bending pipe or channel would be more efficient with a curvilinear coordinate system. A turbine moving inside a duct would be a good use of immersed boundaries in a curvilinear or overset system [DOI: 10.1115/1.4063753], but I don't think that's planned for Waterlily any time soon.
What if you have a geometry that is a "complicated" pipe such as blood vessels where tortuosity is high with bifurcations and highly irregular cross-section diameters?
I suppose this is not really an issue, but I didn't know where to ask (depending on the answer, perhaps this could turn into an issue). Most of the examples in the repo are of external flows, so it is not clear to me how (or if) I can setup a simulation for flow in a curved pipe where the normal vectors of the input/output surfaces/planes may not be on the same line, for example. It seems you need to have the plane of the inlets/outlets be orthogonal because a structured grid is used, which I understand is fundamental to the method. Is there no way around this with some tricks with the SDF maybe?
The text was updated successfully, but these errors were encountered: