-
 
No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.1.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/pyros-dev/ros1_template.git
VCS Type git
VCS Version master
Last Updated 2017-08-31
Dev Status MAINTAINED
CI status Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Python Template ROS node for use with catkin following good practices

Additional Links

Maintainers

  • AlexV

Authors

  • AlexV

ROS1 Python Template

This package is a template to be used as a reference when creating a new ROS1 node with python, to be used with catkin. In this package we are following http://wiki.ros.org/BestPractices as much as possible, where it makes sense.

Usage

  • Create a catkin_workspace ( Ref : http://wiki.ros.org/catkin/Tutorials/create_a_workspace )
  • Add this ros1_pytemplate package into src/ of the workspace (and maybe more like beginner_tutorials)
  • Build the workspace (Ref : http://wiki.ros.org/catkin/Tutorials/using_a_workspace
  • Source the devel workspace:

    $ source devel/setup.bash
    
  • manually run some python test:

    $ nosetests tests/test_ros1_pytemplate/test_lib_module.py
    
  • manually run some ROS tests:

    $ rostest ros1_pytemplate oracle.test
    
  • run all the tests:

    $ catkin run_tests
    
  • launch some nodes (log on terminal):

    $ roslaunch ros1_pytemplate all.launch --screen
    
  • install that workspace:

    $ make install
    
  • source the install workspace:

    $ source install/setup.bash
    
  • launch some nodes (log in files in .ros/log):

    $ roslaunch ros1_pytemplate all.launch
    
CHANGELOG

Changelog for package ros1_pytemplate

Forthcoming

  • Merge remote-tracking branch 'origin/master' into cpp
  • Merge pull request #9 from pyros-dev/fix_launchers Fix rostests with launchers
  • using better find_package strategy to avoid broken catkin components. making roslinting optional.
  • fixing xml
  • Revert "fixed remap rules for answer_server test" This reverts commit 00afff596609ef78c47fce0249283e673129f148.
  • roslinting
  • fixed remap rules for answer_server test
  • reviewing remaps and code to be able to pass tests running from different namespaces
  • fixing tests to be run with rosrun only and keep them simple.
  • commenting pyros_setup since one might not have the dependency installed and it s not mandatory.
  • Integration all.test checks only all launcher
  • Add msgs dependency
  • Fix fibonacci.launch sub
  • fixing pub sub and remap for integration test
  • Merge pull request #7 from pyros-dev/python restructuring and renaming packages
  • fixing config file paths for integration tests
  • first attempt at integration tests.
  • Fix launcher package renaming
  • Add rostests for launchers
  • generated documentation structure for ros1_pytemplate with sphinx-quickstart removed unused travis builds.
  • restructuring and renaming packages
  • Contributors: AlexReimann, AlexV, Alexander Reimann

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Dependant Packages

No known dependants.

Launch files

  • launch/all.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • answer_override [default: $(find ros1_pytemplate)/config/answer-override.yaml] — used by upper launchers to customize configuration
      • fibonacci_override [default: $(find ros1_pytemplate)/config/fibonacci-override.yaml] — used by upper launchers to customize configuration
  • launch/fibonacci.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • config_override [default: $(find ros1_pytemplate)/config/fibonacci-override.yaml] — used by upper launchers to customize configuration
  • launch/answer.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • config_override [default: $(find ros1_pytemplate)/config/answer-override.yaml] — used by upper launchers to customize configuration

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros1_pytemplate at Robotics Stack Exchange

No version for distro hydro. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.1.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/pyros-dev/ros1_template.git
VCS Type git
VCS Version master
Last Updated 2017-08-31
Dev Status MAINTAINED
CI status Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Python Template ROS node for use with catkin following good practices

Additional Links

Maintainers

  • AlexV

Authors

  • AlexV

ROS1 Python Template

This package is a template to be used as a reference when creating a new ROS1 node with python, to be used with catkin. In this package we are following http://wiki.ros.org/BestPractices as much as possible, where it makes sense.

Usage

  • Create a catkin_workspace ( Ref : http://wiki.ros.org/catkin/Tutorials/create_a_workspace )
  • Add this ros1_pytemplate package into src/ of the workspace (and maybe more like beginner_tutorials)
  • Build the workspace (Ref : http://wiki.ros.org/catkin/Tutorials/using_a_workspace
  • Source the devel workspace:

    $ source devel/setup.bash
    
  • manually run some python test:

    $ nosetests tests/test_ros1_pytemplate/test_lib_module.py
    
  • manually run some ROS tests:

    $ rostest ros1_pytemplate oracle.test
    
  • run all the tests:

    $ catkin run_tests
    
  • launch some nodes (log on terminal):

    $ roslaunch ros1_pytemplate all.launch --screen
    
  • install that workspace:

    $ make install
    
  • source the install workspace:

    $ source install/setup.bash
    
  • launch some nodes (log in files in .ros/log):

    $ roslaunch ros1_pytemplate all.launch
    
CHANGELOG

Changelog for package ros1_pytemplate

Forthcoming

  • Merge remote-tracking branch 'origin/master' into cpp
  • Merge pull request #9 from pyros-dev/fix_launchers Fix rostests with launchers
  • using better find_package strategy to avoid broken catkin components. making roslinting optional.
  • fixing xml
  • Revert "fixed remap rules for answer_server test" This reverts commit 00afff596609ef78c47fce0249283e673129f148.
  • roslinting
  • fixed remap rules for answer_server test
  • reviewing remaps and code to be able to pass tests running from different namespaces
  • fixing tests to be run with rosrun only and keep them simple.
  • commenting pyros_setup since one might not have the dependency installed and it s not mandatory.
  • Integration all.test checks only all launcher
  • Add msgs dependency
  • Fix fibonacci.launch sub
  • fixing pub sub and remap for integration test
  • Merge pull request #7 from pyros-dev/python restructuring and renaming packages
  • fixing config file paths for integration tests
  • first attempt at integration tests.
  • Fix launcher package renaming
  • Add rostests for launchers
  • generated documentation structure for ros1_pytemplate with sphinx-quickstart removed unused travis builds.
  • restructuring and renaming packages
  • Contributors: AlexReimann, AlexV, Alexander Reimann

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Dependant Packages

No known dependants.

Launch files

  • launch/all.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • answer_override [default: $(find ros1_pytemplate)/config/answer-override.yaml] — used by upper launchers to customize configuration
      • fibonacci_override [default: $(find ros1_pytemplate)/config/fibonacci-override.yaml] — used by upper launchers to customize configuration
  • launch/fibonacci.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • config_override [default: $(find ros1_pytemplate)/config/fibonacci-override.yaml] — used by upper launchers to customize configuration
  • launch/answer.launch
    • Standard launch file. for more information check http://wiki.ros.org/roslaunch/XML.
      • config_override [default: $(find ros1_pytemplate)/config/answer-override.yaml] — used by upper launchers to customize configuration

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged ros1_pytemplate at Robotics Stack Exchange

No version for distro melodic. Known supported distros are highlighted in the buttons above.