Giter Site home page Giter Site logo

pr2_common's People

Contributors

aginika avatar ahendrix avatar archielee avatar arne48 avatar bmagyar avatar cottsay avatar danepowell avatar davetcoleman avatar furushchev avatar gerkey avatar jleibs-test avatar k-okada avatar knorth55 avatar kwc avatar pgrice avatar sachinchitta avatar scpeters avatar tfoote avatar theclearpathdash avatar thedash avatar trainman419 avatar v4hn avatar vrabaud avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

pr2_common's Issues

throttle: excessive CPU usage (ros ticket #1519)

throttle was observed on prf2 to consume ~20% CPU while throttling /stereo/cloud. It appeared that no subscribers were connected.

A quick test shows that a high input rate to throttle can indeed bring up its CPU usage. It can probably be fixed by being smarter about reusing memory rather than reallocating for each message. If necessary, the memcpy on incoming messages can be skipped when no subscribers are connected.

trac data:

rospy does not use sim time (ros ticket #1387)

I'm playing back a bag file, using "rosplay -b 100 name.bag". The -b option makes rosplay publish the bag recording time on the /time topic. On the parameter server I set the use_sim_time parameter:

$ rosparam get use_sim_time
true

In the python code I'm running, I want to get the rostime that is published by rosplay. I use:

rospy.sleep(2.0)
d.header.stamp = rospy.get_rostime()
print "time ",d.header.stamp

The problem is that the time that is printed is the system time, not the time when the bag was recorded:

$ ./detect_handle_from_bag.py
time 1242246848651374101

The actual rostime I want to get is:
$ rostopic echo time
rostopic: topic is [/time]
... logging to /u/meeussen/ros/ros/log/rostopic-13657-1242247140575.log

topic type is [roslib/Time]

header:
seq: 18
stamp: 1242147450772084035
frame_id:
rostime: 1242147450986051982

trac data:

laser_scan test tolerance needs to be larger than desired (ros ticket #1651)

hi Tully,

Some of the laser_scan tests have been failing on 64-bit since this build:

http://build.willowgarage.com/view/personalrobots/job/personalrobots-update-test-64/461/testReport/

Looks like your changes in r17401,r17402 triggered the failures.

If I'm reading the results correctly, then the test is pretty close, e.g.:

/home/rosbuild/hudson/workspace/personalrobots-update-test-64/personalrobots/common/laser_scan/test/projection_test.cpp:234
The difference between cloud_out.pts[i].x and scan.ranges[i] * cos(scan.angle_min + i * scan.angle_increment) is 1.08708e-06, which exceeds tolerance, where
cloud_out.pts[i].x evaluates to 2.57519,
scan.ranges[i] * cos(scan.angle_min + i * scan.angle_increment) evaluates to 2.57519, and
tolerance evaluates to 1e-06.

Perhaps the tolerance should be loosened a bit?

brian.

trac data:

fix param calls in ground plane node (ros ticket #1524)

like I did in the incremental updates

{{{
Revision: 16337
http://personalrobots.svn.sourceforge.net/personalrobots/?rev=16337&view=rev
Author: tfoote
Date: 2009-05-29 03:37:11 +0000 (Fri, 29 May 2009)

Log Message:

fixing param call to be cached for it was causing major delays sometimes 40Hz -> 1/2Hz

Modified Paths:

pkg/branches/milestone2/mapping/semantic_point_annotator/src/sac_inc_ground_removal.cpp

Modified: pkg/branches/milestone2/mapping/semantic_point_annotator/src/sac_inc_ground_removal.cpp

--- pkg/branches/milestone2/mapping/semantic_point_annotator/src/sac_inc_ground_removal.cpp 2009-05-29 03:31:35 UTC (rev 16336)
+++ pkg/branches/milestone2/mapping/semantic_point_annotator/src/sac_inc_ground_removal.cpp 2009-05-29 03:37:11 UTC (rev 16337)
@@ -132,10 +132,10 @@
void
updateParametersFromServer ()
{

  •  if (node_.hasParam ("~z_threshold")) node_.getParam ("~z_threshold", z_threshold_);
    
  •  if (node_.hasParam ("~ground_slope_threshold")) node_.getParam ("~ground_slope_threshold", ground_slope_threshold_);
    
  •  if (node_.hasParam ("~sac_fitting_distance_threshold"))  node_.getParam ("~sac_fitting_distance_threshold", sac_fitting_distance_threshold_);
    
  •  if (node_.hasParam ("~sac_distance_threshold"))  node_.getParam ("~sac_distance_threshold", sac_distance_threshold_);
    
  •  node_.getParam ("~z_threshold", z_threshold_, true);
    
  •  node_.getParam ("~ground_slope_threshold", ground_slope_threshold_, true);
    
  •  node_.getParam ("~sac_fitting_distance_threshold", sac_fitting_distance_threshold_, true);
    
  •  node_.getParam ("~sac_distance_threshold", sac_distance_threshold_, true);
    
    }
    }}}

trac data:

conduct an API review of robot_actions (ros ticket #1250)

there are many of us that don't really know what robot actions are and how they work. And they've made there way into prcore so we should do a quick API review of them this week.

Conner if you could put up a review page for them with a summary of their API and usage. And then schedule a review sometime this week that would be great.

trac data:

Create wiki pages for all packages in common stack (ros ticket #1593)

I've been creating a new sub-menu system on the wiki, including one for the common stack. In creating it, I noticed that several packages within the common stack do not have a wiki page yet. Please create them and also add the appropriate include macro:

{{{
[[Include(Menus/CommonStack)]]
}}}

(easier to copy and paste from another package in the stack

trac data:

make test fails to re-run, after it failed (ros ticket #1187)

I am debugging something in robot_actions.
I do make test
The test fails, for reasons that are legit
I make some changes to fix it and make test again. I get output as shown below, which is problematic because it:
a) indicates SUCCESS at the end

b) does not allow test to run again because of an nfs lock file preventing the test output directory from being written.

make[3]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' [ 90%] Built target _rospack_genmsg make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
Scanning dependencies of target robot_actions
make[3]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
[ 95%] Building CXX object CMakeFiles/robot_actions.dir/src/action_runner.o
Linking CXX shared library ../lib/librobot_actions.so
make[3]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' [ 95%] Built target robot_actions make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
Scanning dependencies of target test/utest
make[3]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
[100%] Building CXX object CMakeFiles/test/utest.dir/test/utest.o
Linking CXX executable ../test/utest
make[3]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' [100%] Built target test/utest make[2]: Leaving directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[1]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' if cd build && make -k test; then make test-results; else make test-results && exit 1; fi make[1]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[2]: Entering directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
[ 90%] Built target _rospack_genmsg
[ 95%] Built target robot_actions
[100%] Built target test/utest
make[4]: Entering directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' rm: cannot remove/u/mcgann/ros/ros/test/test_results/robot_actions/.nfs00000000006184f2000000d1': Device or resource busy
make[4]: *** [tests] Error 1
make[4]: Target CMakeFiles/tests.dir/build' not remade because of errors. make[4]: Leaving directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[3]: *** [CMakeFiles/tests.dir/all] Error 2
make[3]: Target CMakeFiles/test.dir/all' not remade because of errors. make[3]: Leaving directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[2]: *** [CMakeFiles/test.dir/rule] Error 2
make[2]: Target test' not remade because of errors. make[2]: Leaving directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[1]: *** [test] Error 2
make[1]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[1]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[2]: Entering directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[3]: Entering directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'

make[4]: Entering directory `/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'

[AGGREGATED TEST RESULTS SUMMARY]

PACKAGES:

  • robot_actions

SUMMARY

  • RESULT: SUCCESS
  • TESTS: 0
  • ERRORS: 0
  • FAILURES: 0

make[4]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' Built target test-results make[3]: Leaving directory/wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build'
make[2]: Leaving directory /wg/stor5a/mcgann/ros/ros-pkg/highlevel/robot_actions/build' make[1]: Leaving directory/wg/stor5a

trac data:

Move PolygonalMap, CollisionMap, and OrientedBoundedBox from robot_msgs to manipulation_msgs (Think about moving them elsewhere later) (ros ticket #1323)

Radu, we had a meeting about this yesterday and for now these are too specific for robot_msgs. If you get a change to do this it would be great. Otherwise I'll take care of it when I close the other tickets from this review.

The meeting notes are here:
http://pr.willowgarage.com/wiki/robot_msgs/2009-05-05_API_Review

trac data:

robot_actions: split into separate interface and message packages (ros ticket #1197)

robot_actions appears ready for inclusion in the prcore stack. As we don't want any domain-specific, pr2-specific code in the prcore stack, it will need to be split into separate interface and message packages.

The separate message package could be called pr2_robot_actions, or there could be separate domain-specific packages as appropriate.

As we are prepping prcore for release, please address this sooner rather than later.

trac data:

document image_msgs/Image (ros ticket #1363)

I made morgan's uvc_cam publish image_msgs/Image this weekend. And it ended up being mostly trial and error for what worked with some cutting and pasting from various sources such as wiki and ros-users posts. We need proper documentation and tutorials for how to load and unload. the cvBridge is only useful for going to and from opencv and is still not well documented.

trac data:

create a dictionary loading framework (ros ticket #1147)

This came out of the filters API review. This would be a generic framework for loading a dictionary of parameters. Either straight from the parameter server or from file such as yaml.

Something like:
DictionaryBrowser

With
DictionaryFromFile : public DictionaryBrowser

DictionaryFromParam : public DictionaryBrowser

Where dictionary broswer would expose a simple standardized way to browse through dictionaries. Something like a nested map of map with supported data types string, int, float, and vectors of those types.

trac data:

Twist uses Point when it should really use Vector3 (ros ticket #1723)

The vel and rot components of the Twist message should use a Vector3 and not a Point. This blocks all other Twist related tickets against this milestone. Also, if there are any bag files with the Twist message, the next version of the bag migration tools are needed before this fix can happen. Otherwise, bags will break.

trac data:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.