clearpath_config: 2.0.0-1 in 'jazzy/distribution.yaml' [bloom]

[tonybaltovski]

Increasing version of package(s) in repository clearpath_config to 2.0.0-1:

• upstream repository: https://github.com/clearpathrobotics/clearpath_config.git
• release repository: https://github.com/clearpath-gbp/clearpath_config-release.git
• distro file: jazzy/distribution.yaml
• bloom version: 0.12.0
• previous version for package: null

clearpath_config

* Add HE2410 & HE2411 battery support (#110 <https://github.com/clearpathrobotics/clearpath_config/issues/110>) (#111 <https://github.com/clearpathrobotics/clearpath_config/issues/111>)
  * Add support for the HE2410 and HE2411 batteries to J100 and A200
* Fixed tests.
* Add additional controllers (#105 <https://github.com/clearpathrobotics/clearpath_config/issues/105>)
  * Add Xbox controller support
  * Add PS5 controller support
* Add enable_ekf property to platform (#106 <https://github.com/clearpathrobotics/clearpath_config/issues/106>)
* Re-add the A200/A201 Observer sample now that https://github.com/clearpathrobotics/clearpath_common/pull/122 is merged (#107 <https://github.com/clearpathrobotics/clearpath_config/issues/107>)
* Fix failing tests (#104 <https://github.com/clearpathrobotics/clearpath_config/issues/104>)
  * Remove the husky observer sample; it depends on as-yet-unmerged changes to clearpath_common
  * Flag the Zed camera as unsupported for now
  * Skip any additional tests if there's an unsupported platform or accessory in the sample
* Fix the Axis camera topics (#100 <https://github.com/clearpathrobotics/clearpath_config/issues/100>)
* Raise an UnsupportedPlatformException for the Jackal (for now); we don't have Jazzy firmware for it yet (#103 <https://github.com/clearpathrobotics/clearpath_config/issues/103>)
* A300 VCAN (#102 <https://github.com/clearpathrobotics/clearpath_config/issues/102>)
  * A300 vcan0 bridge
  * Disable vcan1 bridge for now
* Fix support for the device_type parameter; previously the camera would always be a Q62 (#99 <https://github.com/clearpathrobotics/clearpath_config/issues/99>)
* Add the A200 Observer backpack attachment (#96 <https://github.com/clearpathrobotics/clearpath_config/issues/96>)
  * Add the A200 Observer backpack attachment
  * Add the Husky Observer sample
  * Add the IMU to the sample
  * Add source CI
  * Linting for new CI
  * More linting
  * Silently replace the A201 prefix with A200; this lets us support the Observer with minimal changes elsewhere (and the number of A201 bases is very small)
  * Update the Observer sample to use the A201 serial numbers
* Add A300 samples (#98 <https://github.com/clearpathrobotics/clearpath_config/issues/98>)
  * Add the AMP mount attachment
  * Add A300 samples
  * Add the outline sample
  * Add AMP frame to sample
* Bugfix MODEL.keys() (#97 <https://github.com/clearpathrobotics/clearpath_config/issues/97>)
* A300 battery comment to LiFEPO4
* Fix all linting errors
* Add a300 extra ros parameters
* Add a300 to attachment mux
* Add a300 platform empty ros parameters
* Add a300 can interfaces
* Add a300 platform battery
* Add a300 platform attachments
* Add A300 platform entry
* Add the ability to flag previously-supported accessories & platforms as not (currently) supported (#86 <https://github.com/clearpathrobotics/clearpath_config/issues/86>)
  * Add initial support for flagging unsupported accessories (e.g. Kinova arms, whose binary drivers don't exist in Jazzy yet)
  * classmethod -> staticmethod
  * Use the ROS_DISTRO variable from clearpath_generator_common instead of hard-coding the distro
  * Start fixing up python linter errors, code formatting, replace % strings with f'' strings.
  * Finish first-pass replacing " -> '
  * Fix remaining linter errors. Some tests are still failing, but the major code tidying-up should be done now
  * Fix type -> _type
  * Update CI for Jazy
  * Update Python package workflow for Jazzy
  * Remove dependency on clearpath_generator_common; doing so creates a circular dependency. Instead use the system level envar
  * Add the ability to flag whole platforms as deprecated and/or unsupported
  * Docs
  * Fix imperative tone, missing periods in docstrings, missing newline at end of file
  * Mark everything besides Jackal and Husky as presently unsupported
  * Fix up sample yaml formatting. Remove unmatched quotation marks, restructure to avoid foo.bar.spam: eggs notation
  * Fix quotation marks for the sample serial number
* Add default vcan ROS interfaces based on platform
* Add support for Axis cameras (#90 <https://github.com/clearpathrobotics/clearpath_config/issues/90>)
  * Add the initial AxisCamera class with all ROS parameters defined in axis_camera's launch files & nodes
  * Remove duplicate argument
  * Add the AxisCamera class to the sensors generator
  * Add the serial to the axis camera's template
  * Add serial to the template keys too
  * Add serial getter/setter. Use empty string as default serial
  * Refactoring, set the property to the value for the template
  * frame_width -> width, frame_height -> height
  * Rename setter
  * Make the scales & offsets floats by default
  * Add the TF prefix parameter
  * Add the camera_info_url parameter
  * camera_num -> camera
  * Note that the serial isn't used, fix the name of the PTZ teleop parameter
  * Add the remaining camera topics to the Topics object
  * image_raw -> image
  * Add axis_camera sample
  * Linting fixes
  * End docstring with .
* Add ur_arm
* Add a sample for each sensor
* Add default vcan ROS interfaces based on platform
* Add support for Axis cameras (#90 <https://github.com/clearpathrobotics/clearpath_config/issues/90>)
  * Add the initial AxisCamera class with all ROS parameters defined in axis_camera's launch files & nodes
  * Remove duplicate argument
  * Add the AxisCamera class to the sensors generator
  * Add the serial to the axis camera's template
  * Add serial to the template keys too
  * Add serial getter/setter. Use empty string as default serial
  * Refactoring, set the property to the value for the template
  * frame_width -> width, frame_height -> height
  * Rename setter
  * Make the scales & offsets floats by default
  * Add the TF prefix parameter
  * Add the camera_info_url parameter
  * camera_num -> camera
  * Note that the serial isn't used, fix the name of the PTZ teleop parameter
  * Add the remaining camera topics to the Topics object
  * image_raw -> image
  * Add axis_camera sample
  * Linting fixes
  * End docstring with .
* Remove empty line at EoF
* Add header
* rx and tx topics for can bridge
* Initial can_bridges add
* Add ur_arm
* Add a sample for each sensor
* Add the ability to flag previously-supported accessories & platforms as not (currently) supported (#86 <https://github.com/clearpathrobotics/clearpath_config/issues/86>)
  * Add initial support for flagging unsupported accessories (e.g. Kinova arms, whose binary drivers don't exist in Jazzy yet)
  * classmethod -> staticmethod
  * Use the ROS_DISTRO variable from clearpath_generator_common instead of hard-coding the distro
  * Start fixing up python linter errors, code formatting, replace % strings with f'' strings.
  * Finish first-pass replacing " -> '
  * Fix remaining linter errors. Some tests are still failing, but the major code tidying-up should be done now
  * Fix type -> _type
  * Update CI for Jazy
  * Update Python package workflow for Jazzy
  * Remove dependency on clearpath_generator_common; doing so creates a circular dependency. Instead use the system level envar
  * Add the ability to flag whole platforms as deprecated and/or unsupported
  * Docs
  * Fix imperative tone, missing periods in docstrings, missing newline at end of file
  * Mark everything besides Jackal and Husky as presently unsupported
  * Fix up sample yaml formatting. Remove unmatched quotation marks, restructure to avoid foo.bar.spam: eggs notation
  * Fix quotation marks for the sample serial number
* Removed line at EOF
* Add header
* Merge pull request #82 <https://github.com/clearpathrobotics/clearpath_config/issues/82> from clearpathrobotics/lcamero/phidgets_spatial
  Add phidgets spatial to config
* Add OAKD
* rx and tx topics for can bridge
* Initial can_bridges add
* Contributors: Chris Iverach-Brereton, Luis Camero, Roni Kreinin, Tony Baltovski, Yoan Mollard

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Discord Server and ask questions in the #infra-help channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the #infra-help channel on our Discord server.

---

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks