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

Added petscviews for KSP and PC, added BCGS test for KSP #40

Merged
merged 1 commit into from
Dec 2, 2015

Conversation

kshyatt
Copy link
Contributor

@kshyatt kshyatt commented Nov 23, 2015

Now the test/ksp.jl file shows how to set the solver type. I also added a viewer routine in the test, both to show that it actually does use bijacobi and so you can see some performance info. Added a petscviewer for PC as well, in case someone wants to inspect that.

@kshyatt
Copy link
Contributor Author

kshyatt commented Dec 2, 2015

Ok, no one had anything to say and this has been open for more than a week, so I'm gonna merge.

kshyatt added a commit that referenced this pull request Dec 2, 2015
Added petscviews for KSP and PC, added BCGS test for KSP
@kshyatt kshyatt merged commit c04fd32 into master Dec 2, 2015
@kshyatt kshyatt deleted the ksh/viewer branch December 2, 2015 19:43
@stevengj
Copy link
Contributor

stevengj commented Dec 4, 2015

Thanks @kshyatt.

I wonder if we can implement writemime(io::IO, ::MIME"image/png", x) for PETSc objects via PetscViewerBinaryOpen or similar, so that we can get graphical PETSc output in an IJulia notebook etc.

@kshyatt
Copy link
Contributor Author

kshyatt commented Dec 4, 2015

I don't see why not? I can also imagine doing fun and silly things with PetscViewerASCIIOpen and UnicodePlots!

One thing that would be quite cool would be to be able to pipe the PETSc monitors to Gadfly or similar plotting libs, or the interactive stuff @timholy has been working on, so we could see pretty perf graphs in real time.

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.

2 participants