Skip to content

Robot class to util#704

Merged
SteveMacenski merged 14 commits intomasterfrom
robot_class_to_util
Jul 19, 2019
Merged

Robot class to util#704
SteveMacenski merged 14 commits intomasterfrom
robot_class_to_util

Conversation

@SteveMacenski
Copy link
Copy Markdown
Member

@SteveMacenski SteveMacenski commented May 11, 2019


Basic Info

Info Please fill out this column
Ticket(s) this addresses #692
Primary OS tested on Ubuntu
Robotic platform tested on Simulation

Description of contribution in a few bullet points

  • Remove the robot class
  • Replace with 2 utils: VelocityPublisher to wrap the cmd_vel topics for the recoveries, tests, and DWB planner and the RobotStateHelper which currently contains helper methods for pose and odometry information about the robot.

fixes #575

Copy link
Copy Markdown
Contributor

@orduno orduno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented May 16, 2019

@mkhansen-intel do you have a preference if this is merged now or after the lifecycle updates?

Edit: memory serves that @orduno wanted to wait on this for after D release. We can do that too. I dont have a horse in this race.

@ghost
Copy link
Copy Markdown

ghost commented May 16, 2019

Fixes #575

@SteveMacenski SteveMacenski force-pushed the robot_class_to_util branch from 5be4d30 to 9aa8c97 Compare May 16, 2019 21:04
@SteveMacenski
Copy link
Copy Markdown
Member Author

This has elements folks wanted to wait until after the Dashing release, however I'd like to make sure in Dashing we have access to TF-based positioning. To do this with the utils methods I would need this PR merged so I can implement the TF positioning so that we're not using the last AMCL pose.

Thoughts?

Copy link
Copy Markdown

@bpwilcox bpwilcox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this refactor into utils. I'm in favor of getting it in soon (with implemented getTfPose) as it is relevant to refactors for collision checking in #737 and removing duplicate code

}

bool
RobotStateHelper::getTfPose(geometry_msgs::msg::PoseWithCovarianceStamped::SharedPtr & /*robot_pose*/) {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were you planning to implement this function as is done currently in Costmap2DROS? If we were to merge this before implementing, I would at least put the use_topic default as true

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didnt want to mix too much stuff into this PR since this PR is primarily a refactor. Adding new functionality I think should be done after merging. Default true is right, thanks

@ghost ghost added this to the D Turtle Release milestone Jun 10, 2019
@ghost ghost added the 2 - Medium Medium Priority label Jun 10, 2019
@bpwilcox bpwilcox force-pushed the robot_class_to_util branch from b7c4108 to 9534a7c Compare June 28, 2019 23:08
@SteveMacenski
Copy link
Copy Markdown
Member Author

@crdelsey @orduno is this still good to merge (after I fix the conflicts)?

@ghost
Copy link
Copy Markdown

ghost commented Jul 15, 2019

@SteveMacenski Yes. This is still good to merge.

@ghost ghost removed this from the D Turtle Release milestone Jul 15, 2019
@ghost ghost added this to the E Turtle Release milestone Jul 15, 2019
@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented Jul 16, 2019

@crdelsey @orduno this requires a conversation. I'm dealing with the merge conflicts and I'm seeing that you guys replaced the use of odometry in the recovery behaviors with the positioning, which is a not great thing since the positioning can and will jump based on AMCL updates without predictability. Remember that AMCL is only accurate at most to 5cm so you can be bouncing around quite alot during updates.

We use odometric position for anything that sends a control signal to the base so that we're tracking continuous non-cusping signals.

Can I get an "ok" on that to remove all use of getRobotPose() inside of the recovery behaviors and replace back with getOdometry?

Another question: why are we calling a service to get the position of the robot? This is accessible from TF much more quickly and a single instance of the TF buffer can be created in the application and a pointer added to the constructor of each recovery behavior to reduce network traffic. This is something to address in another PR but I'd like to know what the intent was.

@ghost
Copy link
Copy Markdown

ghost commented Jul 17, 2019

Can I get an "ok" on that to remove all use of getRobotPose() inside of the recovery behaviors and replace back with getOdometry?

I believe that was done to support the way the way collision detection is implemented. @bpwilcox can probably answer that question better than me. I think we want to just get the pose using TF in the long term. I'm not sure if it is safe to just replace getPose with getOdom, but we can try it.

Another question: why are we calling a service to get the position of the robot? This is accessible from TF much more quickly and a single instance of the TF buffer can be created in the application and a pointer added to the constructor of each recovery behavior to reduce network traffic. This is something to address in another PR but I'd like to know what the intent was.

It was done because we didn't have a good way of propogating the transform_tolerance parameter. Every node that needed the pose would also need a copy of theparameter, which seemed like a bigger usability problem than the service call. I agree the service call seems like overkill. I'm not sure it is in practice. We just don't have the data yet. Possibly with composed nodes and the intra_process optimization turned on, this could be a lightweight operation. @bpwilcox is working on reviving the robot package as a parameter server, so we can store common parameters there, which would address my concern about copying the transform_tolerance parameter.

@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented Jul 17, 2019

@crdelsey getting from TF can include the odometry, and that is the preferred way (really, all that topic based stuff in robot.cpp just needs to be straight up deleted, which is what I'm aiming at for my next PR after this). Recall that the transformations go map->odom->base link->base footprint. Getting the odom->base link transform is 100% promised to be continuous and locally smooth. When you add in the map->odom part that's where its deeply problematic for local control use. When an AMCL update comes along and your position jumps, the math will get wacky and since that happens asynchronously to the controller and recoveries, it does genuinely cause problems.

For reference, the transform tolerance was a parameter in nearly every package in ROS1 navigation. People didn't always use it because the defaults were pretty reasonable, but I think that's not great to add runtime overhead in exchange for a 1-time configuration (for which you could likely just neglect to include in your file if each has a reasonable default)

@bpwilcox I'd like to chat with you about that work before you spend too much time on it. I really think that the robot package in any meaningful way should just be deleted outright in the near future. Having a centralized parameter sever for common params I support, but I'm not sure that relates to the robot package as much as a general-purpose parameter server like in ROS1

@ghost
Copy link
Copy Markdown

ghost commented Jul 17, 2019

@SteveMacenski I think we are mostly in agreement on where we want to end up.

We'd like to have a parameter server for common parameters and we'd like to get the pose from TF. I'm OK with the changes you want to make.

We still want to keep a way of getting the amcl_pose, because it is the only source of our localization certainty. However, that doesn't need to reside in the robot class or even nav2_util if it doesn't make sense. Maybe it resides in nav2_amcl somewhere.

@bpwilcox
Copy link
Copy Markdown

bpwilcox commented Jul 17, 2019

Can I get an "ok" on that to remove all use of getRobotPose() inside of the recovery behaviors and replace back with getOdometry?

I believe that was done to support the way the way collision detection is implemented. @bpwilcox can probably answer that question better than me. I think we want to just get the pose using TF in the long term. I'm not sure if it is safe to just replace getPose with getOdom, but we can try it.

@SteveMacenski Right now the collision_checker grabs the robot pose via the GetRobotPose service in the local costmap frame. The intent here was to use the robot pose to unorient the oriented footprint (subscribed from topic) before again orienting it back to the requested pose (same frame) for collision checking. I changed using pose from odom to ensure the footprint used for the collision check would be oriented with a pose in the costmap's frame.

I think we'd need to resolve collision checking in recovery working with the odometry pose (whilst using costmap's frame for the check) before we make any changes.

@bpwilcox
Copy link
Copy Markdown

bpwilcox commented Jul 17, 2019

@bpwilcox I'd like to chat with you about that work before you spend too much time on it. I really think that the robot package in any meaningful way should just be deleted outright in the near future. Having a centralized parameter sever for common params I support, but I'm not sure that relates to the robot package as much as a general-purpose parameter server like in ROS1

@SteveMacenski Sure, we can chat. As of now, I see what I am working on as a "robot server", in contrast to the robot class (which will be rightfully deleted here) which is more a subscriber/client convenience class. In that vain, it would be a robot-specific parameter server and provide services to any robot-specific states such as the robot pose (until we resolve not to use this service). Thus, no other packages would need to know about or include the robot_server package.

@SteveMacenski
Copy link
Copy Markdown
Member Author

Ok @bpwilcox. Do you have a list of things that you'd want to have this server provide (not necessarily a full design doc). I'm just not 100% sure what all those things might be that would naturally be grouped together in this fashion.

@bpwilcox
Copy link
Copy Markdown

bpwilcox commented Jul 17, 2019

@SteveMacenski No design doc at the moment, but we discussed this a bit in our meeting on Monday. For now, I am only assuming the robot-specific parameters (those used in dwb, costmap, and motion primitives) that would be loaded from a specific robot's yaml file as well as the robot pose (currently being hosted as service in world_model and obtained via the tf transform in costmap_2d_ros). These robot states would be namespaced by the robot to help support multi-robot use.

We had discussed future ideas to allow user-defined services via a plugin interface and support for other robot packages entities like robot manipulation. We'd at that point consider moving the server concept outside of navigation.

@SteveMacenski
Copy link
Copy Markdown
Member Author

SteveMacenski commented Jul 19, 2019

I need to get on a call with one of you guys about this, there's enough that I perceive as wrong that there's some really massive changes I would need to make to be comfortable. Does anyone have time today to chat?

This is a super old PR and I'm just going to bite it and open tickets for the things that need fixing

@SteveMacenski SteveMacenski merged commit d076e5d into master Jul 19, 2019
@SteveMacenski SteveMacenski deleted the robot_class_to_util branch July 19, 2019 22:48
bpwilcox pushed a commit to bpwilcox/navigation2 that referenced this pull request Jul 22, 2019
bpwilcox pushed a commit that referenced this pull request Jul 22, 2019
ghost pushed a commit that referenced this pull request Aug 1, 2019
* remove nav2_robot package

* remove CMakeList and package.xml dependence on nav2_robot

* robot_util classes for publishing and states

* changing all users of robot_ to their appropriate eq.

* changing the controller to use the nav2_utils velocity publisher wrapper as well

* adding shared locks properly to share get resources

* correct namespace nav2_robot -> nav2_util

* remove sharedptr references

* resolve merge conflicts

* Setting default to use AMCL topic to true

* fix rebase/merge conflicts

deleting robot package

* removing old maintainers from navigation1

* Switch from map service to topic (#885)

* Add parameter to disable map server

* Move parameter check to getParameters

* Uncrustify

* Don't mark static layer as current until we have a map

* Make sure static layer gets initialized

Make sure static layer gets initialized, even with an empty layer, so it doesn't crash if you disable the map service and enable the obstacle layer

* remove map service from static layer

Only use map topic instead
Subscribe to map topic with default transient local volatility
Add parameter "map_subscribe_transient_local" (default=true) for backwards compatibility with volatile publishers

* Change AMCL to use only the map topic, not map service

* remove now-unused MapServiceClient

* uncrustify

* only set current_=true when first map received

* Fix nav2_costmap inflation tests.

* Fixing collision tester test.

* Revert "uncrustify"

This reverts commit 82f88a7.
This uncrustify failure is enforced differently depending on whether
we are on the dashing branch or on the master branch. This particular
commit is only appropriate on the dashing branch, but is already present
there.

* change primitives to recoveries (#705)

* change primitives to recoveries

* changing all over new bringups with nav2_recoveries

* renaming primitive_name -> recovery_name

* stop robot on cancel in recovery

* fixed recovery node halt bug

* removing nav2_robot package

* adding lifecycle publisher for dwb

* Removing unneeded tf initialization calls

* Remove dedicated thread from costmap

* Add support for new createTimerInterface API

* Fix system test launch file.

* updated the build scripts for ROS2 Dashing (#924)

* run build from anywhere in tree

* renaming dependencies because its driving me up a wall autocomplete for nav doesnt work

* remove extra files re-introduced in PR #704

* set align critics scale to 0 (#936)

* fix typo in build tool updates

* Nav2-rviz-plugin changes. (#937)

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

* fix linter failures in Rviz plugin (#979)

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Fixing typo in dependencies (#982)

* Fixing typo in dependencies

* Also remove some duplicate dependencies

* Fixing robot_state_publisher dependency

* Add support to change the local controller rate. (#970)

* Add back parameter to configure DWA rate

* Report out if we missed our control loop time.

* Fix the dashing build on OSRF build farm. (#935)

All our builds have boost installed due to other dependencies, so
we've never run into this. The build farm must build with all other
dependencies removed somehow.

* bump for release to 0.2.2

* Fix for TEB local planner buildable (#981)

Signed-off-by: vinnamkim <vinnam.kim@gmail.com>
ghost pushed a commit that referenced this pull request Sep 9, 2019
* remove nav2_robot package

* remove CMakeList and package.xml dependence on nav2_robot

* robot_util classes for publishing and states

* changing all users of robot_ to their appropriate eq.

* changing the controller to use the nav2_utils velocity publisher wrapper as well

* adding shared locks properly to share get resources

* correct namespace nav2_robot -> nav2_util

* remove sharedptr references

* resolve merge conflicts

* Setting default to use AMCL topic to true

* fix rebase/merge conflicts

deleting robot package

* removing old maintainers from navigation1

* Switch from map service to topic (#885)

* Add parameter to disable map server

* Move parameter check to getParameters

* Uncrustify

* Don't mark static layer as current until we have a map

* Make sure static layer gets initialized

Make sure static layer gets initialized, even with an empty layer, so it doesn't crash if you disable the map service and enable the obstacle layer

* remove map service from static layer

Only use map topic instead
Subscribe to map topic with default transient local volatility
Add parameter "map_subscribe_transient_local" (default=true) for backwards compatibility with volatile publishers

* Change AMCL to use only the map topic, not map service

* remove now-unused MapServiceClient

* uncrustify

* only set current_=true when first map received

* Fix nav2_costmap inflation tests.

* Fixing collision tester test.

* Revert "uncrustify"

This reverts commit 82f88a7.
This uncrustify failure is enforced differently depending on whether
we are on the dashing branch or on the master branch. This particular
commit is only appropriate on the dashing branch, but is already present
there.

* change primitives to recoveries (#705)

* change primitives to recoveries

* changing all over new bringups with nav2_recoveries

* renaming primitive_name -> recovery_name

* stop robot on cancel in recovery

* fixed recovery node halt bug

* removing nav2_robot package

* adding lifecycle publisher for dwb

* Removing unneeded tf initialization calls

* Remove dedicated thread from costmap

* Add support for new createTimerInterface API

* Fix system test launch file.

* updated the build scripts for ROS2 Dashing (#924)

* run build from anywhere in tree

* renaming dependencies because its driving me up a wall autocomplete for nav doesnt work

* remove extra files re-introduced in PR #704

* set align critics scale to 0 (#936)

* fix typo in build tool updates

* Nav2-rviz-plugin changes. (#937)

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

* fix linter failures in Rviz plugin (#979)

* I added a timeout to spin_until_future_complete, so rviz doesn't get frozen if something goes wrong in the navigation stack. I did some changes in the start navigation; - changed the funtion type to boolean - added returns to the funtion, so it will return false if something goes wrong. I changed goal_tool added a if statement to check if start_navigation doesn't return false before calling any other functions in goal_tool

* made the code cleaner and changed the error messages. Reduced the timeout value to 3 seconds. The timeouts will be parametrized in the future.

* added timeout parameter

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Update navigation_dialog.cpp

* Update navigation_dialog.hpp

* Fixing typo in dependencies (#982)

* Fixing typo in dependencies

* Also remove some duplicate dependencies

* Fixing robot_state_publisher dependency

* Add support to change the local controller rate. (#970)

* Add back parameter to configure DWA rate

* Report out if we missed our control loop time.

* Fix the dashing build on OSRF build farm. (#935)

All our builds have boost installed due to other dependencies, so
we've never run into this. The build farm must build with all other
dependencies removed somehow.

* bump for release to 0.2.2

* Fix for TEB local planner buildable (#981)

Signed-off-by: vinnamkim <vinnam.kim@gmail.com>

* adding rate loops where applicable (#743)

* adding rate loops where applicable

* throttle while loops with sleep_for

* sleep_dir -> sleep_dur

* enabling closed-loop control in spin (#983)

* implemented controlled spin

* remove files reintroduced (#991)

* collision checkers in recoveries now look sufficiently far ahead in the local coordinate frame

* removing whitespace

* revert to global: need PR for TF positioning merged before can fix that

* Creating a simple action server to be able to invoke Random Crawl from BT (#945)

added random crawl action to bt

* amcl particlecloud is best effort (#1003)

Signed-off-by: Mikael Arguedas <mikael.arguedas@gmail.com>

* Disable displaying RobotModel in Rviz by default (#1001)

* returning failed if recovery cannot be completed due to collision

* backing out collision detection into a new fuction

* removing extraneous visualization from tests that have been removed

* revert my own config

* make ye old linter happy

* Footprint subscriber const topic

Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>

* Costmap subscriber const topic

Signed-off-by: Shane Loretz <sloretz@osrfoundation.org>

* fixing PR feedback to stopRobot() in better location and parameterization

* removing unnecessary smart pointers that dont effect lifecycle

* lifecycle executor doesnt need to be a pointer

* removing extra PR template field in application no one uses

* Reorganize some of the BehaviorTree-related code (#957)

* Reorganize some of the BehaviorTree-related code.

Eliminate the NavigateToPoseBehaviorTree class, merging it with the BehaviorTreeEngine.
Put clear_entirely service client with the others in nav2_util.
Move RecoveryNode to nav2_behavior_tree with the other BT nodes.

* Remove method signature that isn't implemented yet

* Add a missing dependency

* Address a couple linter issues

* Tf based positioning (#993)

* remove topic based positioning for TF and removing extraneous build fields

* robot utils complete for getting positioning from TF

* readding the custom logger for getting current pose

* remove extra TODO

* fixing fun crustyness

* pass by ref not shared ptr

* wrapping costmap 2d's get pose with util

* revert costmap 2d plugin initialization swap

* fixing more uncrustified issues while I wait

* adding transform listener to buffers

* adding tf listeners and missing dependencies

* editing test cases

* trying no exception

* first stab at unit tests with TF2 for costmap 2D integration test

* adding the create timer interface

* adding updated pose info for testing

* com'n crusty code, why are you different in CI?

* fixing merge conflicts p2

* remove unnecessary CMake code to remove warning (#1005)

Signed-off-by: Mikael Arguedas <mikael.arguedas@gmail.com>

* disabling by default the debug markers for local planner (#1007)

* adding deprecation warning for topic-based goal navigation

* fixing spin recovery

* incorrect topic names

* Provide correct path to default map (#987)

* Extend the costmap's namespace with the hosting node's namespace (#999)

* Parameter dumping utility (#902)

* Add a parameter dumping utility to nav2_utils

* Add some convenience functions to simplify declaring parameters

* Add some examples for AMCL

* Remove stray example file

* Default to dumping all nodes; throw/catch exceptions

* Address some review feedback

* Fix node name collisions (#1020)

* Fix node name collisions

Make sure service clients have a unique node name (this was a problem in recoveries nodes)
Delimit ros arguments with new `--ros-args`,`--`

* Uncrustify

* Fixing linter failures introduced in master (#1029)

* Fixing linter failures introduced in master

* Sort of fix test_occ_grid_cpp test but disable since it's flaky

* Disable failing test_collision_checker test

* Recovery using odometric poses and costmaps (#1023)

* recovery behaviors using the odometric positioning for pose estimation

* use local costmap information in recoveries

* fixing costmap namespacing for collision detector

* odometry based recoveries with collision checker global frame model

* on download, rosdep all necessary items, calling on each build is redundant

* doing rosdep install in a single call

* removing extraneous cd

* adding recoveries XML to simulation launch file (#1031)

* adding recoveries XML to simulation launch file

* fix typo from name vs frame odom

* refactor goal handle into panel

clean up

remove extra log info

* remove nav2 goal tool and address review feedback

* fix lint issue

* send pose via qt signal through goal tool

* remove navigation dialog

minor clean up

* use enum for action states

fix compile issues

remove extra semicolons

fix uncrustify

* add QBasicTimer

cleanup timer

* remove more unnecessary headers

* Add parallel testing jobs for each rmw vendor

* Fix yaml

* Fix yaml

* Use custom version of nightly instead

* Extend workflow for rmw testing on release

* Fix typo

* Try speeding up build by omitting job limit

* Ensure checksum.txt exist for restoring cache

* Set --load-average +1 from -j
For a 2CPU/4096MB CI resource

* Reorganized executor and add caching nonce

Improve env DRY'ness by using separate executors

Enable debug builds

Add nonce to caching to help avoid caching key collisions
between debug and release workflow paths

* Fix awk to print env to checksum

* Add .dockerhub build hooks
and add FROM_IMAGE to arguments

* Switch to custom docker repo

* Use symlinks to place Dockerfile with hooks
Tweak build hook to compensate for dockhub assumptions
DockerHub repo build rules:

source: master
tag: master
Dockerfile: /.dockerhub/nightly/Dockerfile

source: master
tag: master-rmw
Dockerfile: /.dockerhub/nightly-rmw/Dockerfile

source: /^.*-devel$
tag: {sourceref}
Dockerfile: /.dockerhub/devel/Dockerfile

* Have CI Dockerfile use ccache

* Add .dockerignore to avoid braking build cache
So tweaking unrelated files doesn't invalidate:
COPY ./ navigation2/

* Word wrap long command

* Combine ccache with Circle CI caching

* Correct terms for underlay and overlay
upstream -> underlay
navigation2,build,source -> overlay

* Change setup_underlay to setup_dependencies

* Share ccache across overlay and underlay

* Correct typo

* Add new line

* Always save ccache
avoid unnecessary checking step

* Hack to avoid breaking docker build cache
for COPY when changing Dockerfile itself.
This shouldn't be needed,
but does not seem to work without **
¯\_(ツ)_/¯

* Add adjustable build failure behavior
When FAIL_ON_BUILD_FAILURE is unset
failures from colcon build will be supressed
allowing for docker build to succeed.
This prevents DockerHub CI images from becoming stale
when branch build brakes, previously blocking DockerHub CI image builds.

* Enable nightly release tests
now that docker CI builds unset FAIL_ON_BUILD_FAILURE
thus its status is less indicative of master build breaking

* Avoid cache collisions for PRs with same branch name
by including unique PR number into cache key

CircleCI branch name substitution using {{ .Branch }}
does not prefix names with the repo name.
Thus PRs from separate forks using the same branch name could collide.

https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables
https://circleci.com/docs/2.0/configuration-reference/#save_cache

* Do not share underlay cache across branchs/PRs

* Abridge lengthening cache key names

* Account for failed underlay builds
if we don't happen to clean the underlay
when we keep the underlay from the docker image

Copy logic to overlay for consistency in behavior

* Add epoch to cache key given caches are immutable
and use spaceless string concatenation in yaml
to split long key names into multiple lines.

Given the immutability of caches,
and that cache key matching is prefix based,
{{ epoch }} must be the last part of the cache-save key.

https://discuss.circleci.com/t/add-mechanism-to-update-existing-cache-key/9014/13
https://circleci.com/docs/2.0/caching/#restoring-cache
https://circleci.com/docs/2.0/configuration-reference/#save_cache
https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-over-multiple-lines/21699210#comment65667554_21699210

* Clean workspace incase build_failed

* Improve underlay build cache
By only copying .repo file for vcs import of underlay
and move overlay copy just before rosdep install for overlay

* Remove duplicate copy of overlay .repos file
given the dockerfile now copies this directly into the overlay wrokspace

* Rename workspaces to underlay and overlay
To complete the standardization of terminology
ros_ws -> underlay_ws
nav2_ws -> overlay_ws

* Add on_checkout anchor
to make config more DRY

* Target nonfree tag to include connext

* Add ccache stats command
to print and zero ccache statistics
as well as ccache version and config

after restore of ccache cache
and after each underlay/overlay build

* Cleanup code coverage pipline
Use offical Codecov orb for uploading
make the coverage script more DRY

* Remove unnecessary indents

* Split debuild build and test
and make release tests more DRY

* Shorten config

* Print out lcov command when runing script

* Use  to avoid infinite recursion

* Add common_environment refrence
and make jobs more DRY

* Store ccache logs for CI debugging

* Simplify code coverage script
to prevent untented shell glob expansion

* Rename fields

* Store test result

* Copy test results into expected directory structure
See directory structure example in
https://circleci.com/docs/2.0/configuration-reference/#store_test_results

* Store test artifacts for debug uploaded results

* Support parallel testing

* Fix xargs line splitting

* Run colcon test-results to fail on test errors
Needed to use return status from test-results

* Lookup historical timing data by classname for split-by
E.g. "costmap_queue.CostmapQueue" in `costmap_queue/utest.gtest.xml` :

<testsuites tests="5" failures="0" disabled="0" errors="0" timestamp="2019-08-12T06:57:26" time="0.499" name="AllTests">
<script/>
<testsuite name="CostmapQueue" tests="5" failures="0" disabled="0" errors="0" time="0.499">
<testcase name="basicQueue" status="run" time="0" classname="costmap_queue.CostmapQueue"/>
<testcase name="bigTest" status="run" time="0.496" classname="costmap_queue.CostmapQueue"/>
<testcase name="linearQueue" status="run" time="0" classname="costmap_queue.CostmapQueue"/>
<testcase name="crossQueue" status="run" time="0.001" classname="costmap_queue.CostmapQueue"/>
<testcase name="limitedQueue" status="run" time="0.002" classname="costmap_queue.CostmapQueue"/>
</testsuite>
</testsuites>

* Show split count and omit unneeded xargs

* Simplify build using colcon mixins
and add build args for underlay and overlay mixins

* Override mixing in build hook

* Rename build hooks and tags

* Build overlay with same settings to maximize ccache hit rate

* Correct mixin typo

* Make checksum.txt more informative
by piping message into directly into file for debugging
and simplify digests inclusion for spotting hash diffs

* Fixing up paths for codecov.io report (#1036)

* Update .dockerignore

Co-Authored-By: Carl Delsey <carl.r.delsey@intel.com>

* Move rwm jobs back into nightly workflow

* Set genhtml as default and add case for ci

* Refactor config using commands

* Use paths instead of env

* Revert ccache anchor name

* Fix install linking

* Avoid using paths as keys
prefix matching fails when key includes slashes

* Rename yaml anchor

* Make sure lcov is installed for CI

* Fix the build due to access specifiers (#1040)

No idea why this builds under GCC but these changes were needed to build under clang.

* Mark timerEvent override (#1037)

* Add dummy Dockerfiles for setting repository links on Docker Hub

* Set exit and print trace in script

* Tweek tag names

* nav2_util::duration_from_seconds -> rclcpp::Duration::from_seconds (#1048)

* nav2_util::duration_from_seconds -> rclcpp::Duration::from_seconds

* Update nav2_costmap_2d/plugins/static_layer.cpp

oops!

Co-Authored-By: Carl Delsey <carl.r.delsey@intel.com>

* Rewrite nav2_map_server (#989)

Add GraphicsMagick API and use it to implement map_saver, map_loader
Removes dependency on SDL, creates installation dependency on libgraphicsmagick++; apt package libgraphicsmagick++1-dev
Allows saving in trinary, raw, or scale mode.
Added configurable image format pgm, png, etc.
Add warning when using scale mode with opaque format.
Remove SDL from map server
Extract repeated MapMode to shared enum class
Switch writing YAML to same library that reads it (yaml-cpp)
Add --help alias to map saver -h
Extract map yaml loading to its own function, with better error messages. Also fixed crash due to misuse of std::string constructor.

* Migrate image tag to rosplanning repo

* Enable AMCL to initialize at the origin, under control of a parameter

* Make sure everything shuts down cleanly

* Some cleanup and linting

* Address review feedback

* Also have to update the YAML file

* Remove the connection object for now. Needs further investigation

* Find all uses of yaw to quaternion and use new function

* Simplify a quaternion copy

* Restore COLCON_IGNORE file

* Oops. Missed a package dependency

* Fixing a rebase error

* Add missing dependencies to system tests (#1059)

Signed-off-by: Louise Poubel <louise@openrobotics.org>

* add tf2_geometry_msgs dependency

* Fix the updown test. (#1061)

* Fixing linter errors, accidentally commited.

* Export envs for arg in build hook

* Remove the setSimTime() method - not needed anymore

* Remove ros2param package dependency

* Fix indentation (#1065)

* BT Service node & implementations (#1055)

* generic ros service caller BT node

* BT specialty service callers using BT node service

* rename to reinitialize global localization

* uncrustify/lint

* changes per PR requests

* changing pose topics to goal_pose

* Removing deprecation warning

* Removing an accidentally re-introduced file

* use seconds in Duration

* Enable global planner tester (#927)

* use duration from seconds

* Add ctest loop script to system tests

* Set line buffering to 1 in system test launch

* Update README

* Update README for using ctest_loop script

* Recombine AMCL library components with AMCL to have consistent license (#1074)

* Move AMCL library files back to nav2_amcl package

* Fixing up naming so things compile again

* Transition copyright disable check to follow eig3 files.

* Transition amcl files license to LGPL 2.1

* Adding missing copyright headers to nav2_bringup package

* Adding missing copyright headers to nav2_common

* Fixing up include guard to match coding style

* Reformatting license to pass the copyright check

The change here is only whitespace changes - line length and paragraph
spacing, as well as the addition of the license title

* Relicensing file to better match the existing package

* Fixing readme to account for the new change

* Begin updating nav2_behavior_tree README

* Continue update of nav2_behavior_tree readme

* Add link to behavior tree basic nodes to README

Adding a link to the upstream documentation on behaviortree.dev

* Clarify Licensing throughout the repo (#1080)

* Add proper SPDX license IDs and repo LICENSE file

* Fixing a minor linter typo

* Use python yaml safe loader (#1085)

* Null-terminate string to dirname function (#1093)

possibly responsible for heisenbug #1079 (comment)

* Update to latest v2 BT Library (#1088)

* Revert CreateTimer change

* Revert "nav2_util::duration_from_seconds -> rclcpp::Duration::from_seconds (#1048)"

This reverts commit 7c473cd.

* Fix dependency exports

* Fixing missing boost dependency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2 - Medium Medium Priority

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove stop motion primitive, make a method on the robot class

3 participants