Add proxybylevel option to chunkerflam and chunkerkerneval #112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces a
proxybylevel
boolean option tochunkerflam
andchunkerkerneval
which, if true, adaptively computes the number of necessary proxy points separately at each level during relevant FLAM routines. This is needed for moderate to high frequency oscillatory problems (see #85), since the number of points needed to resolve oscillations in the kernel is smaller for smaller boxes.I've tested this for Helmholtz (see the$O(k)$ factor.
devtools/test/flamproxybylevelTest.m
script), and it speeds up the FLAMrskelf
andrskel
routines on domains which are tens to a few hundred wavelengths by an approximatelyThis does require minor modifications to FLAM itself. I've forked FLAM under the fastalgorithms org and pushed my changes to https://github.com/fastalgorithms/FLAM. I'm not a submodule expert, so please let me know the best way to point the
chunkie/FLAM
submodule to this fork.