Thanks. /opt/ros/cturtle appears to be setup properly, and I'm sourcing /opt/ros/cturtle/setup.sh in my .bashrc. However, I also have to manually set environment variables (ROBOT, ROBOT_NAME, ROS_MASTER_URI, etc.) since there are no /etc/ros/cturtle setup files. Are these meant to be created manually if desired, or is there some canonical source? -- Anand On Fri, Aug 6, 2010 at 8:50 AM, Ken Conley wrote: > The cturtle setup.sh files append to your PYTHONPATH, which is > different from the boxturtle behavior, which reset your PYTHONPATH. It > sounds like we may need to figure out some fancier way of setting the > cturtle path to not result in this condition. > > FYI: installing cturtle via deb should place the setup files in > /opt/ros/cturtle. The /etc/ layout is currently specific to the PR2 > configuration. Your standard procedure for using it should simply be > to source the cturtle setup file instead of the boxturtle setup file. > > - Ken > > On Fri, Aug 6, 2010 at 2:27 AM, Anand Atreya wrote: > > Thanks, Ken. It looks like the PYTHONPATH was the culprit. Boxturtle's > > roslib was first since the .bashrc was still loading boxturtle's > setup.bash. > > > > Is there a standard procedure for using cturtle (or some other distro) on > a > > robot with boxturtle installed as the default? The /etc/ros/cturtle > > directory is missing, and I know that's the proper way to get all the > > necessary environment variables set. Should that have been created as > part > > of a cturtle debian package? > > > > Thanks. > > -- Anand > > > > On Thu, Aug 5, 2010 at 11:04 PM, Ken Conley > wrote: > >> > >> Hi Anand, > >> > >> What's your PYTHONPATH? Do you have two copies of roslib on it? What > >> does roswtf output? > >> > >> - Ken > >> > >> On Thu, Aug 5, 2010 at 10:45 PM, Anand Atreya > >> wrote: > >> > I'm getting a Python error when I try to launch pr2_dashboard. one is > in an outdated format. > > On Fri, Aug 6, 2010 at 8:50 AM, Ken Conley wrote: > >> The cturtle setup.sh files append to your PYTHONPATH, which is >> different from the boxturtle behavior, which reset your PYTHONPATH. It >> sounds like we may need to figure out some fancier way of setting the >> cturtle path to not result in this condition. >> >> FYI: installing cturtle via deb should place the setup files in >> /opt/ros/cturtle. The /etc/ layout is currently specific to the PR2 >> configuration. Your standard procedure for using it should simply be >> to source the cturtle setup file instead of the boxturtle setup file. >> >> - Ken >> >> On Fri, Aug 6, 2010 at 2:27 AM, Anand Atreya wrote: >> > Thanks, Ken. It looks like the PYTHONPATH was the culprit. Boxturtle's >> > roslib was first since the .bashrc was still loading boxturtle's >> setup.bash. >> > >> > Is there a standard procedure for using cturtle (or some other distro) >> on a >> > robot with boxturtle installed as the default? The /etc/ros/cturtle >> > directory is missing, and I know that's the proper way to get all the >> > necessary environment variables set. Should that have been created as >> part >> > of a cturtle debian package? one is in an outdated format. >> >> On Fri, Aug 6, 2010 at 8:50 AM, Ken Conley wrote: >> >>> The cturtle setup.sh files append to your PYTHONPATH, which is >>> different from the boxturtle behavior, which reset your PYTHONPATH. It >>> sounds like we may need to figure out some fancier way of setting the >>> cturtle path to not result in this condition. >>> >>> FYI: installing cturtle via deb should place the setup files in >>> /opt/ros/cturtle. The /etc/ layout is currently specific to the PR2 >>> configuration. Your standard procedure for using it should simply be >>> to source the cturtle setup file instead of the boxturtle setup file. >>> >>> - Ken >>> >>> On Fri, Aug 6, 2010 at 2:27 AM, Anand Atreya wrote: >>> > Thanks, Ken. It looks like the PYTHONPATH was the culprit. >>> Boxturtle's >>> > roslib was first since the .bashrc was still loading boxturtle's >>> setup.bash. >>> > >>> > Is there a standard procedure for using cturtle (or some other distro) >>> on a >>> > robot with boxturtle installed as the default? The /etc/ros/cturtle >>> > directory is missing, and I know that's the proper way to get all the >>> > necessary environment variables set. Should that have been created as >>> part >>> > of a cturtle debian package? >>> > >>> > Thanks. >>> > -- Anand >>> > >>> > On Thu, Aug 5, 2010 at 11:04 PM, Ken Conley >>> wrote: >>> >> >>> >> Hi Anand, >>> >> >> > >> > Thanks. >> > -- Anand >> > >> > On Thu, Aug 5, 2010 at 11:04 PM, Ken Conley >> wrote: >> >> >> >> Hi Anand, >> > > >> > Similarly, > >> > and perhaps for a related reason, I'm also unable to use > >> > pr2_tabletop_manipulation.launch to start the grasping pipeline. The > >> > errors > >> > I'm getting are below. Any ideas what might be wrong? I'm guessing > >> > it's > >> > something simple, but I've been poking around for a while to no avail. > >> > > >> > I'm running the most recent Cturtle debs on our PR2. > >> > > >> > Thanks. > >> > -- Anand > >> > > >> > > >> > $ rosrun pr2_dashboard pr2_dashboard > >> > Traceback (most recent call last): > >> > File > >> > "/opt/ros/cturtle/stacks/pr2_gui/pr2_dashboard/scripts/pr2_dashboard", > >> > line > >> > 50, in > >> > import pr2_dashboard > >> > File > >> > > >> > > "/opt/ros/cturtle/stacks/pr2_gui/pr2_dashboard/src/pr2_dashboard/__init__.py", > >> > line 1, in > >> > from pr2_frame import * > >> > File > >> > > >> > > "/opt/ros/cturtle/stacks/pr2_gui/pr2_dashboard/src/pr2_dashboard/pr2_frame.py", > >> > line 43, in > >> > from robot_monitor.robot_monitor_panel import RobotMonitorPanel > >> > File > >> > > >> > > "/opt/ros/cturtle/stacks/diagnostics/robot_monitor/src/robot_monitor/robot_monitor_panel.py", > >> > line 44, in > >> > from diagnostic_msgs.msg import DiagnosticArray, DiagnosticStatus, > >> > KeyValue > >> > File > >> > > >> > > "/opt/ros/cturtle/stacks/common_msgs/diagnostic_msgs/src/diagnostic_msgs/msg/__init__.py", > >> > line 1, in > >> > from _DiagnosticArray import * > >> > File > >> > > >> > > "/opt/ros/cturtle/stacks/common_msgs/diagnostic_msgs/src/diagnostic_msgs/msg/_DiagnosticArray.py", > >> > line 311, in > >> > _struct_I = roslib.message.struct_I > >> > AttributeError: 'module' object has no attribute 'struct_I' > >> > > >> > > >> > > >> > $ roslaunch pr2_tabletop_manipulation_launch > >> > pr2_tabletop_manipulation.launch > >> > Traceback (most recent call last): > >> > File "/opt/ros/cturtle/ros/bin/roslaunch", line 2, in > >> > from ros import roslaunch > >> > File "/opt/ros/boxturtle/ros/core/roslib/src/ros/__init__.py", line > >> > 63, in > >> > __getattr__ > >> > return __import__(name) > >> > File > "/opt/ros/cturtle/ros/tools/roslaunch/src/roslaunch/__init__.py", > >> > line 43, in > >> > from roslaunch.config import ROSLaunchConfig > >> > File "/opt/ros/cturtle/ros/tools/roslaunch/src/roslaunch/config.py", > >> > line > >> > 49, in > >> > import roslaunch.loader > >> > File "/opt/ros/cturtle/ros/tools/roslaunch/src/roslaunch/loader.py", > >> > line > >> > 45, in > >> > from roslib.names import make_global_ns, ns_join, PRIV_NAME, > >> > load_mappings, is_legal_name, canonicalize_name > >> > ImportError: cannot import name canonicalize_name > >> > > >> > > >> > > >> > > >> > _______________________________________________ > >> > ros-users mailing list > >> > ros-users@code.ros.org > >> > https://code.ros.org/mailman/listinfo/ros-users > >> > > >> > > >> _______________________________________________ > >> ros-users mailing list > >> ros-users@code.ros.org > >> https://code.ros.org/mailman/listinfo/ros-users > > > > > > _______________________________________________ > > ros-users mailing list > > ros-users@code.ros.org > > https://code.ros.org/mailman/listinfo/ros-users > > > > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >