Ask Your Question

dearl's profile - activity

2015-03-03 01:55:13 -0500 received badge  Popular Question (source)
2015-03-03 01:55:13 -0500 received badge  Notable Question (source)
2015-03-03 01:55:13 -0500 received badge  Famous Question (source)
2012-09-05 15:18:51 -0500 received badge  Necromancer (source)
2012-09-05 13:18:19 -0500 answered a question Gazebo 1.0.x and CUDA in Furete

I'm going to hazard a guess that it is no longer supported/maintained. In $(rosfind gazebo)/build/gazebo-r22f33a2ed71a/deps/parallel_quickstep/ there is some code that references CUDA, but I can't find anywhere where it connects to the main gazebo program (renaming the folder seems to have no ill effects on compilation). The patch files in the main directory don't look like they have been updated since before fuerte.

2012-08-27 14:06:39 -0500 answered a question Where can I download swistrack for ROS?

using roslocate prints out this info:

$roslocate info swistrack
- svn:
    local-name: swistrack
    uri: http://ua-ros-pkg.googlecode.com/svn/trunk/arrg/ua_experimental/swistrack

checking out the repo seems to have a non-standard makefile which downloads swistrack from a 3rd party repo and applies a ros-specific patch.

2012-07-19 09:43:05 -0500 answered a question ROS not working when Home directory is renamed

try a bash script to clean everything. although you might still have to clean up some by hand if the makefiles aren't the standard ros makefile

find . -name Makefile > foo
export MY_PWD=`pwd`
while read line 
do 
    DIR=`dirname $line`
    cd "$DIR"
    make clean
    cd "$MY_PWD" 
done < foo  
2012-07-12 16:22:03 -0500 received badge  Teacher (source)
2012-07-12 14:56:04 -0500 answered a question How to make a robot immovable in Gazebo

If you don't want the robot to move at all, I believe that in your urdf adding the entry <link name="world"/> and create a fixed joint between world and your robot will do what you want.

2012-07-06 07:40:37 -0500 answered a question ROS not working when Home directory is renamed

If you move the ROS folder, all the executables may look for the libraries in the old places. After updating all your variables you'll need to clean and remake all the packages.

so, fix your setup.sh, and re-source the setup.bash script, go into ros/ dir and 'make clean; make' to build rospack, etc, and then perform 'rosmake --pre-clean -ak'. Some packages may fail and then you may need to go individually to it and 'make clean; make'

2012-07-05 14:18:46 -0500 received badge  Editor (source)
2012-07-05 14:17:32 -0500 asked a question running fuerte gazebo gui and server on separate machines seg fault

Has anyone been successful in running the fuerte gazebo server on a different machine than the gui? When I try, I get a seg fault once the gui connects.

the details: machines A,B are connected via openvpn without connectivity issue. On machine A I intend to run the gui and I ssh into B. I set the ROS_MASTER_URI and GAZEBO_MASTER_URI to point towards B with ports 11311 and 11345 respectively. I set DISPLAY on B to be :0.0 ( it has its own monitor, same error with X forwarding ). Running the roscore and the server works fine (using empty.world). Once I start the gui on A, the gui finds the server on B and then the server on B crashes.

(forgive me, not enough karma to post a file)
ROS is installed from source in in ~/ros/fuerte on both machines, the user is different between the two. I do have gazebo built in 'debug' mode and running in gdb, so I can provide more information as needed.

 
#0  0x00007ffff7599fa2 in boost::asio::basic_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp=""> >::close (this=0x0) at /usr/include/boost/asio/basic_socket.hpp:264
#1  0x00007ffff7592162 in gazebo::transport::Connection::Close (this=0x7fffdcb1d9b0) at /home/robo/ros/fuerte/simulator_gazebo/gazebo/build/gazebo/src/transport/Connection.cc:363
#2  0x00007ffff75b9c53 in gazebo::transport::Connection::OnReadHeader<boost::_bi::bind_t<void, boost::_mfi::mf1<void,="" gazebo::transport::publicationtransport,="" std::string="" const&="">, boost::_bi::list2<boost::_bi::value<gazebo::transport::publicationtransport*>, boost::arg<1> > > > (this=0x7fffdcb1d9b0, _e=..., _handler=...)
    at /home/robo/ros/fuerte/simulator_gazebo/gazebo/build/gazebo/src/transport/Connection.hh:152
#3  0x00007ffff75bb6d7 in boost::_mfi::mf2<void, gazebo::transport::connection,="" boost::system::error_code="" const&,="" boost::tuples::tuple<boost::_bi::bind_t<void,="" boost::_mfi::mf1<void,="" gazebo::transport::publicationtransport,="" std::string="" const&="">, boost::_bi::list2<boost::_bi::value<gazebo::transport::publicationtransport*>, boost::arg<1> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >::operator() (
    this=0x7fffe715b9c0, p=0x7fffdcb1d9b0, a1=..., a2=...) at /usr/include/boost/bind/mem_fn_template.hpp:280
#4  0x00007ffff75bb349 in boost::_bi::list3<boost::_bi::value<gazebo::transport::connection*>, boost::arg<1> (*)(), boost::_bi::value<boost::tuples::tuple<boost::_bi::bind_t<void, boost::_mfi::mf1<void,="" gazebo::transport::publicationtransport,="" std::string="" const&="">, boost::_bi::list2<boost::_bi::value<gazebo::transport::publicationtransport*>, boost::arg<1> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >::operator()<boost::_mfi::mf2<void, gazebo::transport::connection,="" boost::system::error_code="" const&,="" boost::tuples::tuple<boost::_bi::bind_t<void,="" boost::_mfi::mf1<void,="" gazebo::transport::publicationtransport,="" std::string="" const&="">, boost::_bi::list2<boost::_bi::value<gazebo::transport::publicationtransport*>, boost::arg<1> > >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >, boost ...
(more)