You should also start writing up your application, so you can get some feedback on it. Something to think about: you have a lot of ideas and you may not be able to get to all of them over the summer. This is fine, but you should think about prioritizing them so that you do the most important things first, and put the less important things to the end of the summer for if you have time. Consider not only the relative importance of each idea, but also which things will depend on one another (e.g., will you need to fix up the structure of the new plotting module before implementing this algorithm, or can they be done independently?).
Aaron Meurer On Tue, Mar 27, 2012 at 3:12 PM, [email protected] <[email protected]> wrote: > @Bharath, as the ideas for your project are becoming much more > interesting than just adding a backend / plot type, I was wondering > what are you thinking about the structure of the module. Do you think > that you will need to restructure the module for example? How will the > interval arithmetics couple to lambdify? > > Moreover, concerning lambdify, do you think that you will have to work > on it? I am asking as there is an extensive todo list for that piece > of code that can make your work unnecessary hard. Especially if > lambdify and the interval arithmetics are not well separated. > > Finally, have you fulfilled your patch requirement? If you need any > help with this, just ping us. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
