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

Add new gauges #541

Merged
merged 4 commits into from
Jun 4, 2016
Merged

Add new gauges #541

merged 4 commits into from
Jun 4, 2016

Conversation

mandli
Copy link
Member

@mandli mandli commented Jun 4, 2016

Add a new gauge solution class used by other clawpack repositories. See clawpack/clawpack#91 for the overarching commit.

@coveralls
Copy link

coveralls commented Jun 4, 2016

Coverage Status

Coverage remained the same at 69.685% when pulling eeeb619 on mandli:add-new-gauges into 40e1f82 on clawpack:master.

@mandli
Copy link
Member Author

mandli commented Jun 4, 2016

This PR is really meant to just stick the new gauge class into PyClaw since that's where it's going to end up anyway. I did take a look at what a preliminary implementation of replacing the current gauges in PyClaw would look like but it is a bit more complex than I had originally though about. Can we merge this PR and open an issue to incorporate these gauges into PyClaw for the time being?

@rjleveque
Copy link
Member

OK with me to merge, but perhaps @ketch disagrees?

We need this to merge in a bunch of other changes in amrclaw and geoclaw.

@rjleveque rjleveque merged commit 314fd93 into clawpack:master Jun 4, 2016
@ketch ketch removed the in progress label Jun 4, 2016
@ketch
Copy link
Member

ketch commented Jun 6, 2016

I'm fine with merging this in the interest of moving forward, especially since I don't expect to have time to make the changes in PyClaw soon.

@mandli
Copy link
Member Author

mandli commented Jun 6, 2016

I will make the issue.

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

Successfully merging this pull request may close these issues.

None yet

4 participants