From a G4 perspective, why don’t you implement your own for competitions? There are many resources for figuring it out.
Teams are expected to be able to write their own code and libraries. Why outsource?
LemLib has been working great this season, and I encountered quite an interesting issue.
I had to make a duplicate Pros Imu class with a scalar to feed Lemlib corrected Imu measurements. This was to account for a very consistent undershoot in the imu measurements. After a few rotations, the IMU would be out by 5-10 degrees.
Also working with the Motion-View guy to get seamless support would be awesome. Motion view looks like a really good project to augment and level up what you can get out of Lemlib.
I must of missed something, you don’t mean path.jerryio?
I don’t know if this is possible (or a good idea), but currently one thing I’ve noticed is that the docs’ configuration pretty much just says, “Put your motor port number here, and copy paste this in.”
This isn’t necessarily a bad thing, it makes it really easy to use, but I think it also encourages this thought process of “copy paste, no need to learn”. I don’t really know HOW you’d implement this in a way that it’s easy for experienced people to reference but also helps a beginner learn, but what about adding more, “how it works” into the documentation? Once again, I don’t know if this is a good idea, but it would definitely help people understand the library better.
If LemLib is ok with it, I’d be happy to port over my existing MVLib and modify it to fit seamlessly with LemLib. If it were up to me, the syntax would likely by chassis.logger.foo(); or something similar.