Testing your installation about swarm HOT 10 CLOSED

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

ns-3 is not needed. I've update the installation tutorial.

Did you compile and install the example directory as described in the tutorial?

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

• set assignee_account_id to "557058:4ded1ddf-947e-4154-bbd1-3dba24f1bdbd"
• set assignee to "caguero (Bitbucket: caguero, GitHub: caguero)"

from swarm.

Original comment by Pat Cappelaere (Bitbucket: cappelaere).

Yes I did. Example is actually running pretty far but it looks like the swarm members are not communicating.

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

The last version of the controller example doesn't print the neighbors on the console. You can go ahead and uncomment lines 162-169 in example/TeamControllerPlugin.cc to show this information in each update cycle.

#!python

// Uncomment the following block to display the list of neighbors.
// if (myNeighbors.empty())
//   std::cout << "[" << this->Host() << "] Neighbors: EMPTY" << std::endl;
// else
// {
//   std::cout << "[" << this->Host() << "] Neighbors:" << std::endl;
//   for (auto const &neighbor : myNeighbors)
//     std::cout << "\t" << neighbor << std::endl;
// }

from swarm.

Original comment by Pat Cappelaere (Bitbucket: cappelaere).

Hi Carlos,
It would be great if the examples outputs could match the installation guide without having to dink with the code.
Since I have no idea what they do... this makes it hard to check if my installation is working or not.
I have no idea what a BooController is or does. It does not look like it even generates a boo anymore. Am I right?
The TerrainTestPluggin.cc is looking for a terrain.csv and elevation.csv. How do they get created? Is this documented somewhere?
Sorry for all these questions.
Pat.

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

I have updated the code and the installation tutorial. Now, you should just see a message showing that the default team controller was successfully loaded:

#!python
[Msg] Waiting for master.
[Msg] Connected to gazebo master @ http://127.0.0.1:11345
[Msg] Publicized address: 172.23.1.7
[Msg] BrokerPlugin::ReadSwarmFromSDF: 3 swarm members found
[Msg] [192.168.3.1] TeamController plugin loaded succesfully
[Msg] [192.168.3.2] TeamController plugin loaded succesfully

The BOO controller should be generated when you compile the example directory.

Do not worry about TerrainTestPlugin, that's for our internal testing.

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

@cappelaere Is there something pending to do related with this issue?

from swarm.

Original comment by Pat Cappelaere (Bitbucket: cappelaere).

Hi Carlos,
I would recommend something a little better to test the installation than a program that prints a few lines and then hangs. I would have loved to see the three drones trying to find the lost person, find that person and exit cleanly. It would been nice to see the drones going over some terrain to get a feel for the capability. This would have been a great step to start. Just my two cents.
Thanks,
Pat.

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

The rest of the tutorials are covering different aspects of the vehicle capabilities and explain how to use the API for the specific features discussed in the tutorial.

Tutorial 7 exercises a more complete set of features in the line of your suggestion. They search the lost person, relay messages among the members of the team and communicate with the BOO.

from swarm.

Original comment by Carlos Agüero (Bitbucket: caguero, GitHub: caguero).

• changed state from "new" to "resolved"

Installation tutorial updated.

from swarm.