GSoC 2016: Improve the plotting module

[Ryan McCampbell]

Hello, I am Ryan McCampbell, a Computer Science student at the University of Virginia.

I am interested in working on improving the sympy plotting library, as mentioned at https://github.com/sympy/sympy/wiki/GSoC-2016-Ideas#improve-the-plotting-module. I am not sure if I can do some of the hard tasks, but I have experience with matplotlib and think I could implement many or at least some of the suggested features. How many of these do you think would be reasonable for a project? And is there any additional information I should know?

[Ryan McCampbell]

On Tuesday, March 22, 2016 at 9:07:44 PM UTC-4, Ryan McCampbell wrote:

Hello, I am Ryan McCampbell, a Computer Science student at the University of Virginia.

I am interested in working on improving the sympy plotting library, as mentioned at https://github.com/sympy/sympy/wiki/GSoC-2016-Ideas#improve-the-plotting-module. I am not sure if I can do some of the hard tasks, but I have experience with matplotlib and think I could implement many or at least some of the suggested features. How many of these do you think would be reasonable for a project? And is there any additional information I should know?

Also I was thinking that the plotting functions could be more embeddable/customizable. Currently the "plot" function picks a backend (falling back on the "TextBackend" if matplotlib is not installed) and creates a window automatically. You can postpone it and modify the figure by setting show=False, but it is a little awkward. I would rather the user be able to pass in a preexisting mpl figure or axes object to plot on, and to select between multiple backends. That way you could for instance embed it in a GUI. 

[Aaron Meurer]

I agree that the interaction with matplotlib plots could be better.
You can search the issue tracker and stackoverflow to see some
examples of things that users commonly request.

Remember that the deadline is Friday, both for the application and the
patch requirement.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+un...@googlegroups.com.
> To post to this group, send email to sy...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/d70d8cd6-bea0-4c6d-92b9-6fb7c157018b%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Ryan McCampbell]

What exactly is the patch requirement? It just says "you must submit at least one patch to sympy"... is this supposed to be a sample related to the project or just code to demonstrate your ability?

[James Milam]

I believe it is just code to demonstrate your work process, however, if you can relate it to your project you'll have a better understanding of the relevant code that you will need to talk about in your proposal. 

[Aaron Meurer]

Yep, that is correct.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+un...@googlegroups.com.
> To post to this group, send email to sy...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/sympy/3312ae00-4207-4fd6-92a6-6283e7f964d8%40googlegroups.com.