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

Sim launch position arg #43

Merged
merged 14 commits into from
Feb 26, 2024
Merged

Sim launch position arg #43

merged 14 commits into from
Feb 26, 2024

Conversation

PatXue
Copy link
Collaborator

@PatXue PatXue commented Feb 19, 2024

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Changed arguments in single and 2 buggy simulator launch files to allow user to start buggy(s) from any distance along the planned trajectory by passing in command line arguments.

QA Instructions, Screenshots, Recordings

Tested single buggy sim on both Gabe's and my computer, and appears to behave as expected. Tested double buggy sim on my computer, and also seems to work as expected.

PatXue and others added 11 commits February 17, 2024 17:47
Code still not tested, could not figure out how to import world and trajectory into engine.py
Ideally would figure out how to not have to do this and just import them directly from auton directory
Rather than dealing with the two different Pose classes (from pose.py and rospy), just do the conversion directly in engine.oy
The sim now seems to start the buggy at the correct place, but auton doesn't seem to take it well and causes buggy to steer in very tight circles (buggy appears static on map)
@PatXue PatXue requested review from Jackack and christianvluu and removed request for Jackack February 19, 2024 04:13
@christianvluu
Copy link
Collaborator

I was imagining we have certain "keypoints/checkpoints" around the course where the buggies could start, instead of inputting a distance.

Perhaps there's a different option upon launching that could allow you to specify the start location down to the particular coordinate/distance along the path, but in general, we're only going to be starting the simulation at a few positions right? @Jackack

@Jackack
Copy link
Collaborator

Jackack commented Feb 19, 2024

The idea is to use distance to specify the key points

Copy link
Collaborator

@Jackack Jackack left a comment

Choose a reason for hiding this comment

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

In engine.py, can you add the ability to pass starting position as a utm cooridnate as well?

@christianvluu
Copy link
Collaborator

Yeah, was gonna ask what if we want to start slightly off from the path.

Copy link
Collaborator

@christianvluu christianvluu left a comment

Choose a reason for hiding this comment

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

Also please update documentation as appropriate.

@Jackack
Copy link
Collaborator

Jackack commented Feb 19, 2024

I requested a change to add raw coordinates as well, if that's what auto testing wants. There's also already a dictionary of key points in engine.py. It's commented out by this commit but we should keep that feature too.

Copy link
Collaborator

@Jackack Jackack left a comment

Choose a reason for hiding this comment

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

In engine.py, can you keep the starting_poses dictionary, and add the ability to use either distance or a key into the starting_poses dict?

Uses start_pos arg as dict key if valid key, and as distance otherwise
@PatXue PatXue requested a review from Jackack February 19, 2024 23:07
@PatXue
Copy link
Collaborator Author

PatXue commented Feb 19, 2024

Added back in ability to use start_pos argument as a dictionary key for starting_poses, will work later on inputting utm coords

@Jackack Jackack merged commit a5c1201 into main Feb 26, 2024
3 checks passed
@Jackack Jackack deleted the sim-launch-position-arg branch February 26, 2024 22:07
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.

None yet

4 participants