Importing video traffic into OPNET - Revision history

Cly at 21:30, 2 April 2009

2009-04-02T21:30:21Z

2009-04-02T21:30:01Z

2009-04-02T21:29:10Z

2009-04-02T21:28:05Z

2009-04-02T20:52:18Z

2009-04-02T20:52:02Z

2009-04-02T20:50:55Z

2009-04-02T20:48:23Z

2009-04-02T20:46:17Z

2009-04-02T20:42:56Z

@@ Line 13: / Line 13: @@
 For Verbose Trace File use this shell command line to do the extraction:
 <pre>
-''awk '// {print $4/8}' video_trace.data > traffic_trace.csv''
+awk '// {print $4/8}' video_trace.data > traffic_trace.csv
 </pre>
 For Terse Trace File use this:
-:''awk '// {print $2/8}' terse_trace.data > traffic_trace.csv''
+<pre>
 Save the output file into your opnet_models folder. Or any folder in your OPNET models path.

@@ Line 12: / Line 12: @@
 For Verbose Trace File use this shell command line to do the extraction:
+<pre>
-:''awk '// {print $4/8}' video_trace.data > traffic_trace.csv''
+''awk '// {print $4/8}' video_trace.data > traffic_trace.csv''
 For Terse Trace File use this:

@@ Line 1: / Line 1: @@
-==Video Traces==
+== Video Traces ==
 Video Trace files available at
@@ Line 6: / Line 6: @@
-==Processing Video Traces==
+== Processing Video Traces ==
 The video traces data required pre-processing before they could be imported into OPNET Modeler video conferencing application (VCA) traffic data. The frame sizes need to be extracted from the video traces, then converted from bits to bytes. Saving the final result as a .csv compatible format file.
@@ Line 19: / Line 19: @@
 Save the output file into your opnet_models folder. Or any folder in your OPNET models path.
-==OPNET Setup==
+== OPNET Setup ==
 * From the Object Palette insert an "Application Config" node

@@ Line 37: / Line 37: @@
 [[Image:Streaminfo.png]]
-* On the client workstation select the profile with the Application you've just created.
+* On the client/workstation select the profile with the Application you've just created.
 * Run the simulation :)

← Older revision		Revision as of 20:52, 2 April 2009
Line 36:		Line 36:
	Select "Edit" for Incoming and Outgoing stream. Set ''Distribution Name=scripted'' for both incoming and outgoing stream. Enter the processed traffic_trace (without .csv extension).		Select "Edit" for Incoming and Outgoing stream. Set ''Distribution Name=scripted'' for both incoming and outgoing stream. Enter the processed traffic_trace (without .csv extension).
	[[Image:Streaminfo.png]]		[[Image:Streaminfo.png]]
		+
		+	* On the client workstation select the profile with the Application you've just created.
		+
		+	* Run the simulation :)

@@ Line 17: / Line 17: @@
 :''awk '// {print $2/8}' terse_trace.data > traffic_trace.csv''
 ==OPNET Setup==
@@ Line 33: / Line 34: @@
 * Select "Edit" for Frame Size Information (bytes)

← Older revision		Revision as of 20:48, 2 April 2009
Line 30:		Line 30:

	* Enter the video's frame rate into "Frame Interarrival Time Information" field.		* Enter the video's frame rate into "Frame Interarrival Time Information" field.
		+	[[Image:Framerates.png]]

	* Select "Edit" for Frame Size Information (bytes)		* Select "Edit" for Frame Size Information (bytes)

@@ Line 20: / Line 20: @@
 ==OPNET Setup==
-From the Object Palette insert an "Application Config" node
+* From the Object Palette insert an "Application Config" node
 [[Image:Application.png]]
-Next, edit the attributes of the Application node. Under Application Definitions->Description select "Video Conferencing". Choose "Edit"
+* Next, edit the attributes of the Application node. Under Application Definitions->Description select "Video Conferencing". Choose "Edit"
 [[Image:App_attributes.png]]

← Older revision		Revision as of 20:42, 2 April 2009
Line 25:		Line 25:

	Next, edit the attributes of the Application node. Under Application Definitions->Description select "Video Conferencing". Choose "Edit"		Next, edit the attributes of the Application node. Under Application Definitions->Description select "Video Conferencing". Choose "Edit"
		+
	[[Image:App_attributes.png]]		[[Image:App_attributes.png]]