{"id":164920,"date":"2023-03-17T08:58:59","date_gmt":"2023-03-17T08:58:59","guid":{"rendered":"\/knowledge\/forums\/topic\/why-am-i-getting-divergence-on-the-first-iteration-for-an-axisymmetric-problem\/"},"modified":"2023-07-31T12:26:32","modified_gmt":"2023-07-31T12:26:32","slug":"why-am-i-getting-divergence-on-the-first-iteration-for-an-axisymmetric-problem","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/why-am-i-getting-divergence-on-the-first-iteration-for-an-axisymmetric-problem\/","title":{"rendered":"Why am I getting divergence on the first iteration for an axisymmetric problem?"},"content":{"rendered":"

This can be caused by one of two problems with the geometry. (1) Part of the mesh lies below the axis boundary. Do a Mesh->Check to make sure it does not report something like this: Checking for nodes that lie below the x-axis. WARNING: Invalid axisymmetric mesh: 6 nodes lie below the x-axis. and WARNING: Mesh check failed. For axisymmetric problems in Fluent, it is a requirement that the axial direction must always be along the x-axis and the radial direction is in the positive y-direction. If the y-coordinate for any of the nodes in the mesh is negative, even if it is only a very small negative value like -1e-32 m, the solution will fail. To fix this: Use Mesh->Translate and move the geometry so ymin is positive. You can use Mesh > Scale to determine the minimum y-coordinate and thus how far it needs to be moved (2) Part of the axis boundary has been accidentally defined as a wall This can sometimes happen in the preprocessor if the axis consists of a large number of edges and one or more edges are accidentally not included when the named selection is created. Models which have one or more very short edges on the axis are susceptible to this because it may be very hard to see whether or not they have been selected in the graphics window. If the mesh check does not identify any nodes below the x-axis, this is reason for the divergence. The most common way to correct the problem is to use the grid display to display each wall, one at a time, to locate the ones that are on the axis. The boundary conditions type can then be changed from wall to axis in Fluent<\/p>\n","protected":false},"template":"","class_list":["post-164920","topic","type-topic","status-publish","hentry","topic-tag-4457","topic-tag-fluent","topic-tag-fluid-dynamics","topic-tag-general"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t