Bug 1547 – visualizer not working

Bug 1547 - visualizer not working


Summary:	visualizer not working

Status:	RESOLVED INVALID

Product:	ns-3
Classification:	Unclassified
Component:	visualizer
Version:	pre-release
Hardware:	PC Linux

Importance:	P5 blocker
Assigned To:	Gustavo J. A. M. Carneiro

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-12-09 23:27 UTC by Tom Henderson
Modified:	2012-12-10 23:52 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tom Henderson 2012-12-09 23:27:01 UTC

Current ns-3-dev does not work with visualizer.  I learned of this while testing a release candidate and testing the visualizer (this feature not covered by our buildslaves).

This testing performed on Ubuntu 11.10 system.  Both tests below run successfully on ns-3.15 release, but fail on ns-3-dev (they actually succeed in running the simulation but fail to launch the visualizer):

C++ visualization:

./waf --run examples/wireless/wifi-simple-adhoc-grid --vis

Python visualization:

./waf --pyrun src/flow-monitor/examples/wifi-olsr-flowmon.py --vis


I don't have any idea when this might have been introduced since ns-3.15.

Comment 1 Gustavo J. A. M. Carneiro 2012-12-10 05:16:52 UTC

Sorry, I moved to London and am a bit out of touch from ns-3 lately.  Is this blocking an imminent ns-3 release?  I might take a look tonight (London time).

Comment 2 Vedran Miletić 2012-12-10 07:27:30 UTC

Thanks Gustavo. Please also take a look at bug 954 if you can.

If help with bisecting is needed for this bug, I  volunteer to do it.

Comment 3 Tom Henderson 2012-12-10 23:52:49 UTC

Upon trying to bisect this tonight, I wasn't able to reproduce it, and I was able to successfully run it from C++ and Python up to changeset da7f1cf69d77 (the last one before side effects were introduced on Saturday).  This may have been a problem with my local desktop state (I have rebooted since then).

I'm marking as invalid as a result.