Hi Carlo, "argos3 -q sensors " reports among other things the presence of the colored_blob_omnidirectional_camera, which says "A generic omnidirectional camera sensor to detect colored blobs", which to me implies that it should be able to be used with any robot model. However, as...

Hi Carlo/Michael, I know that multiple dynamics3d engines is not currently supported in general, because the boundary transfer is not implemented for all of the dynamics3d plugins to correctly transfer their information as robots cross the boundaries between engines. My question is more narrow: if I...

Hi Carlo, I had assumed that a foot-bot running inside of a pointmass3d engine would be able to interact with non-movable boxes/cylinders/etc that are created inside ARGoS, BUT upon creating an empty arena and simply having the robot drive forward, it reaches the edge of the arena and drives THROUGH...

Any update on this?

Hi Carlo, Are multiple pointmass3d engines officially supported in ARGoS? The docs ("argos3 -q pointmass3d") don't say one way or the other. I found out from Michael that multiple dynamics3d engines are not supported, and so I've switched to trying to use the pointmass3d engine instead, wh...

Hi Carlo, I've been doing some profiling in ARGoS with large robot swarms ( >8K) with large numbers of blocks in the arena (blocks are modeled as in the foraging example, as flat black shapes on the floor). I'm using the loop functions GetFloorColor() to determine the color of the floor in a given l...

Have you found a student to work on the foot-bot dynamics3d model? Just wondering if I should plan on adapting my 3D experiments with the foot-bot to work with the pointmass3d engine or not.

Thanks!
- John

Hi Carlo,

As part of my testing to with the dynamics3d engine, I found an initialization failure bug which I opened a pull request for (the <boundaries> tag is treated as a plugin). Very simple fix.

Any update on the proximity sensor?

- John

Hi Carlo, From my initial testing, the foot-bot proximity sensor seems to operate under the same assumption that the distance scanner does when you specifiy "rot_z_only", in that the foot-bot is assumed to be parallel to the XY plane. When I have the robot drive up one a shallow ramp, the ...

Ah so that is a bug. Is it an easy fix that I could do, if you point me to where to look? I tried trying to track the problem through the various layers of ARGoS but did not end up having any luck finding where to change/add a few lines.