To build the nightly snapshot, you need to grab the nightly snapshot of protolib ( https://www.nrl.navy.mil/itd/ncs/products/protolib ) and place it in the main scriptools directory (or symlink to it) as scriptools/protolib so that the makefiles can find it. There may be additional system libraries required as well (e.g. gdal-dev).
-Jeff Weston > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of GONZALEZ, > SAXXON K DR-01 USAF AFMC AFRL/RITF > Sent: Tuesday, November 08, 2016 2:49 PM > To: [email protected] > Subject: Re: [emane-users] Using CORE with EMANE > > Thank you for your response. I have begun exploring scriptools, however when > building the examples as described in the Scriptools > User Guide step 1.1 it fails due to some missing protoTree.h file. Below is > the command I ran and the exact error. I searched for > the > file but it is nowhere in the downloaded zip file. If anyone has any > experience running theses scriptool examples please advise. > > I downloaded the Oct 26 scriptool snapshot from the following link. > http://downloads.pf.itd.nrl.navy.mil/mnmtools/nightly_snapshots/ > > Command: > > $ cd mnmtools/scriptools/makefiles > $ make -f Makefile.linux mp mg gb > > Error: > > ... > ../include/mp.h:8:23:fatal error: protoTree.h: No such file or directory ... > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Vijayasarathy > Rajagopalan > Sent: Tuesday, November 08, 2016 12:25 AM > To: [email protected] > Subject: Re: [emane-users] Using CORE with EMANE > > Hi, > > > 1. Make CORE subscribe to EMANE events: > > Make emane_event_monitor=True in /etc/core/core.conf > > > 2. Generate your Network and mobility plan, and extract the mobility model > using MNM tools (scriptools as Brian pointed out). I have > not used nmf2core.py but I have had good success with the standard sequence > (1. mp 2. enp.py 3.mg <http://3.mg> 4.gb > <http://4.gb> ). Refer to scriptools manual for more information. This will > create an eel file which will contain GPS coordinates of > the > NEM IDs (If a node has two NEMs, then the NEMs will have the same GPS > coordinates at any particular second, that will be a simple > validation), and the corresponding pathloss variations at different points in > the emulation. > > > 3. Create the corresponding imn file in CORE. Run it once and note as to what > NEM IDs are used against which interfaces. Set the > "pathlossmode" property of the chosen EMANE model to "precomputed" so that > CORE/EMANE does not compute the pathloss, but > expects them from the EEL file > > > 4. The NEM IDs generated by CORE may be different from the NEM IDs generated > by MNM tools for the same NEMs. In this mode, > we have to manually map the NEM IDs correctly in order to get the correct > mobility for NEMs. This is done by modifying the NEM IDs > in > the file emulationDirectory.xml (generated by enp.py) in order to align with > the NEM IDs that CORE generates (thankfully CORE > generates the same NEM IDs for the same NEMs across different emulations). > Re-run mg and gb in order to get the modified eel file. > > > 5. The reference point (0,0) of CORE gets mapped with a standard GPS > coordinate (see Canvas -> size/scale). This reference GPS > coordinate has to be manually changed according to the GPS coordinates that > get generated in the eel file above. If this is not > done, > the (x,y,z) transformed coordinates generated from the eel GPS coordinates > (during emulation run) may generate negative values > and the emulation will run into errors. No foolproof solution here - I had to > "find out" a suitable reference using trial and error, > given > all the GPS coordinates in the eel file. > > > 6. We are set for running the emulation. Use eventservice.xml and > eelgenerator.xml templates, and run emaneeventservice from the > host after starting the emulation: emaneeventservice eventservice.xml > > > NOTE: The device into which EMANE events are pushed is very important for all > the emulation nodes to receive the events (check > with emane.log in individual nodes if they have received the events). This > device is the controlnet interface device at the host, > whose > name changes for every emulation run - it is of the form > b.ctrl0net.<variable>. I have a script which greps on ifconfig and finds > out the > interface name, and replaces this on an eventservice.XML template (<param > name="eventservicedevice" value="CTRLNET_IF"/>, > with CTRLNET_IF replaced), and starts the emaneeventservice. > > > 7. You can optionally use SDT3D for visualization. > > > Brian, it will be great to have a short tutorial on using nmf2core.py as part > of scriptools. > > > Also please let me know if there is a better way of doing part(s) of the > procedure I have explained above. > > > Vijay > > > On Fri, Nov 4, 2016 at 9:30 PM, <[email protected] > <mailto:[email protected]> > wrote: > > > Send emane-users mailing list submissions to > [email protected] > <mailto:[email protected]> > > To subscribe or unsubscribe via the World Wide Web, visit > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > <http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users> > or, via email, send a message with subject or body 'help' to > [email protected] > <mailto:[email protected]> > > You can reach the person managing the list at > [email protected] > <mailto:[email protected]> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of emane-users digest..." > > > Today's Topics: > > 1. Using CORE with EMANE > (GONZALEZ, SAXXON K DR-01 USAF AFMC AFRL/RITF) > 2. Re: Using CORE with EMANE (Steven Galgano) > 3. Re: Using CORE with EMANE (Brian Adamson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 3 Nov 2016 17:25:13 +0000 > From: "GONZALEZ, SAXXON K DR-01 USAF AFMC AFRL/RITF" > <[email protected] > <mailto:[email protected]> > > Subject: [emane-users] Using CORE with EMANE > To: "[email protected] > <mailto:[email protected]> > " > <[email protected] > <mailto:[email protected]> > > Message-ID: > > <f85ea51306d26c48a95b38dc3abaf7ee0569f...@52zhtx-d02-02b.area52.afnoapps.usaf.mil > <mailto:f85ea51306d26c48a95b38dc3abaf7ee0569f...@52zhtx-d02-02b.area52.afnoapps.usaf.mil> > > > > Content-Type: text/plain; charset="us-ascii" > > Hello, > > I was hoping someone might be able to point me to any resources that > can get > me started with using CORE in conjunction with EMANE. The CORE manual > has > very little information on how to do this. Particularly I am interested > on > how I can use CORE to subscribe to EMANE events. The CORE manual > mentions > that this is possible but never says how to do so. > > Thank you for any assistance that you can provide me. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/pkcs7-signature > Size: 5386 bytes > Desc: not available > Url : > http://pf.itd.nrl.navy.mil/pipermail/emane-users/attachments/20161103/805d5829/attachment-0001.bin > <http://pf.itd.nrl.navy.mil/pipermail/emane-users/attachments/20161103/805d5829/attachment-0001.bin> > > ------------------------------ > > Message: 2 > Date: Thu, 3 Nov 2016 13:47:20 -0400 > From: Steven Galgano <[email protected] > <mailto:[email protected]> > > Subject: Re: [emane-users] Using CORE with EMANE > To: "GONZALEZ, SAXXON K DR-01 USAF AFMC AFRL/RITF" > <[email protected] > <mailto:[email protected]> > > Cc: "[email protected] > <mailto:[email protected]> > " > <[email protected] > <mailto:[email protected]> > > Message-ID: <[email protected] > <mailto:[email protected]> > > Content-Type: text/plain; charset=windows-1252 > > I believe your question is better suited for the core-users mailing > list: > > [email protected] <mailto:[email protected]> > http://pf.itd.nrl.navy.mil/mailman/listinfo/core-users > <http://pf.itd.nrl.navy.mil/mailman/listinfo/core-users> > > -- > Steven Galgano > Adjacent Link LLC > www.adjacentlink.com <http://www.adjacentlink.com> > > > On 11/03/2016 01:25 PM, GONZALEZ, SAXXON K DR-01 USAF AFMC AFRL/RITF > wrote: > > Hello, > > > > I was hoping someone might be able to point me to any resources that > can > get > > me started with using CORE in conjunction with EMANE. The CORE manual > has > > very little information on how to do this. Particularly I am > interested on > > how I can use CORE to subscribe to EMANE events. The CORE manual > mentions > > that this is possible but never says how to do so. > > > > Thank you for any assistance that you can provide me. > > > > > > > > _______________________________________________ > > emane-users mailing list > > [email protected] > <mailto:[email protected]> > > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > <http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users> > > > > > ------------------------------ > > Message: 3 > Date: Thu, 3 Nov 2016 14:02:01 -0400 > From: Brian Adamson <[email protected] > <mailto:[email protected]> > > Subject: Re: [emane-users] Using CORE with EMANE > To: "GONZALEZ, SAXXON K DR-01 USAF AFMC AFRL/RITF" > <[email protected] > <mailto:[email protected]> > > Cc: [email protected] > <mailto:[email protected]> , > "[email protected] <mailto:[email protected]> " > <[email protected] > <mailto:[email protected]> > > Message-ID: <[email protected] > <mailto:[email protected]> > > Content-Type: text/plain; charset="utf-8" > > In the /etc/core.conf file, you can enable EMANE event monitoring by > setting > the corresponding attribute to ?true?. I can?t remember the exact attribute > name but it?s something like emane_monitor. This causes CORE to subscribe to > the EMANE event channel and when location events are received, it translates > the EMANE GPS location to the CORE canvas x,y location and updates the node > locations on the CORE canvas. So, it?s a fairly limited use of EMANE events. > > Another visualization option is using the 3-D ?Scripted Display Tool? > (SDT). > CORE has some rudimentary support to drive an associated SDT display, but I > generally have my EMANE event generator (separate from CORE) also drive the > SDT display with node locations and ?link up? and ?link down? status according > to the predicted radio connectivity given pathless and radio parameters. SDT > layers let you use its links, symbols and other annotations to visualize > different aspects of the running emulation. Eventually, it may be nice to > have set of ?SDT widgets? similar to the current CORE canvas widgets > accessible from the CORE GUI. > > At the moment I tend to use _both_ the CORE canvas and its widgets > along with > a separate SDT visualization (and sometimes multiple SDT visualizations with > different views and layer sets) to monitor various emulation activities in > different ways. You can also capture the SDT commands for future playback, > but at the moment these added capabilities are in the ?do it yourself? > department. We hope to mature and share more of these things we develop as > ?add ons? to the emulation framework over time. I do have a Python-based > suite in development that ingests Network Modeling Framework (NMF) XML > ?planning? documents we are using to define scenarios (mobility, network/comms > connectivity, and application/protocol services) then uses the CORE Python > APIs to have CORE deploy the emulation into container-based VMs on a single > host or set of hosts running the core-daemon and begin its execution. This > Python tool (called ?nmf2core.py?) includes its own event generator to > generate EMANE > events as well as drive an SDT display. This code currently accesses > and > uses the EMANE python event service APIs that CORE instantiates for its own > EMANE control and monitoring. > > This code is available for download from > http://downloads.pf.itd.nrl.navy.mil/mnmtools/nightly_snapshots/ > <http://downloads.pf.itd.nrl.navy.mil/mnmtools/nightly_snapshots/> as the > ?scriptools-svnsnap.tgz? file. (ou can run "python setup.py install nmf? to > install the Python tools I am describing here. (we have formalized any stable > releases of this stuff yet). I also have a little bit of ?how-to? > documentation on using the ?nmf2core.py? and associated tools from this > package, but the long pole in the tent is the documentation for creating new > scenarios defined by the NMF XML files is not very mature. But the code in > development here may give you some ideas for enriching your CORE+EMANE > experience. We?re hoping to provide a more integrated option of using these > different components together over time, while preserving the modularity and > ability to use these on an independent basis, too (e.g. EMANE usage > configure/deployed/controlled by other means, too). We may directly add these > capabilities to the CORE code base itself (or CORE?s proge > ny) in the future as the concept and implementation matures. Since, > at this > time, this work is done as a side effort in conjunction with our ongoing > research activities, I don?t have a specific timeline for that maturation. > > (I just saw Steve Galgano?s note regarding posting this to the > core-users > mailing list, so this response is also cross-posted to that list.) > > best regards, > > Brian > > > > On Nov 3, 2016, at 1:25 PM, GONZALEZ, SAXXON K DR-01 USAF AFMC > AFRL/RITF > <[email protected] <mailto:[email protected]> > wrote: > > > > Hello, > > > > I was hoping someone might be able to point me to any resources that > can > get > > me started with using CORE in conjunction with EMANE. The CORE manual > has > > very little information on how to do this. Particularly I am > interested on > > how I can use CORE to subscribe to EMANE events. The CORE manual > mentions > > that this is possible but never says how to do so. > > > > Thank you for any assistance that you can provide me. > > _______________________________________________ > > emane-users mailing list > > [email protected] > <mailto:[email protected]> > > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > <http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users> > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://pf.itd.nrl.navy.mil/pipermail/emane-users/attachments/20161103/e2fd3e2c/attachment-0001.html > <http://pf.itd.nrl.navy.mil/pipermail/emane-users/attachments/20161103/e2fd3e2c/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > emane-users mailing list > [email protected] <mailto:[email protected]> > http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users > <http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users> > > > End of emane-users Digest, Vol 79, Issue 2 > ****************************************** > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
