Here are the compiler flags I use when compiling and linking (for gcc7): -O3 -ggdb -Ofast -fno-trapping-math -fno-signed-zeros -march=native -fno-stack-protector -flto I'm using the footbot proximity, light, motor_ground sensors (though there are others in the input .argos file that I don't use that...

I've been playing around with the # engines/ # threads parameters in the multiple_engines example, and haven't been able to obtain real-time results for anything over 200 robots or so. I've modeled my configuration after what was described in the original ARGoS paper: 16 cores/16 physics engines/16 ...

Hope IROS went well! Any update on the mult-physics engine example?

- John

Awesome, thank you!

Hi, I'm trying to use multiple physics engines to divvy up the processing of robots distributed throughout the arena, so I can run with a 1024 robot swarm of homogeneous controllers, but can't find any examples of how to do so. There is a single reference to a section <arena_physics> in the input fi...

When I use the binary argos from the download page and compile my code with gcc/g++ 7.2 then I also get a loop functions not found error, even though the symbols ARE in the .so library. Argos finds the library without a problem, and everything works as expected, IF I use gcc 5.4. Is this a known iss...

Hello, I've been trying to compile my code into a .so (based on the foraging example originally) using icpc, as I have found that compiler to give much better performance for many workloads on intel chips However, whenever I try to run it with the version of ARGoS that is in the .deb for ubuntu dist...