-
Notifications
You must be signed in to change notification settings - Fork 90
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
General Questions about Future Features and Overall Usage #67
Comments
Hi! I'm sorry that I came across your thread just today. It's been almost 4-5 months since I accessed the code. I am also sailing on an almost similar boat wrt features and usage of the code. Regarding your queries - By default the initial conditions profile should be kept 4. This is named as CODE_PROFILE, though in the inputs.md page https://github.com/ucns3d-team/UCNS3D/blob/master/docs/inputs.md Reg. other doubt, All conditions which we specify in the UCNS3D.DAT are taken as inlet/freestream conditions. For code profile (or) initial conditions profile set to 4, the values specified for these variables are used as the inlet values. FREE-STREAM CONDITIONS This is the way freestream values are set. There are no unit conventions followed. We need to enter all values from the same SI unit of our choice. Being a user, I am not in a position to guide/help any further with your queries. |
Hi SRKumar97, thanks for getting back to me! I actually have been figuring things out as well by going through the examples/making modifications and seem to have gotten a handle on it since making this post. Thanks for your help however as I am sure it will be helpful to newer users. |
Hi, I am a current doctoral student seeking to use this code/develop it for my research project. I was able to find the test cases and run them no problem, but currently, my group aims to make grids independently and write them to Fluent format (.msh format) so there is some trial and error here to get the format correct. I wanted to request/ask about some things I noticed in my brief exposure to the test cases and hope this serves as a useful post for first time users seeking the same basic answers when using the code:
Are there plans to support more generic grid formats (e.g., Plot3D, CGNS, etc.)? My group uses GMSH to make structured grids, but it has been a bit tedious to convert it to a usable format manually. I understand most output seems to be from commercial packages like Pointwise, but having a generic mesh option like Plot3D would be really helpful.
I saw between the ILES and DDES/RANS cases, there's a distinction between using an initial conditions profile 4 and 95. I looked through the various case .dat files provided but do not understand how I would be able to distinguish between using ILES and DDES outside of choosing to use a specified wall model; is it more due to the spatial order of accuracy being used?
I see at the bottom of the end of the input.md file on the Github page that freestream conditions must be made for any inlet/outlet profiles. For any BCs, where do I specify the actual conditions (e.g. pressure for pressure-outlet, or wall temperature in laminar Navier-Stokes simulation)? If this is specified within the input deck, how would I go about this? Further, if this is specified in the initial profile 4, how can I format this/find a template for the initial profile 4 and 95 to understand what inputs may be possible? I understand I can make a new profile in the source code through modification of the profile.f90 file, but is this the approach for any new cases to be run? In the event I run an isothermal wall and need to specify the wall temperature, how would I specify this in a new profile I am to make (if you all can give a quick pointer as an example)?
I saw that there were some capabilities for multi-component gas for inviscid simulation; are there any plans to add multi-species capabilities for viscous flows? My work will revolve around viscous reactive flow modeling, so the plan was to develop the solver to add such capabilities suited to my area of research, but I was not sure if that was something you all may be considering already.
Can I specify spatial/temporal-varying input profiles to an inlet condition/are user-defined functions for BCs supported? If so, what is the best approach to add this capability to an existing profile for a run?
Apologies if any of these questions may be trivial, as this is my first time navigating such a code. I want to be sure I am navigating the code effectively/understanding how to best use it. Thanks for your time.
The text was updated successfully, but these errors were encountered: