-
Notifications
You must be signed in to change notification settings - Fork 99
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
Make PyWENO kernels work with Fortran SharpClaw code #48
Comments
Happy to help with this one... is there a test case for this? |
Hi Matt, Sorry for the slow reply; I was on vacation when you chimed in. There are
I think we'd want to change the code significantly from what PyWENO -David On Tue, Aug 2, 2011 at 4:38 AM, memmett <
|
Alrighty, I'll get right on it. Regarding making it more efficient: PyWENO allows some flexibility in combining several steps (smoothness, weights, reconstruction) into one function call. By combining everything into one function, there might be some redundant computation, but much less data movement. After I get things working I'll try this out. Matt |
Hi David, I'm going to start with the weno5 routine in flux1.f90. Can the other weno5_* routines be re-written to call the plain weno5 routine? Matt |
That sounds good. Let's not worry about the other reconstructions (wave, -David On Mon, Aug 15, 2011 at 8:51 PM, memmett <
|
Do you have a preference for how to select the WENO order? How about a 'weno_order' attribute of SharpClawSolver that defaults to 5? |
That sounds good to me. David Ketcheson Sent from my iphone On Aug 19, 2011, at 6:07 PM, memmettreply@reply.github.com wrote:
|
Pull request submitted... will close this issue when the request gets merged. |
Complete as of cd5daf3. |
No description provided.
The text was updated successfully, but these errors were encountered: