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.

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

Gauge exactly at boundary produces no output #577

Open
ketch opened this issue Jun 7, 2017 · 3 comments
Open

Gauge exactly at boundary produces no output #577

ketch opened this issue Jun 7, 2017 · 3 comments

Comments

@ketch
Copy link
Member

ketch commented Jun 7, 2017

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.

@mandli
Copy link
Member

mandli commented Jun 7, 2017

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

@ketch
Copy link
Member Author

ketch commented Jun 8, 2017

@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?

@mandli
Copy link
Member

mandli commented Jun 8, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants