time/iteration

- April 19, 2020 at 7:24 am
  
  bobd
  Subscriber
  
  Hi,
  
  i'm running a simulation where after a while I got an time/iteration of more than 1 hour. does anyone now what the reason could be?
  I'm running only single precision. I tried to run parallel, but then my dynamic mesh doesn't work anymore.
- April 20, 2020 at 6:21 am
  
  DrAmine
  Ansys Employee
  
  Do run double precision. The message it too small but it seems you are executing a macro which transforms an interior to wall and back I guess. Probably here an issue is occurring. Are you using dynamic mesh events? Can you try that without any events:, just try changing boundaries back and forth for testing.
- April 20, 2020 at 7:16 am
  
  bobd
  Subscriber
  
  If u run double precision I have the same problems.
  
  I change my two pressure outlets to walls, but even if i don't do this I have the same problem.
  
  Yes i'm using a dynamic mesh, where the inner horizontal line, goes deeper until a certain end point.
- April 20, 2020 at 9:40 am
  
  DrAmine
  Ansys Employee
  
  Can you figure out why the macro it is executed? Is it your macro?
  
  Regarding double precision: You need always to run in double precision.
- April 20, 2020 at 9:42 am
  
  bobd
  Subscriber
  
  yes, the macro is to switch the boundarys to walls. I wrote this myself.
- April 20, 2020 at 9:45 am
  
  DrAmine
  Ansys Employee
  
  Does it work without your macro? What does the macro do?
- April 20, 2020 at 9:47 am
  
  bobd
  Subscriber
  
  Yes it works without the macro but I keep having the time/iteration probems.
  
  Here is my macro code:
  
  (cond
  
  ((> (rpgetvar 'time-step) 930)
  
  (ti-menu-load-string "define/boundary-conditions/zone-type 6 wall")
  
  (ti-menu-load-string "define/boundary-conditions/zone-type 7 wall")
  
  )
  
  )
- April 20, 2020 at 5:14 pm
  
  DrAmine
  Ansys Employee
  
  I do not understand the problem with iteration? More details?
- April 20, 2020 at 7:06 pm
  
  bobd
  Subscriber
  
  Well that in the beginning of my simulation the time/iter ationequals about 0:00:05. but now it is equal the numbers down here which is really long if this is only one iteration and i have 150 iteration per time step.
  
  So, the simulations goes really slow
- April 21, 2020 at 5:33 am
  
  DrAmine
  Ansys Employee
  
  You can ignore that: do not focus on that number. Better is to benchmark your case and run say 100 time steps and then check the timer usage. Disable all I/O and run it in batch for accurate performance tracking.
- April 21, 2020 at 5:34 am
  
  DrAmine
  Ansys Employee
  
  And 150 iterations per time steps is insane and not required: better to lower the time step size instead.