Hello Jeff, now is almost clear, but I need to remove few doubts.
>>> Some questions about your script: >>> - if I use X,Y locations which is the command from python to change pixel- >> per-meter-scale? > > These lines set the origin (ref pt) and scale: > > session.location.setrefgeo(47.57917,-122.13232,2.00000) > session.location.refscale = 150.0 > Do I have to set the refgeo point also with X,Y locations? >>> - if I use X,Y locations may I use 2ray/freespace pathless mode? (I guess >> yes, but you grouped differently); > > Yes. Set emane_event_monitor=True in /etc/core/core.conf if you want to > subscribe to EMANE location events; emane_event_monitor=False if you want to > generate them using the X,Y location of nodes. > In summary if I have to emulate Wi-Fi end-point communication at two different distance, e.g. 200m and 500m I have to set up the scale: session.location.refscale=100.0 #100 pixel = 100m first distance, e.g. 200 m: Node1 = (100, 50) and Node2 = (300, 50) first distance, e.g. 500 m: Node1 = (100, 50) and Node2 = (600, 50) >>> - if I use 3 and select pathlossmode=pathloss, do I have to launch pathloss >> event GUI? Is there a way to set up the pathloss between nodes only via >> python? > > There is no pathloss event GUI; there is a Comm Effect Controller GUI (which > would be option #4), only works with the Comm Effect EMANE model. There are > emaneeventpathloss Python bindings that make it easy to generate pathloss > events from a Python script. > >>> - If I use pathloss events, how does CORE manage the distance in pixel >> between nodes? I guess that it consider the pathloss written for each link. > > With pathloss events, location doesn't matter. > This point is not clear, at least for me, few months ago I used in CORE the emanelosscontroller. Is that still alive? Which is the difference with emaneeventpathloss? >>> As maybe you have already understand I would manage all the scenario from a >> python script and use the GUI only to verify the set up of parameters. In >> fact if I launch a session using python and then I attach the CORE GUI to the >> session I noted that any changes on the GUI doesn't have any effect on the >> simulation... >>> maybe I made some mistake... what do you think? > > You can start the Python script from the GUI and the GUI will connect to the > running session; see "Execute Python script" under the File Menu: > http://pf.itd.nrl.navy.mil/core/core-html/usage.html#file-menu > > Also, you can start a Python script with this syntax: > # start cored as normal > sudo cored > # tell cored to execute a script and add the session to the active session > list > cored -e /path/to/mycorescript.py > # run the script, passing it command-line arguments > cored -e "/path/to/mycorescript.py -n 10" > > The GUI can later connect to scripts started this way using the "Session" > > "Change sessions..." menu item. Ok, thanks. I said that in my emulations the GUI attached to a session wasn't able to produce any effect because I had the following scenario: I launched a session with a python script. I opened CORE with this command: "sudo core" (not cored!) In the window a select the session already launched with the script. I reduced the txpower till based on my calculation I shouldn't have any wireless link, BUT I continued to ping the two nodes. Which was my mistake? Regards, Simone _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
