Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add ros env vars to source script #2288

Merged
merged 1 commit into from
Oct 6, 2024
Merged

add ros env vars to source script #2288

merged 1 commit into from
Oct 6, 2024

Conversation

sid-parikh
Copy link
Contributor

Description

ROS2 enviornment was messed up -- ros2 topic list would not result in anything in a new terminal. I identified that ros expects certain env vars to be the same in all shells that are talking about the "same" ros processes

Associated / Resolved Issue

Resolves ClickUp card

Steps to Test

Test Case 1

  1. Ideally on a fresh install
  2. make run-sim in one terminal
  3. source && ros2 topic list in another terminal

Expected result: you see all the topics

Key Files to Review

  • env.sh has the new envs
  • do you like where I put the source command? (source.bash)

Questions

  • should we think about our naming convention with .zsh .bash etc?
  • source.bash is pretty shell-agnostic

Review Checklist

  • Docstrings: All methods and classes should have the file appropriate docstrings which follow the guidelines in the "Contributing" page of our docs.
  • Remove extra print statements: Any print statements used for debugging should be removed
  • Tag reviewers: Tag some people for review and ping them on Slack

Copy link
Contributor

@shourikb shourikb left a comment

Choose a reason for hiding this comment

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

Switching to this branch worked for making all the topics show up when you run ros2 topic list after sourcing.

@jacksherling jacksherling merged commit b6dcfc1 into ros2 Oct 6, 2024
2 checks passed
@jacksherling jacksherling deleted the sp/fix-ros2-env branch October 6, 2024 23:00
piman51277 pushed a commit that referenced this pull request Oct 6, 2024
Squid5678 pushed a commit that referenced this pull request Oct 28, 2024
shourikb pushed a commit that referenced this pull request Oct 30, 2024
jacksherling added a commit that referenced this pull request Nov 6, 2024
* Created a new motion planner called rotation planner. It is a work in progress. This planner should theoretically only be rotation around a point (in our case, we are developing it to rotate about itself).

* tested some theory about the problem. With changing the values in points, we have pinpointed the likely problem. If the two rotation points are the current pivot point and the point (0, 0), it will rotate but also translate. If the only points in the rotation are the pivot point, it will try to plan but get stuck. This is because we try to move to the same point that we are already at, so we think it is done because planners check they are done by translation. However, we need to make this one check it is done by its orientation.

* trapezoid angle planning

* end 09/08

* updated files

* Dribble in Sim (#2287)

* dribbler is stupid

* use realism

* add realism to simoulator cli run

---------

Co-authored-by: petergarud <[email protected]>

* add ros env vars to source script (#2288)

* Update tutorial.rst (#2286)

* fixed rebase issues

* Fix Code Style On rotate-kick (#2300)

automated style fixes

Co-authored-by: Squid5678 <[email protected]>

* changes

* Fix Code Style On rotate-kick (#2303)

automated style fixes

Co-authored-by: Squid5678 <[email protected]>

* change to is angle done threshold

* removing SPDLOG stuff

* removed unnecessary line pivot changes

* gitignore

* remove log stuff

* comments

---------

Co-authored-by: Shourik Banerjee <[email protected]>
Co-authored-by: rishiso <[email protected]>
Co-authored-by: Sanat Dhanyamraju <[email protected]>
Co-authored-by: petergarud <[email protected]>
Co-authored-by: Sid Parikh <[email protected]>
Co-authored-by: Jack <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Squid5678 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants