iNSpect version 4 is a wireless and wired network visualization tool. iNSpect 4.0 is faster and more agile than its 3.4 predecessor with a more lightweight object design and a number of applied design patterns. The results of this effort are a more user friendly program with many opportunities for custom code. iNSpect has been tested successfully on:
- Ubuntu & Debian: g++ 4.1.2, 4.2.1, and 4.3.2, gtkglext 1.2.0, and OpenGL 2.0
- Redhat & Fedora Core: g++ 4.2.1, gtkglext 1.2.0, and OpenGL 2.0
- Windows XP (SP2): Dev-C++ 188.8.131.52, GLUT 3.7, GTK+ 2.10.11 (NOTE: iNSpect does not compile in Cygwin)
All of the code in iNSpect version 4.0 was developed by members of either the Toilers Research Group at the Colorado School of Mines or the Department Security Technology at the Fraunhofer Institute for Computer Graphics Research. Specifically:
- Tracy Camp, Stuart Kurkowski, Mike Colagrosso, Neil (Tuli) Mushell, Matthew Gimlin, Neal Erickson, and Jeff Boleng from the Toilers Research Group at the Colorado School of Mines were a part of creating the original iNSpect visualization tool for wireless networks.
- Fatih Gey and Peter Eginger from the Department Security Technology at the Fraunhofer Institute for Computer Graphics Research over-hauled the original iNSpect visualization tool for wireless networks. This overhaul provided a cleaner and more logical class structure, allowing it to be much easier to extend this visualization tool.
- Jeremy Norman, Chris Walsh, Kurt Strovink, and Tracy Camp from the Toilers Research Group at the Colorado School of Mines significantly modified and extended the Fraunhofer IGD implementation of iNSpect (e.g., added support for wired networks, faster load times, threaded file reading, better memory management, Connectivity Graph, and more).
Links from this page outline contact information for bug reports, comments, and suggestions. Also, there are a few pages that explain how to extend iNSpect with custom traces and more.
Installation and Usage Instuctions
For more information about installing iNSpect, please click here
. For usage instructions for version 4.0, please click here
. While iNSpect can run on windows (see installation instructions), it does not show any of the text output from iNSpect; thus, error messages will not be visible (since they are printed to cerr).
Examples of Using iNSpect
Examples of using iNSpect are available within sample.tgz
A full demo (for iNSpect 3.5) is available within demo-full.tgz
A movie showing the LAR protocol (iNSpect 3.x) is available at: LARmovie.avi
A movie showing iNSpect version 4 is available at: wireless.avi
Getting the iNSpect code
If you would like the code to iNSpect 4, please complete the form below. This form will help us keep track of interest in iNSpect (for publications, etc); no personal information will be made available to anyone outside of the Toilers. Once you complete this form, you will receive an email from us with information on downloading iNSpect.
Useful and Other Custom Code
Creating your Own Custom Code
iNSpect has many ways for custom code to be developed and integrated into the visualizer, model, controller, and input system. You can find resources for how to add custom code here
. If you do create custom code, feel free to contact us and let us know what features you added and send us a patch. Maybe your code will be incorporated directly into the main distribution. Otherwise, we can put a note on this page which explains your extension, a link to your site, and instructions on how to install it.
iNSpect 3.x required that the initial node locations were at the beginning of the NS-2 trace file at time 0. iNSpect 4 no longer requires this, but the utility may still be of use for when reading trace files directly or if using an older version of iNSpect. Use traceFix.py as follows: python traceFix.py It produces a new trace file by the name Fix.tr traceFix.py
: Fixes trace files that don't have initial node locations at the top of the trace file
NS-2 to vizTrace converter
Saeed Khalafinejad from Sharif University of Technology has written a program that converts an NS-trace file to an iNSpect viz-Trace file*. He created both a C++ version and a delphi version. Click here for the C++ version
and here for the delphi version
. If you have any questions about this code, contact Saeed at: email@example.com
. * Due to the major overhaul of inspect for version 4, the vizTrace format is currently not supported. This will hopefully change in the near future. If you have a need for this format specifically, please contact Tracy Camp
for either an older version of inspect or to inquire if trace has been added back yet.
Please send any comments, questions, suggestions, or enhancement patches to firstname.lastname@example.org