|
Javis vs. Nam (Features Comparison) |
|
|
|
|
|
Get all test files by click here.
1. Javis version 0.2
2. Nam version 1.0a8
Nam features not implemented on Javis:
1. "orient" option:
- This option, used to exactly specify the positions of nodes in the topologies, does not work on Javis.
2. showing a packet's details:
- With Nam, we can see the details of each packet currently showing on the simulation by click mouse on the packet itself. In contrast to Nam, Javis cannot show the details of each packet.
3. "label" method:
- With Nam, this method is used for labeling the interested positions on the simulation. However, this method does not affect to Javis.
4. traced variables:
- We can trace some interested variable by using "tracevar" method provided by Nam. We don't have to use any explicit output command (such as "puts") to show the values of traced variables. This method itself usually shows the values of traced variables at the bottom part of Nam's console (above the annotation part).
In contrast to Nam, "tracevar" method does not work on Javis. The developers have to use an explicit command to show the values of interested variables.
5. link color:
- With Nam, the developers can specify the desired link colors that will be shown on the simulation. This can be done by either "duplex-link-op" method or "simplex-link-op" method of the Simulator class.
On the other hand, Javis always shows links in black color.
6. a node's shape:
- With Nam, we can specify the shape of a node before starting the simulation. The provided shapes are "circle", "square" and "hexagon". However, Javis can show only circle nodes.
7. showing mobility of a node:
- With our test file, Javis right now cannot show any mobility of a node on the simulation. Moreover, it also cannot show control messages implemented by DSDV protocol. In Nam, this message is shown as a circle from a source node; gradually widen; then disappeared when it is out-of-range.
8. descriptions of multicast protocols' activities:
- When a multicast protocol, such as PIM-DM or CtrMcast, is running, Nam automatically shows the explanations of what is now happening on the simulation. For example, when a node called "n0" joins a multicast group say "0x800", Nam will automatically show at the annotation part as "node n0 - joins 0x800"
In contrast to Nam, Javis does not automatically show any explanations. The developers have to put the explanations by themselves.
Additional features implemented on Javis:
1. "text" event:
- This feature looks similar to Nam's annotation. It is shown on a screen at the specific time. The difference is that the "text" event is shown in the simulator; however, Nam's annotation is shown separately at the bottom of Nam's console. Moreover, in contrast to Nam's annotation, Javis's text event appears on the screen for only 0.05 simulation seconds.
Comments about the text event:
- At this time, the position of the desired text cannot be controlled. It is always shown at the left-top corner of the Javis's screen. It will be nice if Developer can control the position for showing his/her desired texts.
- Javis's text event stays on the Javis's screen for 0.05 simulation seconds, then it is deleted automatically. However, what will happen if we want to show the 2nd text after the 1st text for 0.25 simulation seconds? Of course, the second text will be written upon the 1st text. Then, we can read neither. It will be nice if Developer can get rid of the previous text in case that he/she wants to display the later one within less than 0.05 simulation seconds.