Hi Barry, ok I understand now.
so taking things through one at a time.
so to clarify, if time step length is 1s and the end time is 1000s then we get 1000 timesteps, that is of simulated time, not real time or clock time. So if we simulated a building for say 100s in real time this would take an age, but the simulated time would be 100 seconds.
Timestep: Specifies the write interval via the actual simulation time steps
Runtime: Specifies the write interval via the computing time
Clock time: Specifies the write interval via the real time, measured on the computing machine
CPU time: Specifies the write interval via the real time, measured by the CPU
Adjustable runtime: Specifies the write interval via the actual simulation time steps
I find most of these to not really be much good in my use cases, I tend to use timestep if steady state, this allows me to say when I want a write in terms of iterations, if transient I tend to use adjustable runtime, this allows me to make a garanteed write at a time regardless of weather im using automated timestepping.
This could be many number of things, but most likely:
- You simulate a more accurate fluid flow due to transient flows (vortex shedding for example)
- the transient flow is not fully developed, there is a certain amount of your simulation that is kind of not relevant at the begining where the flow pattern is still developing.
Hope this helps ![]()
Darren