Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Force new dt after regrid #356

Closed
maxpkatz opened this issue Jul 5, 2018 · 1 comment
Closed

Force new dt after regrid #356

maxpkatz opened this issue Jul 5, 2018 · 1 comment

Comments

@maxpkatz
Copy link
Member

maxpkatz commented Jul 5, 2018

Amr has a parameter compute_new_dt_on_regrid which is disabled by default. But we want this option to be on for most of the problems that are of interest to Castro, which can evolve rapidly and for which updating the timestep after generating new regrid data is probably wise. So we should force this option to be on by default in Castro, assuming that we can find a way to still allow the user to disable it if they really want to.
@zingale
Copy link
Member

zingale commented Sep 26, 2019

we should just turn this on by default.

This was referenced Dec 29, 2019
Open
Merged
@zingale zingale closed this as completed in 45282cf Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zingale @maxpkatz