Derek Gaston
Derek Gaston
It is restartable on purpose - you can use `reset_dt` in the `Executioner` block to override this behavior. I have been over and over all of the scenarios. The defaults...
When you are restarting you may need to continue the timestep size from before - particularly if you're using high order time integration there needs to be continuity. We always...
All restartable data is recoverable. Restartable is a subset of recoverable.
If you have a TimeStepper that is using time_step to set the dt... then it doesn't care about reset_dt. What reset_dt is there for is for _adaptive_ timestepping algorithms. For...
This is not an error - this is the correct behavior. When not doing picard you can set `output_sub_cycles = true` to tell a sub-app to write out its intermediate...
working on this in relation to #10914
Also do `ScalarKernels` ( #10922 ) and `VectorKernels`
I'm interested in what you're thinking here. Make sure you think about how this will be presented downstream to visualization tools as well. I don't really see the need for...
The offsetting by 1000 is something we did in the mesh generator (for the fuel rod mesh generator) not something MOOSE did... and we did it for this reason: to...
I think in the case of restart you just wouldn't do the check. Presumably the check was done on the initial startup so the mesh as it's written out in...