Got it. I'll pull the latest from the tutorial, and look at demo 0 and 1 again. Thanks for all the help!
Thanks, Cem Karan ________________________________________ From: Steven Galgano [sgalg...@adjacentlink.com] Sent: Monday, February 05, 2018 4:48 PM To: Karan, Cem F CIV USARMY RDECOM ARL (US) Cc: emane-users@nrl.navy.mil Subject: Re: [emane-users] [Non-DoD Source] Re: Help understanding 'platformendpoint' and 'transportendpoint' All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser. ---- Cem, I have already removed the two unused input files from the tutorial [1]. There is no issue with emane. The emulator did what it was supposed to do - it rejected the XML with a detailed reason. You may benefit from (re)reviewing the tutorial. You seem to be missing some necessary understanding. There are many ways to run emane - demo 2 is another way. From the demo 2 wiki entry [2]: "The first thing you probably noticed is that all of the NEMs in this demonstration will be instantiated by a single emulator instance. Depending on your scenario and radio model resource requirements, there may be performance issues when running multiple NEMs per emulator instance. In this case, we'll be fine." I would suggest spending time on demo 0 and demo 1. Demo 1 is most likely how you would run your experiment. [1] Caution-https://github.com/adjacentlink/emane-tutorial/commit/9fc1091f233d363ea7dffcf33ac6e7f0cb9f5cd6 [2] Caution-https://github.com/adjacentlink/emane-tutorial/wiki/Demonstration-2 -steve On 02/05/2018 04:33 PM, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote: > Actually, can you check > Caution-https://github.com/adjacentlink/emane-tutorial/blob/master/2/platform.xml > as > well? If we're supposed to name the platforms with different numbers, then > that would suggest that we'd have one nem element per platform, correct? From > demo 2's platform.xml file, it appears that we're supposed to have multiple > nem elements, one per container. If this isn't so, then the DTDs and the > examples all need to be changed. > > Thanks, > Cem Karan > > --- > Other than quoted laws, regulations or officially published policies, the > views expressed herein are not intended to be used as an authoritative state > of the law nor do they reflect official positions of the U.S. Army, Department > of Defense or U.S. Government. > > >> -----Original Message----- >> From: emane-users [Caution-mailto:emane-users-boun...@nrl.navy.mil] On >> Behalf Of >> Karan, Cem F CIV USARMY RDECOM ARL (US) >> Sent: Monday, February 05, 2018 4:12 PM >> To: Steven Galgano <sgalg...@adjacentlink.com> >> Cc: emane-users@nrl.navy.mil >> Subject: Re: [emane-users] [Non-DoD Source] Re: Help understanding >> 'platformendpoint' and 'transportendpoint' >> >> Hrm... OK, do you want me to log a bug, or have you already logged a bug for >> the cruft? >> >> As for the platform, the only thing I have to do is have platform<number>, >> and everything else is handled correctly? If this is so, then I >> have to have a platform file for every container/node, correct? Should I >> create separate eelgenerator.xml files for every platform? What >> about any other files? >> >> Thanks, >> Cem Karan >> >> --- >> Other than quoted laws, regulations or officially published policies, the >> views expressed herein are not intended to be used as an >> authoritative state of the law nor do they reflect official positions of the >> U.S. Army, Department of Defense or U.S. Government. >> >> >>> -----Original Message----- >>> From: Steven Galgano [Caution-mailto:sgalg...@adjacentlink.com] >>> Sent: Monday, February 05, 2018 3:43 PM >>> To: Karan, Cem F CIV USARMY RDECOM ARL (US) <cem.f.karan....@mail.mil> >>> Cc: emane-users@nrl.navy.mil >>> Subject: Re: [Non-DoD Source] Re: [emane-users] Help understanding >>> 'platformendpoint' and 'transportendpoint' >>> >>> All active links contained in this email were disabled. Please verify >>> the identity of the sender, and confirm the authenticity of all links >>> contained within the message prior to copying and pasting the address >>> to a Web browser. >>> >>> >>> >>> >>> ---- >>> >>> Looks like you were ~lucky~ enough to pick one of two demos that have >>> leftover cruft from older emane-tutorials. That file is not used. >>> When you type 'make' you get the actual files, for example >>> gpsdlocationagent1.xml: >>> >>> <eventagent library="gpsdlocationagent"> >>> <param name="pseudoterminalfile" >>> value="persist/1/var/run/gps.pty"/> >>> </eventagent> >>> >>> Having platform<NodeId>.xml files will cause them to run in the >>> appropriate container. >>> >>> -steve >>> >>> >>> On 02/05/2018 03:26 PM, Karan, Cem F CIV USARMY RDECOM ARL (US) wrote: >>>> I just checked the version of emane I'm running; 1.0.1. >>>> >>>> I got the gpsdconnectionenabled parameter by looking through the XML >>>> configuration files in the emane tutorial at >>>> Caution-Caution-https://github.com/adjacentlink/emane-tutorial/blob/master/3 >>>> /g >>>> psdlocationagent.xml >>>> and >>>> Caution-Caution-https://github.com/adjacentlink/emane-tutorial/blob/master/4/gpsdlocationagent.xml. >>>> Is that code now out of date? It is also in >>>> /usr/share/emane/xml/agents/gpsdlocation/gpsdlocationagent.xml, at >>>> least on my system. After deleting gpsdconnectionenabled, I reran >>>> everything and now have errors on gpsdcontrolsocket. I got that >>>> parameter out of the emane tutorials as well, and it also shows up >>>> in /usr/share/emane/xml/agents/gpsdlocation/gpsdlocationagent.xml. >>>> I deleted that one as well, and now only have the error that you >>>> mentioned below about emane being run on the host. >>>> >>>> So, how do the tutorials handle starting emane within each of the >>>> containers? >>>> I took the code at >>>> Caution-Caution-https://github.com/adjacentlink/emane-tutorial/blob/master/s >>>> cr >>>> ipts/democtl-host >>>> and >>>> Caution-Caution-https://github.com/adjacentlink/emane-tutorial/blob/master/s >>>> cr ipts/demo-init as starting points in how I'm supposed to do >>>> things, but it appears that things aren't working as expected. >>>> >>>> Thank you again for all your help in this; it really is a big help. >>>> >>>> Thanks, >>>> Cem Karan >>>> >>>> --- >>>> Other than quoted laws, regulations or officially published >>>> policies, the views expressed herein are not intended to be used as >>>> an authoritative state of the law nor do they reflect official >>>> positions of the U.S. Army, Department of Defense or U.S. Government. >>>> > _______________________________________________ emane-users mailing list emane-users@nrl.navy.mil https://publists.nrl.navy.mil/mailman/listinfo/emane-users
