Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More

Memberships

CFD Dose

Public • 1k • $149/m

14 contributions to CFD Dose
Clearances in CFD
Hello, can someone give me a hand? I have to do a CFD analysis in Ansys Fluent of a rocket that we are going to manufacture for the student association I belong to. The problem is that the CAD file, as it is designed to be manufactured, has a lot of clearances and holes and when I import the geometry, put the enclosure and extract the geometry, as it has clearances the mesh gets into the gaps. Is there a simple way to change the CAD so that it only takes the outer surface (as if I put a cloth over the Rocket).
2
19
New comment Jun 21
Clearances in CFD
0 likes • May 20
A word about animation tools - Animation modeling is not CAD / Solid Modeling, and often has very little in the way of constraints to enforce geometric fidelity. In other words, just because Blender lets you close a hole, does not mean the hole is watertight. We used to have issues like this with Rhino - great tool for creating splines for ship hulls, but the curves it created were often a massive headache for CFD.
0 likes • Jun 21
@Haris Hameed Mian I know STAR-CCM+ has a wrapper, and I am pretty sure other CFD tools also have them. How well they work for any particular geometry model varies quite a bit across the tools and the geometry, but they can provide water-tight geometry. Obviously clean CAD with all the steps and gaps defeatured is preferred, but not necessary, and frankly, not always an available option.
reccomended number of cores
I use alibaba cloud for my simulations and I want to ask for the specific context of either compressible or incompressible flows how many cores are reccomended.
1
3
New comment Jun 7
0 likes • Jun 1
Depends on the CFD code and the MPI it's using, as well as the cluster specs (CPU at each node, memory per node, data transmission infrastructure between nodes, etc.). A good rule of thumb is to not drop below 25K cells per node, as by that point, you are generally spending more time splitting and reassembling the domain than you are actually solving the mesh on each node. If you want to go below that, you'll need to run some benchmarks. It's pretty easy to do. Just create a basic problem (sphere or cylinder in flow), give it a healthy mesh, and run it on the cluster. Try 5K/node, 10K/node, 25K/node, 50K/node, 100K/node. Those 5 tests should give you an idea where the inflection point is.
Gauging Interest
Would the members of the group be interested in a Software Development Primer. This would not be a "How to program in Python / Java / C++" kind of Primer, but rather what makes a person a good developer versus a person who just knows how to program somethin in Python?
Poll
15 members have voted
5
2
New comment May 20
0 likes • May 20
I have a quick trip over the next two days, then I will get started on this.
Some very general advice for CFD...
The following comes from a couple of comments I made, and I thought it might help to have these comments not buried in a post. So... Why CFD? CFD will very rarely match complex flow reality. It can, but the level of effort required is considerable, so it's very rarely done. That said, it is very important to keep in mind what, exactly, you are running the CFD simulation for? - Are you trying to match complex experimental results? - Are you trying to approve / discard designs? - Are you exploring a prototype in detail? - Are you trying to validate the code? etc. If you want to match experimental results, you are probably going to need A LOT of nodes on the cluster, and all the RAM you can beg, borrow, or steal, because your cell count is going to be in the hundreds of millions. This is called Direct Numerical Simulation (DNS), it is difficult and expensive. And be ready to restart that simulation a dozen times while you tweak the ICs, BCs, and relaxation factors. On the plus side, setting up the physics is dead simple, since you won't have any turbulence models, or any other models that attempt to handle complexities in simple ways. Let's talk about physics models. What is a physics model? What is a turbulence model? A turbulence model is, by definition, a simplified model of the turbulence a given flow field will experience. While the models are often very good, they are still models, built with a large number of assumptions, many of which are not correct, but which are "good enough". ALL of the models in a given CFD package are, in some way or another, a handy and acceptable simplification of the physics at play. Thus, they will never get it exactly right. Validating CFD software usually does match reality, because the cases used to validate are exceptionally well understood, and the tweaks are in the research paper everyone reads when setting up the validation case. These are the exceptions. Design exploration is where you want that high fidelity, but you can't afford it. You don't have the time or computing resources, so you go with the best fidelity you can and you target specific things. If I'm looking at how the flaps on a wing impact lift and drag, I'm not going to try to model the flow around the empennage, or through the engine nacelle. Those are getting some pretty basic assumptions and BCs/ICs, along with a coarse mesh, and I simply expect that the fidelity in those areas will be low. If I see evidence of some interesting fluid structures that could be the result of (for example) interactions between the flaps and the engine nacelle, then I'll refine the mesh and re-evaluate the assumptions.
4
2
New comment May 8
3 likes • May 8
A day in the life of a CFD Analyst: 1) You are given geometry and one or more questions about the flow that need answering. 2) You load the geometry, defeature and make watertight as needed (sometimes the CFD analyst does this, sometimes someone from the CAD group does it). 3) You identify and Tag / Label edges, surfaces, and volumes. 4) You create a flow domain. 5) You build out the physics models (materials, turbulence, etc.). 6) You create the post processing you will need (if your solver allows for). If you can't create it ahead of time, you should have a very clear set of post targets you will need to create once you have a solution.* 7) You mesh it, paying attention to the questions that need answering. 8) You setup your solvers and run them. 8a) You troubleshoot the geometry / mesh / solvers as needed until the solution converges. 9) You examine your post processing and make sure the solution makes sense to your engineering knowledge and experience. If you aren't sure, call for a 2nd or 3rd opinion. 10) Assuming the solution looks reasonable, you write it up and pass it to whoever needs it next. * Building out post processing before solving is preferred, because you can usually use some of that post processing to check your solution for convergence.
2 likes • May 8
Troubleshooting a CFD Simulation: 1. Are you using the correct physics for the problem at hand? Are you running segregated when coupled is more appropriate? Is the turbulence model selected adequate to the flow domain? Is the time domain correct? Implicit or explicit? etc. 2. Is the domain large enough? Do you have highly turbulent flow trying to cross a boundary that can't handle it? Is there back flow on an inlet? 3. Are your BCs correct? Are they the correct type? Do they have reasonable values for the domain? 4. Are your ICs correct? Should you perhaps use a simple solution to initialize the whole flow field? 5. Did you run mesh diagnostics? If not, now is the time. If you did, re-run the diagnostics after expanding the range to check for. Look for cells that highly skewed, or oriented in a way that would give the solver a hard time when computing the flow (i.e. none of the faces are even close to perpendicular to the expected flow). 6. Are you using the correct mesh type? Are your running Tets when Quads would be better? Or a Trimmer mesh, or Polyhedral? 7. If the mesh is good, look for areas that may need more resolution, or less. This is counterintuitive, but going back to my comment on your other post, you only want density where you need resolution. If you have an area of high cell density in a location that is not important to the question being answered, you may have a problem. Sometimes you really want the flow to diffuse out complex turbulent structures. Think about reducing the mesh density and/or defeaturing that area. 8. Look over all of the post processing you have, see if anything stands out. Never trust the residuals plot to tell you want is wrong (just like you shouldn't trust a residuals plot to tell you a solution is converged!). If nothing looks amiss, build out more post processing to cover other areas. Set all the post processing to save at every iteration or time step (sometimes by the time the solver quits, the flow domain is a confusing mess - being able to go back a bit to a point before the solver started to choke can be insightful). 9. Get help. Honestly, you can ask for help at any point, but it is a good exercise to run down this list on your own first.
CFD PROFFESIONALS LEVEL
HI every one Iam looking to develop my self in the CFD field ,my experience with CFD was doing aerodynamics CFD simulations in Ansys fluent for a formula student car just following the steps and recommendations from the resources we had found ,I Want develop my self more so I want to know the things that would help me reach a good level . the second question what is the day to day tasks look like for CFD professionals ? , thank u .
4
5
New comment Jun 1
4 likes • May 7
1) You are given geometry and one or more questions about the flow that need answering. 2) You load the geometry, defeature and make watertight as needed (sometimes the CFD analyst does this, sometimes someone from the CAD group does it). 3) You identify and Tag / Label edges, surfaces, and volumes. 4) You create a flow domain. 5) You build out the physics models (materials, turbulence, etc.). 6) You create the post processing you will need (if your solver allows for). If you can't create it ahead of time, you should have a very clear set of post targets you will need to create once you have a solution.* 7) You mesh it, paying attention to the questions that need answering. 8) You setup your solvers and run them. 8a) You troubleshoot the geometry / mesh / solvers as needed until the solution converges. 9) You examine your post processing and make sure the solution makes sense to your engineering knowledge and experience. If you aren't sure, call for a 2nd or 3rd opinion. 10) Assuming the solution looks reasonable, you write it up and pass it to whoever needs it next. * Building out post processing before solving is preferred, because you can usually use some of that post processing to check your solution for convergence.
3 likes • May 8
@Mina Alexan Troubleshooting a CFD Simulation: 1. Are you using the correct physics for the problem at hand? Are you running segregated when coupled is more appropriate? Is the turbulence model selected adequate to the flow domain? Is the time domain correct? Implicit or explicit? etc. 2. Is the domain large enough? Do you have highly turbulent flow trying to cross a boundary that can't handle it? Is there back flow on an inlet? 3. Are your BCs correct? Are they the correct type? Do they have reasonable values for the domain? 4. Are your ICs correct? Should you perhaps use a simple solution to initialize the whole flow field? 5. Did you run mesh diagnostics? If not, now is the time. If you did, re-run the diagnostics after expanding the range to check for. Look for cells that highly skewed, or oriented in a way that would give the solver a hard time when computing the flow (i.e. none of the faces are even close to perpendicular to the expected flow). 6. Are you using the correct mesh type? Are your running Tets when Quads would be better? Or a Trimmer mesh, or Polyhedral? 7. If the mesh is good, look for areas that may need more resolution, or less. This is counterintuitive, but going back to my comment on your other post, you only want density where you need resolution. If you have an area of high cell density in a location that is not important to the question being answered, you may have a problem. Sometimes you really want the flow to diffuse out complex turbulent structures. Think about reducing the mesh density and/or defeaturing that area. 8. Look over all of the post processing you have, see if anything stands out. Never trust the residuals plot to tell you want is wrong (just like you shouldn't trust a residuals plot to tell you a solution is converged!). If nothing looks amiss, build out more post processing to cover other areas. Set all the post processing to save at every iteration or time step (sometimes by the time the solver quits, the flow domain is a confusing mess - being able to go back a bit to a point before the solver started to choke can be insightful). 9. Get help. Honestly, you can ask for help at any point, but it is a good exercise to run down this list on your own first.
1-10 of 14
Shane Gillis
3
21points to level up
@shane-gillis-8518
I'm a Tech Geek who has fused my love of engineering and CFD with my background in computer systems admin and software development.

Active 175d ago
Joined Apr 12, 2024
powered by