The autonomous op mode.

Autonomous op mode to use in case the robot cannot determine its position on the crater side.

Autonomous op mode to use in case the robot cannot determine its position on the depot side.

Autonomous op mode to use in case the normal one completely borks.

Autonomous op mode to use in case there is a chance of collision with the other team's robot.

This file contains an example of an iterative (Non-Linear) "OpMode". An OpMode is a 'program' that runs in either the autonomous or the teleop period of an FTC match. The names of OpModes appear on the menu of the FTC Driver Station. When an selection is made from the menu, the corresponding OpMode class is instantiated on the Robot Controller and executed. This particular OpMode just executes a basic Tank Drive Teleop for a two wheeled robot It includes all the skeletal structure that all iterative OpModes contain. Use Android Studios to Copy this Class, and Paste it into your team's code folder with a new name. Remove or comment out the @Disabled line to add this opmode to the Driver Station OpMode list

Public interface representing the set of methods every single drive system is guaranteed to implement. For example, both a regular two wheel drive and a mecanum drive implement these same methods. This makes it useful for creating op modes that work for both systems.

Throughout DriveMotors and its subclasses, you will find methods referring to two similar yet distinct concepts: power and speed. Power refers to driving a motor by sending a given amount of power to it. Speed refers to intelligently controlling a motor by constantly making adjustments to power so that the motor moves in a consistent manner. Power does not require an encoder; speed does.

You do not construct DriveMotors directly; instead, you use one of its subclasses.

Extake comprised of an elevator that extends and retracts a rotatable bin.

Tests REV Core Hex Motor on LinearMotion Extender

Intake comprised of an elevator that extends and retracts a rotatable bin and roller.

A bare-bones iterative op mode in Java. Runs by repeatedly calling loop over and over again. Good for Tele-Op op modes.

A bare-bones iterative op mode. Runs by repeatedly calling loop over and over again. Good for Tele-Op op modes.

A bare-bones linear op mode in Java. Runs by calling a method once and is slightly simpler to implement than an iterative op mode. Good for Autonomous op modes.

A bare-bones linear op mode. Runs by calling a method once and is slightly simpler to implement than an iterative op mode. Good for Autonomous op modes.

Interface representing the set of methods every extake is guaranteed to implement. It is currently empty.

Interface representing a factory that creates a standard Hardware instance. Most hardware classes will have companion objects implementing this interface.

Public interface representing the set of methods every single gyro sensor is guaranteed to implement. This makes it useful for creating op modes that work for any gyro sensors other than the IMUGyro.

A Gyro instance that uses the REV Robotic Expansion's built-in gyro sensor (IMU) to obtain measurements.

Interface representing the set of methods every intake is guaranteed to implement. It is currently empty.

Tests REV Core Hex Motor on both OldIntake Extender and LinearMotion

Tests REV Core Hex Motor on Intake Roller

Tests REV Core Hex Motor on OldIntake Roller

A linear motion system driven by a DcMotor.

Class representing four DcMotors that comprise a Mecanum drive; in other words, the drive we're using on our robot.

Wrapper class for Vuforia and TFOD. Improves code reusability. Unlike most other classes, you usually do not call standard; instead, you use its constructor.

This 2018-2019 OpMode illustrates the basics of using the TensorFlow Object Detection API to determine the position of the gold and silver minerals. Use Android Studio to Copy this Class, and Paste it into your team's code folder with a new name. Remove or comment out the @Disabled line to add this opmode to the Driver Station OpMode list. IMPORTANT: In order to use this OpMode, you need to obtain your own Vuforia license key as is explained below.

This helper class was intended to assist in the creation of mineral knocking op modes. Since every use case is different, this class has been deprecated. See MineralKnockerOpMode for an example of how it was used. Do not use this class.

Tests REV Core Hex Motor on Intake Roller

Class representing a simple, run-of-the-mill two wheel drive. We used to use this; now we are not.

This was one of the earliest classes made this year; I apologize in advance for the poor coding in this class.

This class takes care of all your vision needs. Wrapper class for Vuforia that extends MineralDetection. Improves code reusability.

IMPORTANT: Use of the Vision class requires a Vuforia auth key. To learn how to set one up, browse to the VuforiaAuthKey class.

Helper class for retrieving the Vuforia authentication key used to power MineralDetection and Vision. This class is automatically called by MineralDetection and Vision.

For security reasons, we do not include the Vuforia auth key in the repository. As such, you will have to add one yourself.

Browse to TeamCode/src/main/res/raw, and make a new file called "vuforiaauthkey.txt". Paste your Vuforia authentication key into there.

TITANIUM KNIGHTS MEMBERS: To get the authentication key, contact Anthony Li or Edward Li.