Difference between revisions of "GSoC2018: A Simulation Execution Manager for ns-3"

From Nsnam
Jump to: navigation, search
m (Add link to proposal PDF)
(Add Week 1 summary)
Line 18: Line 18:
  
 
= Project Timeline =
 
= Project Timeline =
 +
== Week 1 (May 14 - May 19) ==
 +
 +
Week 1 was used to set up the project and define the structure of the code that will be necessary to get to Milestone 1.
 +
For now, code is maintained in src/stats/utils.
 +
 +
'''Summary''':
 +
* Created a basic Python project using pipenv;
 +
* Defined an initial set of classes and functions to outline code structure (code available in the [https://github.com/DvdMgr/ns-3-dev-gsoc/tree/feature/api-specs/src/stats/utils/sem sem] folder);
 +
* A detailed report can be found in the [https://github.com/DvdMgr/ns-3-dev-gsoc/blob/feature/api-specs/src/stats/utils/dev.org dev.txt] file in the project repository.

Revision as of 03:33, 19 May 2018

Return to GSoC 2018 Accepted Projects page.

Project overview

  • Project name: A Simulation Execution Manager for ns-3
  • Abstract: This GSoC project will develop a Python library to automatize the ns-3 simulation script execution and result management processes.
  • About me: I am a first-year PhD student at the University of Padova, Italy, working under the supervision of Prof. Michele Zorzi. My research interests include large scale IoT network simulation and medium access layer protocol design.

Project Timeline

Week 1 (May 14 - May 19)

Week 1 was used to set up the project and define the structure of the code that will be necessary to get to Milestone 1. For now, code is maintained in src/stats/utils.

Summary:

  • Created a basic Python project using pipenv;
  • Defined an initial set of classes and functions to outline code structure (code available in the sem folder);
  • A detailed report can be found in the dev.txt file in the project repository.