shardator's profile - activity

Hi,

When we are using ROS_DEBUG_STREAM() macro, and the output is configured to screen, everything is fine. But when we configure it to log, and it goes to file, we get extremely bloated lines, like:

1530790045.295181299 DEBUG [/home/whoever/catkin_ws/src/module/src/basecontroller.cpp:175(SomeClass::setGoal) [topics: /rosout, /robotpose, /initialpose, /layers/sensors, /layers/plaser, /layers/plaser2, /layers/pultrasound, /layers/pcamera, /layers/cleaning, /hwctrl, /s_pi, /status/opbutton, /status/cleaned_sqm, /status/clean_rate, /status/clean_start, /status/hw_serial, /status/sw_version, /status/core_status, /status/alert, /twr, /mapfile, /layers/map, /layers/map_inflated, /layers/map_active, ...] SomeClass::setGoal(): new goal has been set (mx=446 my=308 theta=2.35619 speed=0)

instead of like:

1530790045.295181299 DEBUG SomeClass::setGoal(): new goal has been set (mx=446 my=308 theta=2.35619 speed=0)

Is there any way to force this behavior in log files?

Thanks!

Hi,

I've been trying hard to install ROS Kinetic from source (so I can change some feature in it) on _clean_, freshly installed Ubuntu 16.04 setup according to the Installing from source manual (steps below) (Note, I was able install ROS Kinetic release on an other clean Ubuntu.)

sudo apt-get install python-rosdep python-rosinstall-generator python-wstool python-rosinstall build-essential
sudo rosdep init
rosdep update
mkdir ~/ros_catkin_ws
cd ~/ros_catkin_ws
rosinstall_generator desktop_full --rosdistro kinetic --deps --wet-only --tar > kinetic-desktop-full-wet.rosinstall
wstool init -j8 src kinetic-desktop-full-wet.rosinstall

At this point I get stuck in an infinite loop of

[opencv3] still active
[opencv3] still active
[opencv3] still active
[opencv3] still active

After killing it, and continuing with the following step:

rosdep install --from-paths src --ignore-src --rosdistro kinetic -y

I get stuck in the unrecoverable error

Reading state information... Done
E: Unable to locate package ros-kinetic-opencv3
ERROR: the following rosdeps failed to install
  apt: command [sudo -H apt-get install -y ros-kinetic-opencv3] failed

I have no idea how to continue from here. Could somebody please help?

Edit: OK, now to get past the error one needs to get rid of the -j8 flag. Some kind of race condition in the package management. It would be great if the documentation would be properly updated.

Note however I get a new error:

  apt: command [sudo -H apt-get install -y shiboken2] failed

This is a mess...

roslaunch find command does not follow symlinks Hi, Is there a way to make $(find ...) command follow symlinks in rosla

Hi! Thank you, this solved the problem! I tried add_subdirectory before, but I did something wrong. Now everything is fi

Hi,

We'd like to make our projects self-contained, so we are adding all possible (external) packages to our GIT repo as submodule, and build our project with catkin_make_isolated. This works with Ceres, Google Cartographer, etc., but does not seem to be working with some other module.

I added it as submodule, but the problem (apart from the missing package.xml, which I created) is that the CMakeLists.txt file is in a cmake/ directory, not in the package root. It looks like catkin_make_isolated fails to find the cmake/CMakeLists.txt file.

Moving or symlinking does not work, as the file uses other files in the cmake/ directory.

Is there a way to force catkin to look for CMakeLists.txt in cmake/?

Thanks.

How to catkin_make_isolated a non-catkin package when CMakeLists.txt not in pkg root Hi, We'd like to make our projects

How to catkin_make_isolated a non-catkin package when CMakeLists.txt not in pkg root Hi, We'd like to make our projects

Thanks. My only problem is that log4j is quite generic, while the topic listing is very ROS-specific. Also I'm not very

rosconsole: log file bloated with ros topics, etc. Hi, When we are using ROS_DEBUG_STREAM() macro, and the output is co

Hi,

It's hard to believe, but according to my research I am the only one who would like to accelerate simulation of a ROS robot... and it seems to be an almost impossible task.

It looks like when I create a node that generates faster than real time clock topic, it totally messes up the simulation. Not even bags can be replayed faster, than real time.

The reason, as I found is that a huge part of the ROS system relies on WallTime and WallDurations, and not just by using these classes, but by doing waits and sleeps in wall times relevant in the simulation.

I tried to create an accelerated version of ROS:

• Removed the definitions of WallTime and SteadyTime, replaced them with typedefs to Time
• Removed the definition of WallDuration and replaced it with typedef to Duration
• Scaled all timed waits with my desired acceleration factor
• Instead of a clock topic I share the time from a timer process in shared memory, so all calls to Time::now() are in sync

But now I get stuck in various timing issues related to transformations, more specifically I get errors, like:

Lookup would require extrapolation into the future.  Requested time 1270387817.717999935 but the latest data is at time 1270387817.482000113

(Note that the timestamp is intentionally in the past, as it is an accelerated time, not the real time.)

Now in the stack trace, as I see, this is happening in waitForTransform() call, which is called with Time(0) by the simulation (stdr_simulator). And this is weird, semantically, as I would think (by the name of it) that waitForTransform() is intended to wait, until the transform is available, not throw an exception that it is not (yet).

Could please someone help here?

UPDATE I think the problem is somehow related to BufferCore::getLatestCommonTime(). Somehow the cached times does not match the cached transforms.

:( We've explored simple options already. This looks like a difficult task. I think it would be nice to have a 10x accel

I'm also trying to create a simple example, but I'm stuck with some stupid issue with nanosleep() in my /clock generator

Sorry, I did not mean to be rude. I'm struggling with this for some time now, and am a bit frustrated. Yes, I think the

Hi! Thanks. We need to do batch simulations (with perturbed parameters) for optimization, so we need like 20x accelerate

This is because of the 1ms hard-coded delay. 20Hz on 25x acceleration is 500Hz, which is 2ms per timer. If you have 3 ti

This is because of the 1ms delay. 20Hz on 25x acceleration is 500Hz, which is 2ms per timer. If you have 3 timers, espec

OK, so if your timers are 20Hz, and the simulation is accelerated to 25x speed, you cannot have more than 2 timers on qu

We even get incorrect timings in unaccelerated simulated time, which does not actually contain the current real time. It

We even get incorrect timings if we use a /clock, which does not actually contain the current real time. It works, but w

I did that. It simply does not work correctly for anything complex. Only for very simple scenarios. Do you happen to kno

Pardon me my ignorance, but I fail to see how. If I set a timer in my robot's own code, it will fire with physical, real

Hi, The simulator does not provide a clock, I checked that. There is no clock publisher in that. Also, there is no way _

For the record, I updated the ticket, I hope that helps a bit.

Thanks. I've opened it as https://github.com/ros/ros_comm/issues/1272

I will, but I doubt that this will be fixed, as for real time use, this is a non-issue. I need a working workaround, as

speed of the clock...

No, I found that ROS core things fire at wrong times. So wrong, that my robot teleports off the map. It has nothing to d

Also, I know about the Time(0) semantics, it is just after a while, inside waitForTransform() is replaced by some common

No, it does not, because timer delays are expected to be real time. So if you set a timer to 10Hz, it will fire 10Hz rea

stdr_simulator: Accelerating simulation Hi, It's hard to believe, but according to my research I am the only one who wo

stdr_simulator: Accelerating simulation Hi, It's hard to believe, but according to my research I am the only one who wo

stdr_simulator: Accelerating simulation Hi, It's hard to believe, but according to my research I am the only one who wo