https://www.nsnam.org/mediawiki/index.php?title=GUI_Development&feed=atom&action=historyGUI Development - Revision history2024-03-29T07:18:28ZRevision history for this page on the wikiMediaWiki 1.24.1https://www.nsnam.org/mediawiki/index.php?title=GUI_Development&diff=1538&oldid=prevMathieu.lacage at 17:46, 31 March 20082008-03-31T17:46:54Z<p></p>
<p><b>New page</b></p><div>The long term goal of this project is to build a tool which can be used to help researchers and students perform all the tasks in a network simulation workflow:<br />
* layout the network topology: describe the network nodes and their physical-layer connectivity<br />
* add capabilities to nodes: <br />
** mobility models which describe node movements over time.<br />
** ipv4/udp/tcp stack<br />
** MAC bridging stack<br />
** traffic generation and reception applications<br />
** routing daemons<br />
* configure each object in the system to setup its attributes to various values (set PHY tx level of node 4, etc.)<br />
* setup trace events you want to log<br />
* run simulation<br />
* analyse trace logs:<br />
** simple text-based analysis of packet traces<br />
** simple pcap-based analysis of packet traces<br />
** simple graphical analysis: ability to compute averages, distributions of observed variables, etc.<br />
<br />
Some tools already exist which attempt to handle some or all of the above steps for some other network simulators:<br />
* omnet++ has an eclipse-based gui<br />
* opnet is a commercial tool with a free-for-research version which has a strong gui<br />
<br />
Since building such a large tool is really a long-term project, the student should focus on identifying parts of the above workflow for which he wants to provide a gui. Special care should be put to:<br />
* figure out how the student's gui will fit in the long-term gui. i.e., ideally, the student would be able to describe what the long-term gui should look like and show how his component will fit in later.<br />
* figure out how the student's gui will fit in today's workflow.</div>Mathieu.lacage