Delivery-Date: Thu Mar 15 00:43:40 2007
Date: Thu, 15 Mar 2007 00:41:11 -0700
From: Leslie Cheung <lccheung@usc.edu>
Subject: RE: cs551 nam file
In-reply-to: <92e7c4b70703142349t7f54e697n9355e2de565da9a5@mail.gmail.com>
Sender: lccheung@usc.edu
To: cs551@merlot.usc.edu
Message-id: <0JEX00917PCQEL20@msg-mx5.usc.edu>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Thread-index: AcdmziE4zluO5WaAT9i8jpGKGqGVkQABPDsg

Someone wrote:

> Do you know a good tutorial on nam file construction?

I don't really have any tutorial on nam traces. One good starting point is
the "status.out" example in the spec. Let me elaborate on the example here.

V -t * -v 1.0a5

This first line is an initialization command. Just keep this as the first
line in your nam output.

n -t * -s 3 -c red -i black
n -t * -s 4 -c red -i black

Each of these lines creates a node. 
"n" means node. 
"-t *" indicates time. You can just keep it this way.
"-s 3" means source id. This should represent the well-known port of the
nodes. (You can assume all nodes run on nunki, and hence using port number
alone can identify a node.)
"-c red" means color of the node is red.
"-I black" means color of the label (port number) is black.


l -t * -s 3 -d 4 -c blue

This line creates a link.
"l" means link". 
"-t *" indicates time. 
"-s 3" means source id, and "-d 4" means destination id. In the context of
our project, since all we care is who is connected to who, it doesn't matter
which node is the source, and which node is the destination. So, "-s 3 -d 4"
is the same as "-s 4 -d 3". Again, you can use port number as id.
"c blue" means the color of the link is blue.


There is documentation on Nam traces in the Ns manual. You can go to
http://www.isi.edu/nsnam/ns/doc/index.html and search for "Nam Traces"
(Subsection 46).


--Leslie