> Hei Jeff, > > really thanks for the example. > Currently I had some old simulations with CORE 4.3 + EMANE 0.7…. and I would > migrate to the new version. > I downloaded the virtual machine that you provided on the web. > > Some questions about your script: > - if I use X,Y locations which is the command from python to change > pixel-per-meter-scale? > - if I use X,Y locations may I use 2ray/freespace pathless mode? (I guess > yes, but you grouped differently); > - 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? > - 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. > > 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? > > thanks again. > > Simone > > On May 20, 2013, at 10:04 PM, "Ahrenholz, Jeffrey M" > <[email protected]> wrote: > >> Simone, >> >>> -- how does CORE manage distance. In fact I have to reproduce real >>> distances, >>> 100 m, 500 m and 1000 m. >>> -- do I have to draw my network playing with coordinates. I mean >>> NODE1(X1,Y1), NODE2(X2,Y2) and then for the first scenario (i.e. 100m) I >>> should have X2-X1 = 100 and Y2-Y1=0. Of course setting up the right scale >>> in >>> canvas options Scale 100pixel =100m. >>> >>> - Pathloss: -- If I use 80211abg model in EMANE which mode do I have to >>> select? 2ray or pathloss? -- If I do have to use pathloss mode, do I >>> have to calculate separately the pathloss for 100m, 500m and 1000m and >>> then create Events in the PathlossEventGenerator? >> >> Currently your options for EMANE loss between nodes (pathloss) are: >> 1. X,Y locations using GUI and properly setting the pixels-per-meter scale >> 2. lat/long/alt location events using 2-ray/freespace pathloss mode >> 3. using pathloss events, directly specify dB path loss between node pairs >> >> If you're using #2, a tool like Google Earth or similar may help with >> authoring geographic waypoints; for #3 it seems that you really would need >> to understand what you were doing and what the SINR curves look like... >> >>> Last about CORE, if I launch a scenario via python similarly as described >>> here: http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-July/000980.html >>> and then I link the CORE GUI to this session. >>> May I change parameters, e.g. pathloss mode to use PathlossEvent Generator? >>> I have some doubts that these changes don't have any effect on the >>> emulation. >> >> Attached is an example CORE Python script that adds N nodes to an EMANE >> 802.11 network. In this example, I've changed the pathloss mode to >> 'pathloss'. You can see the resulting setting in /tmp/pycore.*/*phy.xml. You >> could change any of the 802.11 MAC/PHY parameters at that same line in the >> code. I'll include this example in the CORE source under >> core/daemon/examples/netns/ (for future snapshots/releases.) >> >> -Jeff >> <emane80211.py> >
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
