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.

-ns-3 testing documentation

Wednesday, August 4, 2010

Why use simulation?

The main reasons to use simulation are:

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
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

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 !

Monday, March 8, 2010

An Improved IEEE 802.16 WiMAX Module for the ns-3 Simulator

Abstract: 

IEEE 802.16 WiMAX is a promising new wireless technology for providing broadband ubiquitous network access. As more and more researchers and industrials are interested in simulating such networks, a number of WiMAX simulators have been emerged in the networking community. One of the most recent WiMAX simulator is the one developed for ns-3. This module provides a standard compliant and well designed implementation of the standard and benefits from the major enhancements provided by ns-3 (compared to other network simulators) which has all the capabilities of becoming the leading network simulator in near future. However, this WiMAX module still lacks some important features which motivated this work. In this paper, we first provide a snapshot of existing WiMAX simulators available in the public domain, while highlighting their limitations. Then, we describe the new features and enhancements we have integrated within the ns-3 WiMAX module, and in particular: a realistic and scalable physical model, an IP packet classifier for the convergence sub-layer, efficient uplink and downlink schedulers, support for multicast traffic and pcap packet tracing functionality. The new design of the physical layer has improved the simulation time by several magnitude orders while still providing a realistic implementation of the standard. Furthermore, the IP classifier has enabled the simulation of an unlimited number of service flows per subscriber station, while the proposed schedulers improve the management of the QoS requirements for the different service flows.

Monday, February 8, 2010

ns-3-wimax vs ns-3-wimax-release

Firdaus masterwimax@gmail.com Feb 05 01:41AM -0800

Hi,

Is there any major different between ns-3-wimax and ns-3-wimax-release
previously?

Thank you.

Ismail Amine Amine.Ismail@sophia.inria.fr Feb 05 11:42AM +0100

Hi Firdaus,

ns-3-wimax is based on ns-3-dev changeset 5944 however ns-3-wimax-release is based on an older version. So please use ns-3-wimax. The repository ns-3-wimax-release will be deleted soon.

Sunday, January 3, 2010

ns-3-wimax overview

The ns-3-wimax module implement the Point-to-Multipoint (PMP) mode and the WirelessMAN-OFDM PHY layer of 802.16 model with the fundamental functions of the CS and MAC CPS.

The ns-3 WiMAX model is mainly composed of three layers:

1. The Convergence Sublayer (CS)
2. The MAC Common Part Sublayer (MAC-CPS)
3. The Physical Layer (PHY)