Every time I try to run my simulation I get the following error message:
The job execution was aborted. A possible cause is that not enough memory was available. In this case, selecting a larger instance or using a coarser mesh should resolve the issue.
My mesh is already relatively coarse for a CFD/HT simulation and I’m not too sure what it means by instances…
alright - so I just had a quick look, but what I can definitely say is that the operations log message is miss-leading (already known - an improved error reporting for this is underway). The problem is not that the machine is running out of memory - in fact, your core count is not efficient. With 400k cells, an 8 core machine is more than enough.
The problem seems to be numerical instability. I didn’t find anything obvious in the solver log message. So the most obvious question would be: 10m/s inlet with a 5cm geometry - quite some speed, is that intended? The next question would be how you came up with the values for k and omega? Did you use some correlation / hand calculation? That could be one reason for the instability and the next place to look would be the numerical schemes.
@gholami has got more experience with CHT. Babak, anything obvious to you?
As for the speed, I was trying to make it a pretty turbulent flow, I calculated that with 10 m/s the flow has a Re number of 7768 for that geometry.
With regards to the k and omega values I just based them of previous turbulent flow simulations, hence I’m sure they’re way off… haha
Same with the numerical schemes.
Yeah, I worked on it a bit more and realised that I had mistakenly put in one of the parameters wrong. After I corrected it I got results.
Looking at the results, they do make sense, hence they are what I expected.