[kuhfzgbt]

Hey, I'm the developer of BuildAnAuton.

Right now, the user has to configure the encoder through getDistancePerPulse() and the program simply uses the getDistance() method. Thanks to your suggestion though, I'll probably implement something that asks for gearbox ratio and wheel size to automatically calibrate the encoder. However, from experience, I've found that that calculation is usually off by a little bit, and requires some fine tuning, so the user will still need to do some of that work. For torque curve, encoder and gyro sensitivity I don't think those would factor into how the program currently works.

Moment of inertia and turning scrub shouldn't be a factor. In fact, I've already tested the program on other robots, and it has worked fine.

The programs are exported as a separate file type that is uploaded to the robot via FTP. And yes, it can be integrated into other programs; it gives up control for teleop, and the program is run by a few line of code in your robot code that you can be creative with.