This content has been marked as final. Show 2 replies
I increased the computational domain by 0.1in all the way around and now some of the simulations that claimed that the max temp goal was invalid run just fine. I still have a few that fail with the same message.
The heatsink is fully ducted, so this is an INTERNAL simulation rather than external. I wouldn't think that the computational domain could make a max temp goal invalid.
I have seen that message from time to time also. I have seen it between configurations where the surfaces and their respective goals have not changed, yet in one configuration I get the message and the other I don't. Remeshing on the troubled surface with a slightly finer mesh fixed it. This is probably what changing the comp. domain probably in effect did the same thing - it moved the mesh around on the area causing the problem and luckily ended up in a situation where Floworks liked it....?