Difference between revisions of "GSOC2013Projects"

From Nsnam
Jump to: navigation, search
(Created page with "{{TOC}} <div style="float: left; width: 100%"> * [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2012/faqs GSoC Frequently Asked Questions] * [http://en.flo...")
 
(Project Ideas)
Line 48: Line 48:
 
== Project Ideas ==
 
== Project Ideas ==
  
The following are project ideas which the ns-3 team has identified as important and is most interested in working on as part of the 2012 Google Summer of Code.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. The project ideas ''have not'' been ordered in order of importance or priority.  Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.
+
The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013.  Applicants are however free to propose their own ideas.  In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list] if you have an idea that you'd like to work on.  Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the [http://mailman.isi.edu/mailman/listinfo/ns-developers ns-developers list]. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.
  
 
<blockquote>
 
<blockquote>
Each project idea has been tagged with the following properties:
+
Each project idea within a particular priority has been tagged with the following properties:
 
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
 
* ''Required Experience:'' Languages, concepts, or packages with which applicants must be familiar.
 
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
 
* ''Bonus Experience:'' Other experience or familiarity which would be greatly helpful to applicants for this project.
Line 61: Line 61:
 
</blockquote>
 
</blockquote>
  
 +
= High Priority Projects =
 +
 +
= Medium Priority Projects =
 +
 +
= Low Priority Projects =
  
  
 
[[Category:GSoC]]
 
[[Category:GSoC]]

Revision as of 09:46, 1 March 2013

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

GSoC 2013 Ideas

This webpage highlights project ideas for ns-3's Google Summer of Code 2013 effort.

GSOC 2012 Timeline is:

  • March 18 - 19:00 UTC: Mentoring organizations can begin submitting applications to Google.
  • March 29 - 19:00 UTC: Mentoring organization application deadline.
  • April 8 - 19:00 UTC: List of accepted mentoring organizations published on the Google Summer of Code 2012 site.
  • April 9-21: Would-be student participants discuss application ideas with mentoring organizations.
  • April 22 - 19:00 UTC: Student application period opens.
  • May 3 - 19:00 UTC: Student application deadline.

Full timeline is here: http://www.google-melange.com/gsoc/events/google/gsoc2013

While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its GSOC application before April 8.

About the ns-3 project

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education.

Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.10 in January 2011). ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained. The tool is coming into wide use; our web server logged almost 71000 successful downloads of our released software between January 2010 and January 2011, and we have a users mailing list of about 900 members now averaging 200-300 posts per month.

Our GSoC organizational admin is Lalith Suresh and our backup org admin is Tom Henderson.

Our mentor pool for this year:

Project Ideas

The following are a list of project proposals from the ns-3 team for Google Summer of Code 2013. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to GSoC, anyone is welcome to work on them. Please email the ns-developers list if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the ns-developers list. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.

Each project idea within a particular priority has been tagged with the following properties:

  • Required Experience: Languages, concepts, or packages with which applicants must be familiar.
  • Bonus Experience: Other experience or familiarity which would be greatly helpful to applicants for this project.
  • Interests: Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
  • Difficulty: easy, medium or difficult
  • Recommended reading: pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.

High Priority Projects

Medium Priority Projects

Low Priority Projects