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

Make PyWENO kernels work with Fortran SharpClaw code #48

Closed
ketch opened this issue Jul 26, 2011 · 9 comments
Closed

Make PyWENO kernels work with Fortran SharpClaw code #48

ketch opened this issue Jul 26, 2011 · 9 comments
Assignees

Comments

@ketch
Copy link
Member

ketch commented Jul 26, 2011

No description provided.

@ghost ghost assigned ketch Jul 26, 2011
@memmett
Copy link
Contributor

memmett commented Aug 2, 2011

Happy to help with this one... is there a test case for this?

@ketch
Copy link
Member Author

ketch commented Aug 15, 2011

Hi Matt,

Sorry for the slow reply; I was on vacation when you chimed in. There are
several test cases for sharpclaw, so the first thing would be to get a
PyWENO-generated fifth-order kernel working and make sure the tests pass.
Then it should be easy to add other orders. Here's what I think needs to
be done:

  1. Put the PyWENO-generated code into a new fortran module that does what
    reconstruct.py does (i.e., takes q and computes ql, qr -- see also
    reconstruct.f90 in pyclaw/src/fortran/1d/sharpclaw).
  2. Modify flux1.f90 (in the same directory) to use the new module instead of
    the old one.

I think we'd want to change the code significantly from what PyWENO
generates in order to make it more efficient (or better yet, we should add
PyWENO routines that generate more efficient, though probably less readable
code as an option). But I think the first thing to do is just get it
working.

-David

On Tue, Aug 2, 2011 at 4:38 AM, memmett <
reply@reply.github.com>wrote:

Happy to help with this one... is there a test case for this?

Reply to this email directly or view it on GitHub:
#48 (comment)

@memmett
Copy link
Contributor

memmett commented Aug 15, 2011

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

@memmett
Copy link
Contributor

memmett commented Aug 15, 2011

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

@ketch
Copy link
Member Author

ketch commented Aug 15, 2011

That sounds good. Let's not worry about the other reconstructions (wave,
characteristic, etc.) for now. I want to do them eventually, but we don't
need them for the paper.

-David

On Mon, Aug 15, 2011 at 8:51 PM, memmett <
reply@reply.github.com>wrote:

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

Reply to this email directly or view it on GitHub:
#48 (comment)

@ghost ghost assigned memmett Aug 17, 2011
@memmett
Copy link
Contributor

memmett commented Aug 19, 2011

Do you have a preference for how to select the WENO order? How about a 'weno_order' attribute of SharpClawSolver that defaults to 5?

@memmett memmett closed this as completed Aug 19, 2011
@memmett memmett reopened this Aug 19, 2011
@ketch
Copy link
Member Author

ketch commented Aug 19, 2011

That sounds good to me.

David Ketcheson

Sent from my iphone

On Aug 19, 2011, at 6:07 PM, memmettreply@reply.github.com wrote:

Do you have a preference for how to select the WENO order? How about a 'weno_order' attribute of SharpClawSolver that defaults to 5?

Reply to this email directly or view it on GitHub:
#48 (comment)

@memmett
Copy link
Contributor

memmett commented Aug 25, 2011

Pull request submitted... will close this issue when the request gets merged.

@ketch
Copy link
Member Author

ketch commented Aug 28, 2011

Complete as of cd5daf3.

@ketch ketch closed this as completed Aug 28, 2011
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