[macfly]

Hi,

I run a script that creates hundreds of surfaces with the command ic_surface 4pts:

ic_geo_new_family SURFACES
ic_surface 4pts SURFACES surf.0001 {{0.2500 0.3000 0.2500} {0.2500 0.5000 0.2500} {0.2500 0.5000 0.9080} {0.2500 0.3000 0.9080}}
ic_surface 4pts SURFACES surf.0002 {{1.7680 0.3000 0.2500} {1.7680 0.5000 0.2500} {1.7680 0.5000 0.9080} {1.7680 0.3000 0.9080}}
ic_surface 4pts SURFACES surf.0003 {{0.2500 0.5000 0.2500} {0.2500 0.7000 0.2500} {0.2500 0.7000 0.9080} {0.2500 0.5000 0.9080}}
...
...
...

The script runs fast at the beginning but it slows down as the number of surfaces grows. At some point it gets very slow, it can take 1 second to generate a single surface. It's like ICEM is clogging up as more and more surfaces are created. My CPU or memory use doesn't increase, the problem seems to be within ICEM.
Is there a way to 'unclog' ICEM when running a large script file?

[Antanas]

Originally Posted by macfly

Hi,

I run a script that creates hundreds of surfaces with the command ic_surface 4pts:

ic_geo_new_family SURFACES
ic_surface 4pts SURFACES surf.0001 {{0.2500 0.3000 0.2500} {0.2500 0.5000 0.2500} {0.2500 0.5000 0.9080} {0.2500 0.3000 0.9080}}
ic_surface 4pts SURFACES surf.0002 {{1.7680 0.3000 0.2500} {1.7680 0.5000 0.2500} {1.7680 0.5000 0.9080} {1.7680 0.3000 0.9080}}
ic_surface 4pts SURFACES surf.0003 {{0.2500 0.5000 0.2500} {0.2500 0.7000 0.2500} {0.2500 0.7000 0.9080} {0.2500 0.5000 0.9080}}
...
...
...

The script runs fast at the beginning but it slows down as the number of surfaces grows. At some point it gets very slow, it can take 1 second to generate a single surface. It's like ICEM is clogging up as more and more surfaces are created. My CPU or memory use doesn't increase, the problem seems to be within ICEM.
Is there a way to 'unclog' ICEM when running a large script file?

Maybe it's because of drawing?

[Kapi]

Ansys can handle given number of edges and faces at a given time which has improved considerably over the years with every new update.

I would suggest you to break your script in multiple parts and run it.
Also if you are doing like named selection and selecting all the faces you want and in exceeds certain limit then you should re-think that as well and break in into multiple named selection.

You can see when it is selection faces and edges in the bar below, mark after how many faces or edges it is slowing down and you can use that as number.

personally I dont have any trouble handling 4K+ faces at a given time with Ansys 17

[macfly]

Originally Posted by Kapi

I would suggest you to break your script in multiple parts and run it.

You mean break my script into multiple scripts? Load part 1 of the script, run it, then load part 2 of the script, run it, and so on..? I had thought of that but didn't try yet.

[bluebase]

Originally Posted by macfly

You mean break my script into multiple scripts? Load part 1 of the script, run it, then load part 2 of the script, run it, and so on..? I had thought of that but didn't try yet.

Make sure, you don't record the commands when you run a script.



Another option is to run your script in batch mode. Just add a few commands that the script will save the geometry. To run icem in batchmode you have to start it from command line in the following structure "icemcfd -batch -script myscript.tcl". Then you may avoid all the drawing necessary, which might have slowed down your script.

With regards,
Sebastian

[Kapi]

yes Macfly,

thats exactly what I mean.
I break my model in different set of bodies.
Draw them all thru different script via batch file one after other.

give it a go and see how it pans out for ya!