amrclaw
amrclaw copied to clipboard
AMR version of Clawpack
There is also no Burgers' example in `classic/examples`, but there are examples in `$CLAW/apps/fvmbook/chap11/burgers` and `$CLAW/apps/fvmbook/chap12/efix` that could be adapted.
Also updated regression data for 2 examples with minor changes in results. See also - https://github.com/clawpack/geoclaw/pull/562 - https://github.com/clawpack/classic/pull/90
When re-writing all the `valout.f90` files for https://github.com/clawpack/amrclaw/pull/275, I noticed that `output_format == 4` sometimes means `hdf` and other places means `netcdf` although I don't think either works. In particular...
@mjberger: When working on https://github.com/clawpack/amrclaw/pull/275 I noticed that when doing binary output we output ghost cell values along with interior grid values, as we do in GeoClaw. But in the...
The function that currently resides in `sts1.f` looks like ```fortran subroutine initTimers() use amr_module !implicit double precision (a-h,o-z) timeBufnst = 0 timeStepgrid = 0 timeStepgridCPU = 0.d0 timeBound = 0...
Should probably maintain this either in `fort.amr` or as an option via verbosity though.
For discussion, fleshing out an idea we've discussed briefly in the past... See also http://www.clawpack.org/refinement.html ## Current flagging strategy in amrclaw: (ignoring adjoint flagging to start) setrun.py sets values: amrdata.flag_richardson...
This is related to https://github.com/clawpack/clawutil/pull/141
I noticed that in 1d the gauge parameters such as `display_format` and `min_time_increment` are not read in or used, and at some point this should be updated to better match...
I just did an AMRClaw run and noticed some strange timing results for the regridding time. I don't have a lot of insight into what might have happened, other than...