- GSoC Frequently Asked Questions
- GSoC Mentor guide
- GSoC student guide
- ns-3's GSoC Student guide
- ns-3's GSoC Mentor guide
- GSoC Student Selection Process
- Patch Requirement Guidelines
- GSoC Student application template
- Get in contact with the ns-3 team: ns-developers mailing list | IRC #ns-3 on freenode.net
ns-3's GSoC 2016
This webpage highlights project ideas for ns-3's Google Summer of Code 2016 effort.
The thirteen week coding period for projects runs from 25 May to 21 August, 2015. The full project timeline is here: https://developers.google.com/open-source/gsoc/timeline?hl=en
ns-3 must apply for GSoC and will learn whether it has been accepted on 29 February 2016.
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.
Mentors will be paired with students based on the projects that are selected. Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring. Prospective mentors should notify Tom Henderson or Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.
ns-3 and other GSoC mentoring organisations
Students interested in ns-3 and GSoC are also encouraged to explore whether other organizations might be a suitable mentoring organization for their project idea. Please keep in mind, though, that the ns-3 project is not involved in the selection process for these other mentoring organizations, and you will have to apply there instead.
Students: how to participate
For students interested in applying to ns-3 for GSOC, first wait to see if ns-3 will be selected. If so, then go through the following list to get started:
- Read the official GSoC student guide.
- Read ns-3's GSoC Student guide.
- Look through our #Project Ideas below to see if you find a project that interests you.
- Review the tutorial thoroughly, if you have not already done so.
- Look through the GSoC Student application template to start preparing your proposal.
- Next, proceed to get in touch with the developers on the mailing list and refine your proposal.
- In parallel, make sure you prepare a patch as per the Patch Requirement Guidelines. Your application to ns-3 will not be considered if you do not fulfill this requirement.
Below is a list of #Project Ideas proposed by the ns-3 team for Google Summer of Code 2016. 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 a different idea that you'd like to work on, to see if a mentor may be interested. 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 stronger the 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.
Mentors: how to participate
The ns-3 project is open to the proposal of new project ideas by developers interested in being a GSoC mentor. For mentors who're adding project ideas to the list below, please ensure that:
- The projects are sized such that there can be a code merge by the end of the coding period. The scope of the project should be such that it is very difficult to not have a code merge by the end of the summer.
- The proposed projects are not too open-ended. That is, if the deliverables or a clear path to the same are not well understood, it is better kept outside GSOC.
- There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply to these repositories, or because they apply to an ns-3 module that is in the process of being merged with ns-3-dev.
Note to students: These ideas are not listed in any priority order.
ICCRG TCP Evaluation Suite port
Mentors: Tom Henderson
The Internet Congestion Control (ICC) research group has worked on an ns-2-based TCP evaluation suite for several years. Details about this suite are described in this internet draft:
and code is provided here:
We would like to find a student interested in porting this evaluation framework from ns-2 to ns-3. Are you interested in this project? In your application, please tell us how you plan to organize your project. It may be too big of a job to complete the entire port; how would you design a project to make sure that at least a portion of the framework is ported by the end of the summer? Another part of the application that will be evaluated is how well the applicant has reviewed the ns-2 code and compared it to ns-3. Where are the differences between ns-2 and ns-3 that make such a port difficult? What pieces might be relatively easy to port? How would you check whether the results from the ns-3 port compare well with the ns-2 code?
- Required Experience: C++
- Bonus Experience: Transport protocols or TCP, ns-2
- Interests: TCP and transport protocol performance
- Difficulty: depends on what functionality the student proposes to implement
ns-3 bug squashing and testing
Mentors: Tommaso Pecorella
The ns-3 project is affected by a number of bugs, like any software suite. All the known bugs are classified and tracked in Bugzilla, divided by severity and module.
Over the time some of these bugs have been left without fixes, some have fixes but they are untested, etc. Moreover, in order to kill a bug for good (and not open another bug while fixing the old one), it is necessary to have tests. Tests also prevent the bug from returning at a later time.
The goal of the project is to:
- Scan Bugzilla and check what bugs are to prioritize (i.e., fix the priorities).
- Fix the bugs (eventually involving the module maintainers).
- Provide unit testing for the fixed bugs.
- Improve the modules documentation.
The candidate is free to propose the methodology he/she wants to pursue (i.e., fix bugs by module, by importance, etc.).
- Required Experience: C++
- Bonus Experience: Bugzilla, bug fixing, unit testing systems.
- Interests: software maintenance.
- Difficulty: depends on what bugs and unit testing the student proposes to fix/implement