-
Notifications
You must be signed in to change notification settings - Fork 59
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
FWH permeable surface #100
Comments
Hi, for a 2D case you can select any depth of a domain. But you must set corresponding normalizing length (dref) in the dictionary. You can see old versions of library as an example, e.g. https://github.com/unicfdlab/libAcoustics/tree/digitef-dev-1912/Tutorials/monopole2D . But, please be careful with the 2D version of the library. Later we've found that while this simplification may be good for learning / testing purposes, it might be also incorrect from the physical point of view. |
Thank you for replying. Thank you for your great works |
You can try both variants: when an STL surface has precisely the same depth, as an computational domain or when an STL surface intersects boundaris of a 2D domain. |
It looks like, I don't have a 2D case with STL surface. So, you should build it yourself and post here your questions. |
@mkraposhin Thank you for replying. May I have some questions? Thank you and Best Regards |
First of all thank you for creating Acoustic library,
I have some questions. In order to create FWH surface for both 2D & 3D cases, What Should I do?
Should I create STL file in ASCII format and then put it inside constant folder and create trisurface folder and paste inside it and the use:
is this correct? what about 2d cases? I mean what should I do with the domain depth?
Farassat1A-triSurface
{
type FfowcsWilliamsHawkings;
formulationType Farassat1AFormulation;
#include "commonSettings";
patches ();
interpolationScheme cellPointFace;
);
Thank you again in advance for your replying.
I greatly appreciate your time and I look forward to hearing from you soon.
The text was updated successfully, but these errors were encountered: