{"id":291292,"date":"2023-07-03T13:43:42","date_gmt":"2023-07-03T13:43:42","guid":{"rendered":"\/forum\/forums\/reply\/291292\/"},"modified":"2023-07-03T13:43:42","modified_gmt":"2023-07-03T13:43:42","slug":"291292","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/291292\/","title":{"rendered":"Reply To: Different boundary condition gives weird result"},"content":{"rendered":"

<p>The monitor isn’t a residual. It’s a report from Fluent of a value at every iteration\/time step. When it’s level it’s a good sign that the model isn’t changing at that location. However, as you’re monitoring an average you may be masking localised changes in value. <\/p><p>Residuals are the solver reports and are a function of how much the overall solution is changing. <\/p><p>Convergence is typically OK when monitors stop changing, residuals drop by the required number of orders of magnitude and fluxes balance. For a transient run the extra requirement is that previous time steps have converged otherwise you risk a model that’s wrong but returning to “correct” over time, so at some point it will be OK. If you check the AIS courses (Learning on here) there will be something covering this in the Fluids\/CFD modules. <\/p><\/p>\n","protected":false},"template":"","class_list":["post-291292","reply","type-reply","status-publish","hentry"],"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