This ensures that any motion between construction and first update will be ignored (this is usually the period between init and start of an op mode). If teams want to track pose during that period, they can call `updatePoseEstimate()` explicitly. This matches the behavior of the 0.5.x localizers (without the annoying reset on every pose estimate set). The localizers also now log much more data to help troubleshoot localization issues in the future.
39 lines
1.1 KiB
Groovy
39 lines
1.1 KiB
Groovy
//
|
|
// build.gradle in TeamCode
|
|
//
|
|
// Most of the definitions for building your module reside in a common, shared
|
|
// file 'build.common.gradle'. Being factored in this way makes it easier to
|
|
// integrate updates to the FTC into your code. If you really need to customize
|
|
// the build definitions, you can place those customizations in this file, but
|
|
// please think carefully as to whether such customizations are really necessary
|
|
// before doing so.
|
|
|
|
|
|
// Custom definitions may go here
|
|
|
|
// Include common definitions from above.
|
|
apply from: '../build.common.gradle'
|
|
apply from: '../build.dependencies.gradle'
|
|
|
|
android {
|
|
namespace = 'org.firstinspires.ftc.teamcode'
|
|
|
|
packagingOptions {
|
|
jniLibs.useLegacyPackaging true
|
|
}
|
|
}
|
|
|
|
repositories {
|
|
maven {
|
|
url = 'https://maven.brott.dev/'
|
|
}
|
|
}
|
|
|
|
dependencies {
|
|
implementation project(':FtcRobotController')
|
|
annotationProcessor files('lib/OpModeAnnotationProcessor.jar')
|
|
|
|
implementation "com.acmerobotics.roadrunner:ftc:0.1.13"
|
|
implementation "com.acmerobotics.dashboard:dashboard:0.4.14"
|
|
}
|