Scripted Autonomous Functionality

[jkleiber]

Summary
In preparation for the 2023 season, we should up our autonomous game. The biggest improvement we can make is by not using hard-coded autonomous C++ files, but rather load dynamically from a script.

In the past I've seen this done via CSV or JSON, but I'd like to try this in TOML using arrays of tables.

Work to Do

• Define autonomous folder structure
• Define autonomous schema based on last year's scheme
• Implement autonomous chooser based on available TOML files
• Dynamically load command lists via TOML tables
• Make unit tests to verify this works

Verification

• CI passes with new unit testing (this probably is blocked by Make parameter loading work in CI #13 )

[danielbrownmsm]

How do you make the step from "command written in TOML" to "actual autonomous code"? Or would the auto just look like some kind of:

public Auto() {
    ArrayList<Command> commandList = new ArrayList<>();
    for command in commands:
        if command.type == SetShooterCommand:
            commandList.append(new SetShooterCommand(*command.args)
        elif command.type == DriveForwardCommand:
            commandList.append(new DriveForwardCommand(*command.args)
    super(commandList);
}

?

[jkleiber]

Yeah, so it would probably be something like what you're describing. The TOML side would pass in command type, parameters, and time. Then we'd need to schedule these commands in AutonomousPeriodic based on time elapsed in auto