IdeasUNVToFoam - big meshes
 

Hi everyone!

I have created a big mesh of about 70 million cells for a heat exchanger, model visible here:https://cad.onshape.com/documents/03...a1b4f5594c73d6


I created the model in Onshape, imported it and meshed it in Salome, downloaded it as a UNV file and am using IdeasUNVToFoam conversion to be able to simulate it in OpenFOAM. The ideasUNVToFoam script has been running for 3 days now and it's not advancing anymore. On smaller models (~1 Million cells) the script has worked perfectly, and the step that I'm currently stuck at is usually the longest step in those other, successful conversions.

I was wondering:
1) Is there any way to make ideasUNVToFoam run in parallel?
2) Are there any inherent limitations in ideasUNVToFoam that I should be aware of, size wise for the model?
3) Are there any flags I could set while running ideasUNVToFoam to make it only do the absolute necessary steps to convert my mesh to a .foam format?



Thank you and I wish you a great weekend!

/Malcolm Akner

Even with 900 million cells there is no way that it should take anywhere near that long. There is either a programming error in the convertor or bad syntax in input file. Either way, it's getting stuck somewhere.

Thank you for your reply olesen.

So what can I do? I need this model in .foam format, what would be the best way of achieving that?

Thank you for your reply olesen.

So what can I do? I need this model in .foam format, what would be the best way of achieving that?

The first thing I normally do is old-school debugging. In your case that would mean adding some progress statements to the convertor. Eg, printing out every 10.000 or even 100.000 points being read and converted. Same thing for the cells being read and converted. Sure, may produce lots of output but also will give you an idea how far it gets before stalling.
After that you can start seeing which part of the code let OKs suspicious or perhaps even check that your file content looks reasonable at that location.
Beyond that, you'll just have to see where it leads you. Much like programming, it is a bit of craftsmanship to debugging as well.