adjustableRunTime breaks apps
 

I've been working on updating a custom solver from 1.4.1 to 1.5 and then 1.6 (another post discusses one issue I have). I was running a new benchmark case and decided to play with adjustableRunTime for writeControl to get nicely spaced time directories.

Its not so much that the change breaks my solver, but the answers I are very different from my previous benchmark. There is nothing different from this new benchmark case and my previous one in the setup save for writeControl being runTime or adjustableRunTime. This also happened when I ran engineCompRatio, with the adjustableRunTime in writeControl version giving me the wrong value.

Has anyone else seen this? Is this peculiar to 1.4.1?

Hi

I'm running this at the moment with turbDyMFoam on 1.5-dev. There's a slight variation in the forces output but nothing that I can't attribute to turbulence. :(