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