Did you use Pathweaver to generate auto trajectories this past year?

Technical Programming
1

Last year my team implemented some autonomous paths with pathweaver for the first time ever.

We originally had to import the field image into pathweaver, and I’m convinced our paths were not correct with it. It seemed as if the scale was not completely correct.

I’m curious how it went for other teams? Did you use pathweaver? Did you paths by hand? How did you control speed throughout these trajectories? How accurate was your driving?

1 Like
2

You had to import the field image when? The kickoff release code can never have the field image (cause it would be a spoiler) but the very first update after that had the field image automatically.

Without knowing more about what you did it is hard to comment on the scale being off. If you go to PathWeaver now and create a new project you get the field image without importing right?

There is nothing special or fancy about what we do to import the field image and it is all documented here.

3

Ah gotcha.

Within pathweaver is there anyway to control the speed between the individual points?

4

I know this isn’t exactly what you asked, but we used pathplanner and had a lot of success with it.

1 Like
5

https://github.com/mjansen4857/pathplanner ?
This project?

1 Like
6

Yes

7

My team switched to PathPlanner in the offseason because it supports swerve drive, but we used pathweaver and RAMSETE with great success in the main season with our tank drive.

1 Like
8

Thanks all for the suggestions. Just spent some time this morning with PathPlanner and loved it

1 Like
9

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.