-ns-3 testing documentation
Tuesday, August 10, 2010
Regression
When a feature stops functioning as intended after some kind of of change to the system is integrated, it is called regression. Originally the term regression referred to a change that caused a previously fixed bug to reappear, but the term has evolved to describe any kind of change that breaks existing functionality. There are many kinds of regression that may occur in practice.
Wednesday, August 4, 2010
Why use simulation?
The main reasons to use simulation are:
1. Diagnosing process issue
1. Diagnosing process issue
2. Test performance improvement idea
3. Evaluating decisions
4. Stress test a system
Tuesday, July 20, 2010
pygccxml on Ubuntu
The steps to install pygccxml on Ubuntu:
1. Download pygccxml 1.0.0
1. Download pygccxml 1.0.0
2. Move to download directory
3. Extract pygccxml zip file
4. Move to extracted pygccxml file
5. Use this command : sudo python setup.py install
Thursday, July 8, 2010
ns-3.8 releases with WiMAX feature merged
ns-3.8, released on May 3, 2010 is merged with WiMAX features.
Monday, May 10, 2010
Module Includes
To help high level script users deal with the large number of include files present in the system, we group includes according to relatively large modules. A single include file are provided that will recursively load all of the include files used in each modules. It give you the ability to load a group of files at large granularity. This is not the most efficient approach but it certainly makes writing scripts much easier.
-ns-3 Tutorial
Saturday, May 8, 2010
CamelCase convention
Name encoding in ns-3 should follow the CamelCase convention where words are joined without spaces and are capitalized. For example: "My computer" is transformed into MyComputer. Do not use all capital letters such as MAC or PHY, but choose instead Mac or Phy. A goal of CamelCase convention is to ensure that the words which make up a name can be separated by the eye.
Variable names should follow a slight variation on the base CamelCase convention: camelBack. For example, the variable "user name" would be named "userName". This variation on the basic naming pattern is used to allow a reader to distinguish a variable name from its type. For example, "UserName userName;" would be used to declare a variable named userName of type UserName.
-ns-3-wimax/doc/codingstd.txt
Wednesday, March 10, 2010
HOWTO make and use a new application
How you go about making changes to components in large systems like ns-3 can seriously affect the level of happiness and stress in your life. So far we've taken an existing application and done nothing to it but change names. Even after this minor change, we observed that the application worked exactly as expected. This is a generic strategy. Take as much existing code as possible and then make small changes, stopping to make sure it all still works as much as possible. Although this may seem silly at first, it allows you to get your feet wet in a large system without getting into a state where you have no idea what is wrong and no idea how to find and fix the problem. This is not a pleasant place to be.
Good Luck !
Subscribe to:
Posts (Atom)