How to fix warning about faces of bodies were not automatically separated as shown in picture below?
December 4, 2020 at 6:55 amJannahSubscriberDecember 4, 2020 at 9:49 amRobForum ModeratorI suspect you have many surfaces and the meshing tool hasn't split these to avoid getting an excessive number of labels. Try and follow the workflow through and see what you get in Fluent solver. As a comment, if you use Named Selections (Groups) in SpaceClaim you can label surfaces you need as boundary conditions there, makes it easier when you get to the solver. nDId you want Japanese script? If not have a look in the installation sections as this was a common question before the summer. nDecember 7, 2020 at 1:32 amJannahSubscriberHi Bob, thank you for your response.nBefore importing the model from Space Claim, I already label surfaces such as inlet, outlet , and other labels. Also as the model has 3 different physical properties i made labels for that too that might be needed as boundary conditions later in Fluent simulation.nAs you wrote above, did you suggest I don' have to solve the warning and should just follow the workflow until the last step which is volume meshing?nAbout the script, I don't need the Japanese one and the English version also will be okay. Im sorry to ask but what do you mean of installation section? Did you mean question like this already being asked before? Im new for this so I don' understand much.December 7, 2020 at 3:15 amKeyur KanadeAnsys EmployeeFrom the information given, I believe you can ignore this warning and proceed to volume meshing. nYour surface mesh looks good. nIf required you can insert improve surface mesh command by right click. nRegards,nKeyurnHow to access Ansys Online Help DocumentnHow to show full resolution imagenGuidelines on the Student CommunitynHow to use Google to search within Ansys Student CommunitynDecember 7, 2020 at 3:59 amJannahSubscriberHi kenyur, thank you for your response.nI will try inserting improve surface mesh command and proceed to volume meshing.nBest regards,nJannahnDecember 7, 2020 at 5:08 amJannahSubscriberHi Kenyur,nI want to ask a question.nMay I know the reason I can ignore this warning? Is the warning didn't affect much my mesh generation so it still be okay to proceed to volume meshing?.December 7, 2020 at 6:57 amDecember 7, 2020 at 8:45 amJannahSubscriberHi Rob, nI want to ask detailed about what do you mean by labels. Did you mean the labels that I created in Space Claim?nSo if I reduce the number of labels, does that mean the warning will not appear?nThank younBest regards,nJannahnDecember 7, 2020 at 8:53 amDecember 7, 2020 at 1:50 pmRobForum ModeratorThe labels are from SpaceClaim. When you also label the volumes it can cause the surface labels to be split up as each volume will have a separate surface. If you put all the volumes into one label it doesn't split the surfaces unless you specifically label them. nThe mesh looks a bit coarse through the yellow/blue stripes. You may not need a BOI as setting a local surface sizing may be sufficient. nFor some reason a few versions back everyone managed to install the Japanese language onto Fluent, so the solution to fix it is most likely in the Installation section. The magnifying glass icon & search text boxes ought to find the solution if you want to change it. nDecember 8, 2020 at 12:31 amJannahSubscriberHi Bob, thank you for the response and explanation.nI will try specifically label the volume with separate surface and see what I get in the results.nAbout local sizing, BOI also one of the local surface sizing right? Do you mean I should try another types of local sizing such as face of size instead of BOI?nRegards,nJannahnDecember 8, 2020 at 2:08 amDecember 8, 2020 at 3:53 amKeyur KanadeAnsys EmployeeBOI is also a local sizing. nYou can try giving face sizing as well. nAre you considering solid as well? nIf you do not want mesh in solid, please make its type to 'dead'. nAlso from image, it looks like you can take advantage of periodicity. Please check forum for periodicity related posts. Please see help manual for more details about these commands. nAs mentioned by Rob, please give labels to bodies in SpaceClaim.Regards,nKeyurnHow to access Ansys Online Help DocumentnHow to show full resolution imagenGuidelines on the Student CommunitynHow to use Google to search within Ansys Student CommunitynDecember 9, 2020 at 12:28 amJannahSubscriberHi Keyur and Rob,nThanks for your response. nHere I want to update about my mesh. Before that, I want to ask a question. About warning that I got after surface meshing, you said that I should ignore the warning and proceed to volume meshing. May I know the reason in term of effect on quality mesh etc? Is that warning is common? And in what cases that warning can be ignored?.I already labeled bodies like this referred to the images above. And yes Im considering solid too.nnI tried meshing again and setting the local size-BOI because for a body. I got warning something about share topology but I checked again my model in Space Claim whether I included body that I set as BOI in share topology or not and apparently BOI not included and I believe I can ignore the warning.nThis is the result of my volume meshing overallnI think my mesh this time is finer than previous one and looks okaynDecember 9, 2020 at 2:51 pmRobForum ModeratorIt's still pretty coarse towards the hub. Adaption may be a solution to this though. nDecember 14, 2020 at 12:09 amJannahSubscriberHi Rob, thanks for the reply.nWhat do you mean by adaption? Im not familiar with that term though. Is it the same as mesh refining?nCan you answer my question about this. About warning that I got after surface meshing, Mr. Keyur said that I should ignore the warning and proceed to volume meshing. May I know the reason in term of effect on quality mesh etc? Is that warning is common? And in what cases that warning can be ignored?.December 14, 2020 at 11:53 amRobForum ModeratorAdaption means the cell splitting (refinement) that's in Fluent. It takes the existing mesh and splits cells up. We often use it where we want to refine a zone due to something in the flow rather than return to the meshing software. nIgnoring warnings needs to be done on a case by case basis: there's a reason they're there but they're not always helpful. A rough rule of thumb is if you're not sure try it and see what happens, if the task fails review the outcome and consider the warning as a probable cause.December 14, 2020 at 11:39 pmJannahSubscriberHi Bob, thanks for the reply.nThe explanation helped me a lot.nIn my case, I proceeded to the volume meshing eventhough the warning from surface mesh are there and there are no errors or warnings appeared in my volume meshing result. So it can be considered that the warning did not affect my meshing and I don'thave to solve the warning from that surface mesh.nnDecember 21, 2020 at 12:09 amJannahSubscriberI have a question regarding the warning and its solution.nAs you said, if the task fails review the outcome, what kind of things and aspects that I should check? How do I check it? For example, if there is no error but the result is affected, how do you specifically check it? I still wondering about the warning that I got as I stated above and I have no idea what is causing this or how to fix it. I keep thinking what kind of warning it is likely to affect the analysis result.nRegards,nJannahnDecember 21, 2020 at 2:50 amDecember 22, 2020 at 2:14 amJannahSubscriberHi nIm so sorry for asking too many questions because I really have no idea whats happening and needs to meet project deadlines.nIn Space Claim, I have tried combining all the parts as one body so the number of labels and parts reduced. When I created mesh using this geometry, no warning appeared and it is a good thing. From this I able to understand that the excessive number of labels could be one of causes why the warning appeared. But in my project I cannot combine all the parts as one body because they have different physical properties that later I will specify the characteristics in ANSYS Fluent. Is it possible to mesh the parts separately?nRegards,nJannahViewing 20 reply threads
Ansys Innovation Space
- You must be logged in to reply to this topic.
Boost Ansys Fluent Simulations with AWS
Computational Fluid Dynamics (CFD) helps engineers design products in which the flow of fluid components is a significant challenge. These different use cases often require large complex models to solve on a traditional workstation. Click here to join this event to learn how to leverage Ansys Fluids on the cloud, thanks to Ansys Gateway powered by AWS.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.Trending discussions
- Floating point exception in Fluent
- What are the differences between CFX and Fluent?
- Difference between K-epsilon and K-omega Turbulence Model
- Getting graph and tabular data from result in workbench mechanical
- The solver failed with a non-zero exit code of : 2
- Time Step Size and Courant Number
- Mesh Interfaces in ANSYS FLUENT
- Suppress Fluent to open with GUI while performing in journal file
- error: Received signal SIGSEGV
- Using GPU in FLUENT
© 2023 Copyright ANSYS, Inc. All rights reserved.Ansys does not support the usage of unauthorized Ansys software. Please visit www.ansys.com to obtain an official distribution.