Highly motivated, versatile, enthusiastic and hard-working person with a genuine eagerness to learn and achieve excellence. Used to work in a competitive and innovation environment developing cutting-edge applications. Loves challenges and to discuss ideas with the team or colleagues to achieve the best solution. Has flair of leaning new tools, new technologies and expanding skills and expertise in different areas.
Is an expert on Microsoft .NET technologies, used to developed complex projects and to surpass difficult challenges. Designing and developing software is not only a job, but an exceeding passion, taken by an eagerness to solve problems the best way.
Usually if you want to change the source code of Network Simulator (NS), for instance, to test and develop a new network protocol, you’ll need the full source code of Network Simulator and you’ll need to compile it to incorporate your changes. This is a lot easier to do in Linux rather than with Windows, there’s also more tutorials and support.
However, sometimes you just want to configure a simulation to study how the common protocols behave and to learn how to use the simulator and its tools. This would only require the binary version of the NS and NAM. The problem here is that there’s no good site explaining how to do that completely, and with all the required resources.
The following link has all the required binaries. Unzip the files to “C:\ns-2“, or other path you would like, and add “C:\ns-2\bin” (please check if this is your path) to the Windows PATH (there are many tutorials to do this, for instance, click here to check this one).
After doing this, you can use the Network Simulator and Network Animator tools in the console, at any path. For using the Network Simulator you can type “ns <tcl file>“, for NAM you can type “nam <nam file>“.
You can download this ns-simple.tcl file and test it. Running “ns ns-simple.tcl” will write two output files, “out.tr” (trace file) and “out.nam” (nam file). You can run the NAM over the “out.nam” file to watch the exchange of packets. You can also run my tool over the trace file “out.tr” to check some statistics.
The new release is in development and it’s very important that you vote which functionalities do you value the most! 🙂
I’m considering developing it in Microsoft .NET C# 4.0, although Java can be executed in more operating systems… after the next release I can consider migrating the application to Java. What do you think? Feel free to add a comment with your opinion.
I will consider the following survey in the development of the new release. Please vote!
I’m posting the last version of NS2 Visual Trace Analyzer I’ve developed, 0.2.72.
It has many features: plots delay, jitter and throughput graphics, calculates many statistics per node or per flow and it has a visual interface of the nodes disposition along the simulation.
The visual tool doesn’t show the packets exchange, I’ve not finished this feature, but it shows pretty well the nodes disposition, coverage and movement.