On Mar 21, 2013, at 8:02 AM, Sachin Joglekar <[email protected]> wrote:
@Prasoon, I recently did a bit of study and planning about our coordination on vector calculus as far as our GSoC proposals are concerned. I will post my total concept of the module by first week of April (@asmeurer, is this a good enough deadline? considering this project will need lots of inputs from the sympy.physics community) but I want to clear up a few things, to make your work (and mine) easier. Yes. See http://www.google-melange.com/gsoc/events/google/gsoc2013. 1. How do you plan to implement Gauss' theorem (divergence) and Stoke's fundamental theorem of curl? I am not talking about the actual implementation here, I would like to have an idea about the API of the functions/methods that you plan to implement. I know this is a bit early for such questions maybe, but I would appreciate it if you clarify this before I upload my proposal. Just a pointer this one. +1. Figuring out the APIs is more important than figuring out the implementation for these projects. 2. I would also need a look at your API for vector field functions to integrate them with some functions I plan to implement for scalar potential fields. I am not clear about this concept myself (and whether implementing scalar fields is necessary), but having methods to return vector fields from potential field gradients would a good idea. I would like the community's views on this. 3. Do you plan to implement methods for polar and cylindrical coordinates? 4. As your work would primarily deal with functions of the coordinates themselves, we would have to collaborate to integrate time-based fields into your work (maybe an auxiliary PR to your branch from my side, or extension of your classes as a part of my work). This is more of a query to our potential mentors here. What do you people think would be the best course of action in this case? You may have to help one another, especially with bug fixes. Coordinating timelines is a great idea. We can also try to make sure that the mentors are coordinated. One thing: you shouldn't think "send a pull request to the other's branch". All completed work should be submitted for review and merged into master as early and often as possible, so you just sending pull requests fixing what is already in main repo. And another note, if your project does depend on another, you should put a contingency plan in your proposal in case only you are accepted. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy?hl=en. For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
