-
Notifications
You must be signed in to change notification settings - Fork 46
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
Adding new limiters? #239
Comments
What brought this up? Do you want to add a new limiter yourself or know somebody who does? How interesting.
— Marsha
… On Apr 4, 2019, at 5:40 AM, Donna Calhoun ***@***.***> wrote:
Are there any thoughts about how to best add a new limiter? I am thinking of a case in which the user adds a new limiter to inline limiter.f90. There doesn't seem to be any way to indicate to the Python routines that they should accept a new limiter number. One idea is to allow a 'user' option + a number, i.e. The number would then indicate the goto location in the limiter file (or at least an offset from limiters known to Clawpack). The user is responsible for making sure this limiter gets called correctly (since they are supplying new limiter file).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#239>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA1DC7wxt0bMriwDfJo63P_CT6sMotYqks5vdciagaJpZM4ccXCr>.
|
If you want to just test a limiter you could use PyClaw which has a number of additional limiters and would be trivial to add a new one. Otherwise in |
Yes, I'd like to try out a new limiter. I am comparing results with Basilisk, and they use the generalized minmod limiter. I am not necessarily proposing to add it to Clawpack, though, and so haven't opted to edit |
It would be pretty easy to add. One thing we did do in PyClaw was add another argument for the courant number as some of the more exotic limiters out there required the courant number. You can see the list if you are interested in https://github.com/clawpack/pyclaw/blob/master/src/pyclaw/limiters/tvd.py. |
Are there any thoughts about how to best add a new limiter? I am thinking of a case in which the user adds a new limiter to
inline limiter.f90
. There doesn't seem to be any way to indicate to the Python routines that they should accept a new limiter number. One idea is to allow a'user'
option + a number, i.e. The number would then indicate the goto location in the limiter file (or at least an offset from limiters known to Clawpack). The user is responsible for making sure this limiter gets called correctly (since they are supplying new limiter file).The text was updated successfully, but these errors were encountered: