Randall J. LeVeque

Both [geoclaw/src/2d/shallow/flag2refine2.f90](https://github.com/clawpack/geoclaw/blob/master/src/2d/shallow/flag2refine2.f90) and [amrclaw/src/2d/flagregions.f90](https://github.com/clawpack/amrclaw/blob/master/src/2d/flagregions.f90) loop over all cells.

#400 is one step in this direction. It would also be very useful to be able to read in, for example a 1/3 arcsecond DEM covering all of Puget Sound...

I was thinking in the specification of topofiles in setrun.py, we might allow the user to specify more information, including what shift to apply to longitude as it is read...

Do you know how to easily? I guess you can make a `datetime.time` object and then use `time.isoformat()` to get such a string, but to make the object in the...

Yes, I guess we should update the comment, also in amrclaw. So I guess we just throw away the finer level data if restarting with fewer levels. Good to know.

Do I understand correctly that the main differences are - Removing some explicit loops, using `:` notation more, - Reordering the indices in some variables. Mostly local variables private to...

I haven't done extensive tests, but this seems to be slower than the original on my laptop. I tried the `chile2010` problem with the refinement ratios changed to `[4,6]` so...

I added this as a discussion point for the workshop next week. Since it is fairly specialized and the implementation is perhaps not yet finalized I would be inclined to...

I think you might be confusing `mcapa` with `maux`, which is the number of aux arrays (also called `num_aux` in setrun.py). The `mcapa` variable corresponds to `capa_index` in setrun.py and...

So you will probably have to make your own local version of geoclaw_module.f90 that doesn't throw an error and then change the Makefile to point to it. And also to...