AscendRobotics/AscendData · Datasets at Hugging Face

text stringlengths 0 715
Flywheel.spin(forward); //just an example
wait(25, msec);
}
return 0; //C++ technicality
}
Tasks can be created with this line of code, and will not run until they have been created. The variable spinFlywheel stores the task internally for future reference.
task spinFlywheel = task(myTask);
If you want the task to stop running, call the stop() function on it:
spinFlywheel.stop();
We recommend using tasks for controlling lifts, catapults, or flywheels when the control algorithm required is non-trivial.
Advanced Drive Code
A more intuitive driving experience
While the basic split arcade drive does work, we'll show you a small addition to the code that can make the driving experience more intuitive. This code simply adjusts the turns to be more intense when the robot is going faster.
void driveCode() {
//drives the robot around based on controller input, double arcade controls
//First, get controller inputs
int straight = Controller1.Axis3.value(); //gives a number -100 to 100
int turn = Controller1.Axis1.value();
//adjust the turn variable based on the straight one
if (forward1 > 50) {
turn *= (((forward1 - 50) / 50) + 1);
} else if (forward1 < -50) {
turn *= (((-50 - forward1) / 50) + 1);
}
//Calculate proper motor powers
int left = straight + turn * 0.7; //the 0.7 makes the turns less intense
int right = straight - turn * 0.7;

//Spin the drive motors at the calculated velocity
Left1.spin(forward, left, percent);
Left2.spin(forward, left, percent);
Left3.spin(forward, left, percent);
Right1.spin(forward, right, percent);
Right2.spin(forward, right, percent);
Right3.spin(forward, right, percent);
}
This was adapted from https://wiki.purduesigbots.com/software/competition-specific/curvature-cheesy-drive


Engineering Notebook
Technical documentation
The engineering notebook is the pièce de rèsistance of a VEX team. From the engineering notebook, one should be able to follow the entire design process of a team. At a basic level, the notebook should have:
* Analysis of the game
* Possible designs
* Selection of the best design
* Step-by-step documentation of the building process
* The full code for the robot
* Testing and test results
* Project management notes
In this section, we will be using team 96504C's Spin Up notebook as an example. While this notebook did earn 4 Excellence Awards, it is not a perfect notebook. Still, it's a good starting point.
Formatting
For the Engineering Notebook
There are many programs that can be used to create Engineering Notebooks: Google Docs, Google Slides, Word, Notion, etc. We recommend Google Docs because it is easy to collaborate with others, but any word processor will work. For competitions, print out the notebook and put the pages in a 3-ring binder.
Here's an example of a well-formatted notebook page. The green annotations highlight the good aspects of this notebook page


Team 96504C's budgeting page. Some ideas adapted from 515R
Some of the important elements of every notebook page:
* Header / footer with section number
* Header / footer with page number
* Digital signatures with dates of contribution
Additionally, make sure to include a table of contents at the beginning of the notebook, so that it's easy to find sections in the notebook. See the next page, "Notebook Walkthrough" for more information.
Notebook Walkthrough
Step-by-step notebook guide
We'll go through most of the notebook sections you should include, with examples. Every page of the notebook should make it easier for the judges to give your team a perfect score on the notebook rubric.
Here's the notebook rubric, for reference: https://roboticseducation.org/documents/2023/06/guide-to-judging.pdf/#page=38&zoom=100,44,62
________________


Introductory Pages
These should go at the front of your notebook; they organize and propel the rest of the notebook.
Title Page
The title page should prominently feature the team name, number, and logo (if you have one). This allows the judges to easily identify which notebook is yours and makes it more memorable when they are distributing awards.


Simple title page
Table of contents
The table of contents organizes the rest of the notebook. When appropriate, each entry should be color-coded based on the Engineering Design Process. For example, the game introduction falls under the "ask" step, so it's colored red in the table of contents below. There are a number of ways to format the table of contents itself, but it should be clear when each entry was made and what step of the Engineering Design Process it shows.


Example table of contents from team 96504C. Some formatting adopted from team 96504P
Engineering Design Process
The Engineering Design Process is the essence of VEX Robotics. Thus, a brief description of the process, in the form of a graphic or text, should be included in the notebook. Make sure to cite your sources for images that are taken from another website!


Cite your sources!
Team Profile
After the Engineering design process, you should include a brief description of the team. This helps the judges match faces to teams, and makes your notebook more memorable. For a great example of a team profile (and other good notebook advice), check out https://wiki.purduesigbots.com/team-administration/team-documentation/how-to-start-a-notebook/segments-of-the-notebook#the-team
Notebook Formatting
Next, we recommend including a page about how the notebook is formatted. This should give the judges a basic idea of how the notebook is set up, and allow them to navigate and grade the notebook quickly.


Google docs has version history tracking! Use that or something similar to verify dates of contribution
Goals
The goals section can be very short, but your team should outline a few targets to reach. A few example goals:
* Qualifying to States / Worlds
* Winning a tournament
* Learning a new programming technique
* Building a low friction drivetrain
GANTT Chart

Flywheel.spin(forward); //just an example

wait(25, msec);

}

return 0; //C++ technicality

}

Tasks can be created with this line of code, and will not run until they have been created. The variable spinFlywheel stores the task internally for future reference.

task spinFlywheel = task(myTask);

If you want the task to stop running, call the stop() function on it:

spinFlywheel.stop();

We recommend using tasks for controlling lifts, catapults, or flywheels when the control algorithm required is non-trivial.

Advanced Drive Code

A more intuitive driving experience

While the basic split arcade drive does work, we'll show you a small addition to the code that can make the driving experience more intuitive. This code simply adjusts the turns to be more intense when the robot is going faster.

void driveCode() {

//drives the robot around based on controller input, double arcade controls

//First, get controller inputs

int straight = Controller1.Axis3.value(); //gives a number -100 to 100

int turn = Controller1.Axis1.value();

//adjust the turn variable based on the straight one

if (forward1 > 50) {

turn *= (((forward1 - 50) / 50) + 1);

} else if (forward1 < -50) {

turn *= (((-50 - forward1) / 50) + 1);

}

//Calculate proper motor powers

int left = straight + turn * 0.7; //the 0.7 makes the turns less intense

int right = straight - turn * 0.7;

//Spin the drive motors at the calculated velocity

Left1.spin(forward, left, percent);

Left2.spin(forward, left, percent);

Left3.spin(forward, left, percent);

Right1.spin(forward, right, percent);

Right2.spin(forward, right, percent);

Right3.spin(forward, right, percent);

}

This was adapted from https://wiki.purduesigbots.com/software/competition-specific/curvature-cheesy-drive

Engineering Notebook

Technical documentation

The engineering notebook is the pièce de rèsistance of a VEX team. From the engineering notebook, one should be able to follow the entire design process of a team. At a basic level, the notebook should have:

* Analysis of the game

* Possible designs

* Selection of the best design

* Step-by-step documentation of the building process

* The full code for the robot

* Testing and test results

* Project management notes

In this section, we will be using team 96504C's Spin Up notebook as an example. While this notebook did earn 4 Excellence Awards, it is not a perfect notebook. Still, it's a good starting point.

Formatting

For the Engineering Notebook

There are many programs that can be used to create Engineering Notebooks: Google Docs, Google Slides, Word, Notion, etc. We recommend Google Docs because it is easy to collaborate with others, but any word processor will work. For competitions, print out the notebook and put the pages in a 3-ring binder.

Here's an example of a well-formatted notebook page. The green annotations highlight the good aspects of this notebook page

Team 96504C's budgeting page. Some ideas adapted from 515R

Some of the important elements of every notebook page:

* Header / footer with section number

* Header / footer with page number

* Digital signatures with dates of contribution

Additionally, make sure to include a table of contents at the beginning of the notebook, so that it's easy to find sections in the notebook. See the next page, "Notebook Walkthrough" for more information.

Notebook Walkthrough

Step-by-step notebook guide

We'll go through most of the notebook sections you should include, with examples. Every page of the notebook should make it easier for the judges to give your team a perfect score on the notebook rubric.

Here's the notebook rubric, for reference: https://roboticseducation.org/documents/2023/06/guide-to-judging.pdf/#page=38&zoom=100,44,62

________________

Introductory Pages

These should go at the front of your notebook; they organize and propel the rest of the notebook.

Title Page

The title page should prominently feature the team name, number, and logo (if you have one). This allows the judges to easily identify which notebook is yours and makes it more memorable when they are distributing awards.

Simple title page

Table of contents

The table of contents organizes the rest of the notebook. When appropriate, each entry should be color-coded based on the Engineering Design Process. For example, the game introduction falls under the "ask" step, so it's colored red in the table of contents below. There are a number of ways to format the table of contents itself, but it should be clear when each entry was made and what step of the Engineering Design Process it shows.

Example table of contents from team 96504C. Some formatting adopted from team 96504P

Engineering Design Process

The Engineering Design Process is the essence of VEX Robotics. Thus, a brief description of the process, in the form of a graphic or text, should be included in the notebook. Make sure to cite your sources for images that are taken from another website!

Cite your sources!

Team Profile

After the Engineering design process, you should include a brief description of the team. This helps the judges match faces to teams, and makes your notebook more memorable. For a great example of a team profile (and other good notebook advice), check out https://wiki.purduesigbots.com/team-administration/team-documentation/how-to-start-a-notebook/segments-of-the-notebook#the-team

Notebook Formatting

Next, we recommend including a page about how the notebook is formatted. This should give the judges a basic idea of how the notebook is set up, and allow them to navigate and grade the notebook quickly.

Google docs has version history tracking! Use that or something similar to verify dates of contribution

Goals

The goals section can be very short, but your team should outline a few targets to reach. A few example goals:

* Qualifying to States / Worlds

* Winning a tournament

* Learning a new programming technique

* Building a low friction drivetrain

GANTT Chart