Learning Forum

[Nyurons]

I am working on a 2-way FSI analysis that takes a few hours to solve. Knowing that the student version has the 512K cell/node limit, I limit the total number of cells/nodes below the 512K. However, in the midst of System Coupling solving, I get "(DO 0) This is an educational executable, and can only be used with cases containing less than 512000 cells". Although I am not sure of why Fluent exceeded the 512K limit, I think this occurred because I am using the remeshing tool. remeshing may have increased the number of cells/nodes.

I can fix this issue by decreasing the number of cells/nodes, but right now I cannot foretell whether Fluent will exceed the limit in the middle of solving. Whenever Fluent exceeds the 512K limit, I have to go back to Mesh, change the element size, update the mesh, and re-update Setup/System Coupling which takes hours to solve. So, is there a method to limit the number of cells/nodes while Fluent is solving?

[Karthik Remella]

Hi,nThis is an interesting problem. I'd say please try to keep your mesh sizes very similar to what you used to generate your original mesh. That way, you will be restricting (not explicitly but implicitly) the overall size of your mesh. nI hope this helps.nThanks.nKarthikn

[Nyurons]

Thank you for your advice. The problem occurs when I have been keeping my mesh sizes very similar to what I generate in my original mesh. However, I will make sure to keep that in mind. I am wondering if there is a way to restrict the number of elements and nodes explicitly during the solving in Fluent/System Coupling. Thank you, again.nn

[Rob]

I don't think so as it's only an issue with the Student & Teaching variants of the software. Research & Commercial versions don't have a cell count limit (other than how much RAM you have). nHave a look at mesh replacement in the Fluent documentation, that may bypass the issue. n

[Nyurons]

Thank you, Rob. Your answer makes sense because I realized that I would not face this issue if it was not on Student license. I will try replacing or keep the initial element/node number away from the 512K limit. n