pyclaw icon indicating copy to clipboard operation
pyclaw copied to clipboard

Gauge exactly at boundary produces no output

Open ketch opened this issue 8 years ago • 3 comments

In at least one example I've seen, placing a gauge exactly at a domain boundary leads to PyClaw silently producing no output for that gauge.

ketch avatar Jun 07 '17 06:06 ketch

We could switch to the same logic in AMRClaw and GeoClaw for gauges which circumvents this problem.

mandli avatar Jun 07 '17 13:06 mandli

@mandli Thanks for the suggestion. In those codes, do you do some kind of interpolation to obtain pointwise gauge values, or do you just use the nearest cell center?

Where is the logic you're referring to, in the code?

ketch avatar Jun 08 '17 03:06 ketch

The primary logic starts at

https://github.com/clawpack/amrclaw/blob/master/src/2d/gauges_module.f90#L398

and uses bilinear interpolation. There is a bit of complexity due to AMR that we would not need to worry about.

mandli avatar Jun 08 '17 17:06 mandli