Sorry for being slow to the party. Took me a while to get through these threads.
Ken and Utkarsh are completely correct. Users do NOT want ParaView time to generally match real world time. In fact, in 14 years of working with users, I believe I have seen them request this once or twice.
Here is a very typical use case for CTH. CTH is a shock physics code. A bullet will be fired into a cement wall. The bullet is moving at kilometers per second. The simulation starts putting out data when the bullet is 1 cm from the wall. In 0.1 mm increments, move the bullet towards the wall internally in CTH, BUT write out data every 1mm (every 10th timestep). When the bullet first touches the cement wall, start dumping all timesteps for the next 100 timesteps. Then, go back to dumping every 10th timestep for the next 1000 timesteps. Users want to see how the cement fractures, and becomes fragments. Then, they want to measure the mass, velocity and energy of the fragments. Users don’t want to see this in realtime, they don’t want to guess seconds into the run, and they don’t want to have to calculate units change every time they run ParaView. They don’t want to mess with a GUI. They just want to see their data - every single frame that they wrote to disk. Almost always.
Ken and Utkarsh are correct.