Hello -- Thanks for your post, and thanks for you enthusiasm!
It's too bad you just found us now; the GSoC application deadline for students is Monday April 7, 5:00 PM PDT. That does give you enough time to put an application together, but you must hurry. > More specifically, I am most interested in developing behavioral modeling > functions for Gnucap. I have a strong background in mathematics and firm > foundation in C++ programming, and I am confident that with some research > and mentoring I would be able to effectively integrate these functions into > a library for use in the gEDA package. I have a basic understanding of the > noise functions, and mathematically speaking I have a good understanding of > Laplace transforms which I see are in need of being developed for Gnucap. > > These functions are something that I could provide as individual > deliverables throughout the summer, which I feel is best for allowing > evaluation, revision, and improvements as needed. I am excited to begin my > involvement with gEDA, and I am open to any suggestions, comments, or > questions that you may have. Also, what would you recommend for any > necessary background, such as publications/information regarding the > functions (noise, transition, slew), and/or their implementation in gEDA? Al Davis -- the main developer of Gnucap -- can speak in more detail about background material you want to explore. I'll note that he has posted his thesis (describing the foundations of Gnucap) and a Gnucap programming doc on the main Gnucap website: http://gnucap.org/papers/ I am not sure how up to date these materials may be. Gnucap has been a moving target for the last year or so. As for writing an application, I recommend the following to anybody writing a GSoC application: * Write up a couple of use cases describing how your proposed feature will work in the context of the larger program. In your case, describe in a detailed, step by step manner how the user will use the behavioral models, what they will do, how he will call them, what is their output, etc. * Be as specific as possible about how your code will work, and where it will plug into the existing app. It will be good if you can say something like "I will modify foo.cc to incorporate a new datastructure which is a struct of function pointers to the various behaviors I want to implement, and then I will create them in a file bar.cc.... Each function will take as arg a pointer to the circuit matrix....." This is good for two reasons: 1. We can see that you understand the existing code (at least to some level), and 2. We can better judge your proposed changes. * Please make a resume available somewhere for us to see. Many people keep their resume on their own web site, but if you don't have that, then you can just post something into the GSoC application form. Please provide some info about what year you are at in the university, which classes you have taken (which are relevant to electronics and software), any side projects or work which is relevant to your proposal, etc. Good luck with your application! Stuart gEDA GSoC admin _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
