| 006:010 Khan | : |
And indeed (many) Messengers were mocked before you, but their scoffers were surrounded by the very thing that they used to mock at. |
| 006:010 Maulana | : |
And certainly messengers before thee were derided but that which they derided encompassed those of them who scoffed. |
| 006:010 Pickthal | : |
Messengers (of Allah) have been derided before thee, but that whereat they scoffed surrounded such of them as did deride. |
| 006:010 Rashad | : |
Messengers before you have been ridiculed. It is those who mocked them who suffered the consequences of their ridiculing. |
| 006:010 Sarwar | : |
They mocked the Messengers who lived before you (Muhammad), but those who received warnings of punishment and mocked the warnings, all suffered their torments accordingly. |
| 006:010 Shakir | : |
And certainly messengers before you were mocked at, but that which they mocked at encompassed the scoffers among them. |
| 006:010 Sherali | : |
And surely the Messengers have been mocked at before thee, but that which they mocked at encompassed those of them who scoffed at it. |
| 006:010 Yusufali | : |
Mocked were (many) messengers before thee; but their scoffers were hemmed in by the thing that they mocked. |
Concepts/Themes Covered: أركان الإسلام > التوحيد > الكافرون > إعراضهم عن آيات الله Pillars of Islam> Islamic> The Disbelievers> Their Turning away from Allah's Signs أركان الإسلام > (محمد (صلى الله عليه وسلم > تأييد رسالته Pillars of Islam> The Blessed Muhammad(PBUH)> Supporting his Message أركان الإسلام > (محمد (صلى الله عليه وسلم > تسليته وتثبيته Pillars of Islam> The Blessed Muhammad(PBUH)> Cheering and Consolidating Him الإنسان والعلاقات الأخلاقية > الأخلاق الذميمة > السخرية Man and The Moral Relations>The Dispraised Morals>Sarcasm
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Labour support in Scotland falling ‘like snow off a dyke’, claims SNP
Justice Secretary Humza Yousaf made the claim as he campaigned in Glasgow North East – a seat the SNP are hoping to win from Labour.
The SNP is forecasting it will win seats back from Labour in next month’s General Election, as a senior figure claimed support for Jeremy Corbyn’s party is “falling off like snow off a dyke”.
Humza Yousaf, the Scottish Justice Secretary, predicted his party would do a “lot better” than it did in 2017, when 35 SNP MPs were elected.
He made the claim after Mr Corbyn spent two days campaigning in Scotland – during which he was repeatedly forced to clarify his stance on whether Labour would permit a second independence referendum.
The UK Labour leader initially said such a vote would not be permitted in the first five-year parliamentary term of a Labour government, before changing this to say it would not take place in the “early years” of such an administration.

Mr Yousaf told the PA news agency: “Labour’s support that they had in 2017 is falling off like snow off a dyke.
“I’m very confident we are going to do a lot better.”
Speaking as he campaigned in Glasgow North East, which Labour’s Paul Sweeney won in 2017, Mr Yousaf said the SNP are “quite confident” of seizing the seat on December 12.
However, Mr Sweeney said voters in the constituency are “flocking to Labour” and he is “confident” of winning the seat again.
He said: “When Labour won this seat in 2017, we did so against the odds. We don’t take this seat for granted, but despite the 2017 result the SNP do.
“Mr Yousaf’s bluster simply does not correspond to the response we are getting in the community.
“Old Labour voters, SNP voters, non-voters, all are flocking to Labour.”
Mr Yousaf also demanded that whoever forms the next UK government repays the VAT charges that police and fire services in Scotland had to pay for years after the SNP merged them into national bodies.
But he said five years worth of payments – amounting to £175 million – should also be returned, as he accused Westminster of “dipping their hands into the pockets of our emergency services, singling out Scottish police and fire services to unfairly face VAT bills”.
Mr Yousaf said: “SNP MPs will hold the next UK government to account and demand that they pay back that money to our police and fire services.
“Our main message to whoever gets into Number 10 is a very clear one – you have taken £175 million of VAT from our police and fire services, whoever gets into Number 10, we demand that back.”


Local Trivia Events Day Location -- Sunday Monday Tuesday Wednesday Thursday Friday Saturday -- Ballard Wallingford Capitol Hill Lower Queen Anne University District Anywhere in Seattle


Results, constructors championship standings, drivers championship standings, fastest laps and more ...
League scorers, standings, stats, draft history, draft rankings, teams and more ...
League scorers, standings, stats, draft history, draft rankings, teams and more ...


Select Plan
Choose your meal options
There are separate plans for lunch and dinner. Please choose one plan. It will be valid for 4 weeks from the order date.
No. Of People:
No. Of People:
No. Of People:
No. Of People:
No. Of People:
No. Of People:
No. Of People:
No. Of People:


2 instantiations of CommandNotFoundException
System.Management.Automation (2)
engine\CommandDiscovery.cs (2)
1107
CommandNotFoundException commandNotFound = new
CommandNotFoundException
(
1215
CommandNotFoundException commandNotFound = new
CommandNotFoundException
(
30 references to CommandNotFoundException
Microsoft.PowerShell.Commands.Utility (1)
commands\utility\ImplicitRemotingCommands.cs (1)
735
if (Deserializer.IsInstanceOfType(remoteException.SerializedRemoteException, typeof(
CommandNotFoundException
)))
System.Management.Automation (29)
engine\CommandDiscovery.cs (13)
267
/// <exception cref="
CommandNotFoundException
">
535
/// <exception cref="
CommandNotFoundException
">
562
CommandNotFoundException
e =
592
CommandNotFoundException
e =
610
CommandNotFoundException
e =
635
CommandNotFoundException
e = new CommandNotFoundException(
728
/// <exception cref="
CommandNotFoundException
">
874
CommandNotFoundException
e =
1012
catch (
CommandNotFoundException
) { }
1107
CommandNotFoundException
commandNotFound = new CommandNotFoundException(
1135
catch (
CommandNotFoundException
) { throw; }
1215
CommandNotFoundException
commandNotFound = new CommandNotFoundException(
1238
catch (
CommandNotFoundException
) { throw; }
engine\CommandProcessor.cs (2)
55
/// <exception cref="
CommandNotFoundException
">
752
CommandNotFoundException
exception =
engine\ExternalScriptInfo.cs (1)
573
CommandNotFoundException
cmdE = new CommandNotFoundException(innerException.Message, innerException);
engine\GetCommandCommand.cs (3)
848
catch (
CommandNotFoundException
)
914
CommandNotFoundException
e =
929
catch (
CommandNotFoundException
exception)
engine\Modules\ModuleCmdletBase.cs (1)
6757
catch (
CommandNotFoundException
cnfe)
engine\MshCmdlet.cs (1)
336
catch (
CommandNotFoundException
) { }
engine\remoting\commands\newrunspacecommand.cs (1)
890
catch (
CommandNotFoundException
)
engine\remoting\commands\PSRemotingCmdlet.cs (2)
1628
catch (
CommandNotFoundException
)
1676
catch (
CommandNotFoundException
)
engine\remoting\commands\PushRunspaceCommand.cs (2)
928
catch (
CommandNotFoundException
)
965
catch (
CommandNotFoundException
)
help\AliasHelpProvider.cs (1)
103
catch (
CommandNotFoundException
)
help\BaseCommandHelpInfo.cs (1)
271
catch (
CommandNotFoundException
)
help\CommandHelpProvider.cs (1)
1276
catch (
CommandNotFoundException
)


Bogo Traceroute: The Traceroute Simulator
Source Address:
Destination Address:
Destination Host Name:
Fetch All
AddEntry
TraceRT
Blank
Blank
initializing...


Welcome
Graham Otieno
I am very passionate about technology.And belive that with a good technology life can be made easier and the output quality will be very high.
I am also in love with coding and programming which is one of the reasons I joined Moringa School.
To be one of the greatest Programmers in Africa.
Learn a couple of programming Languages.
Earn a living with programming.
Playing hockey
Playing Video games
Exploring the computer
I am a go getter
I can blink ten times per second.
I did my High School at Maranda High School(Siaya County).But currently a Prep student in Moringa School along Ngong Road
I am also yet to join the University in September
I have done one personal project.I used both css and HTML.The project was about an agency which helps people book there travells.
It was my first project
personal-projectI have also done one group project with my peers.
In that project I did the menu and the Services part.It was a project on a Hotel.
This project enabled us to practice branching and merging it was fun
group-project| Name | Contact |
|---|---|
| Email address |<EMAIL_ADDRESS>|
| Phone number |<PHONE_NUMBER> |


Etheroji: where you can buy and sell Emojis using Ethereum Smart Contracts. Simply select your choice of Emoji on the site, pay your Ether and then add the link of your choice, so other visitors clicking on it will be directed to your site*.
Your ownership is recorded on the Ethereum blockchain and through the power of Smart Contracts if someone else wants to then buy your Emoji then you will automatically receive your original Ether value back, along with a 20% profit. The Smart Contract controls the price of each Emoji, doubling it each time they are purchased (although keep in mind that it may be that no one wants to buy the Emoji after you – so no returns are guaranteed).
A Smart Contract is a contract coded into the blockchain that is enforced based on a set of rules. While there are plenty of code and theoretical examples available, few are active or do anything average users might understand. Etheroji changes all of that, providing a fun demonstration of this exciting new technology open to anyone with an Ethereum wallet. The Contract is open sourced and available to view below.
Etheroji demonstrates the power of Smart Contract technology, but will also allow us to fund an office kitten (and, all being well, eventually cat). For more details check out the FAQ below
First thing is to go to an exchange where you can use fiat (normal money like Dollars, Euros or Pounds) to buy your Ether. If you’re new to all of this we’d suggest Coinbase as it acts both as an exchange AND a wallet – i.e. you can both buy and store your Ether there. Also, as with any online financial activities, we’d recommend a strong password, and that you turn on their 2 Factor authentication (which means you either receive a text message with a code or have the Google App on your phone to generate one – each time you login).
You will need to get a browser plug-in to buy your Emoji. For this we’d recommend using Mozilla Firefox or Google’s Chrome browser and installing the Metamask plug-in from this link https://metamask.io (again alternatives are available). This will allow you to pay, but also provides your identity for the Smart Contract to confirm your ownership of the link you submit – it also means you can get paid if someone else then buys your Emoji.
There is a fair amount of discussion around this, however in this context its a short-hand for websites that support payments using cryptocurrencies and tokens like Ethereum and for this you'll need to have a browser that supports it. You've probably been directed here as you tried to buy an Emoji and the message said you don't have a Web3 enabled browser. We'd recommend using Chrome or Firefox and the Metamask plug-in. Read on in our exciting WTF for more info on setting these up and how to use them.
This Quora page has some good info on Ether and how if differs from Bitcoin - https://www.quora.com/What-is-Ethereum-and-how-is-it-different-from-Bitcoin.
How about buying an Emoji on Etheroji.com
You can pick your emoji that then appears on Etheroji.com and add a link of your choosing.
You will own that Emoji and your ownership and choice of URL destination are recorded on the Ethereum blockchain. If someone else wants to buy it you get back the Ethereum you paid for it +20%. However, we are obliged to remind you that there is no guarantee that someone else will ever want to buy it.
Etheroji is a fun experiment with Ethereum blockchain technology and demonstrate the power of Smart Contracts. Its also a chance for you to drive traffic to the URL of your choice and potentially profit if others decide to buy your Emoji from you.
No, but you can always buy it back if you want it that badly.
Thanks to the Smart Contract the prices are fixed, they double each time an Emoji is sold.
Currently we've got 1088 emojis on offer. Keep your eye out for new ones...
We reserve the right to remove emoji links if they are pointed at abusive, illegal or unsuitable sites and replace them with something to do with cats. Everyone likes cats.
We’re planning on getting an office cat, we’ve always wanted a cat.
You can find our contract at 0x1b9c123c28dcef6f91f55b38743d9958661f84aa
on the mainnet
network.
View the contract on Etherscan.
The simplest explanation is that Ethereum is the network and Ether is the crypto currency unit that you spend. There are better, and more technical, explanations available via your preferred search engine.
The display of Emojis on the page is dynamic. When an emoji is purchased, it will move above those which are cheaper. This means that those displayed first are the most expensive
It can take a little while for the purchase to process, so give it five minutes before you start rage tweeting.
No, all you are buying is the right to add the link of your choice to an Emoji on the Etheroji website. This doesn’t give you the rights to go around telling people that you own the poo emoji, or writing to the people who made the Emoji movie asking for your share of the profits.
No, you are buying the right to have the link of your choice attached to an Emoji displayed on our site. Someone else may then chose to buy the same Emoji in which case you will get your Ether back + 20%. But keep in mind that they may not, in which case you’ll just get traffic sent to the link of your choice as people click on that emoji.
Once you’ve bought the Emoji it is set in stone on the blockchain, so you can’t make any edits. Unless you want to buy the Emoji again.
Because of the way the Ethereum network operates you will be charged a transaction fee for completing your purchase. You will be quoted the maximum "gas" amount required by metamask before you hit the green approve button (it may end up being less than this). This will also mean that you may receive a message that you don't have enough funds in your metamask account to make a transaction even if you have enough for the quoted price. This is all standard to Ethereum and frankly a bit confusing - but hey we're all learning as we go here!


--- layout: page title: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing" description: "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document provides an overview of HTTP architecture and its associated terminology, defines the \"http\" and \"https\" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes general security concerns for implementations." ---
| Document Name: | RFC 7230 |
|---|---|
| Document URI: |
urn:ietf:rfc:7230
|
| Online Version: |
https://datatracker.ietf.org/doc/html/rfc7230
|
| Organization: | Internet Engineering Task Force (IETF) |
| Series: | Request for Comments (RFC) |
| Abstract: | The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document provides an overview of HTTP architecture and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes general security concerns for implementations. |
compress
,
deflate
,
gzip
,
x-compress
,
x-gzip
Close
,
Connection
,
Content-Length
,
Host
,
TE
,
Trailer
,
Transfer-Encoding
,
Upgrade
,
Via
chunked
,
compress
,
deflate
,
gzip
,
x-compress
,
x-gzip
application/http
,
message/http
http
,
https
Return to ( Series | Organization | all Specifications )


Power10 enablement.
Power9 enablement.
Power9-optimized instruction scheduling in GCC.
Requires at least Power8 for ppc64le.
Power8 Transactional Memory enablement.
Power8 Crypto Operations enablement.
Power8, Power9, and Power10 optimized system libraries.
_Float128 enablement as specified by ISO/IEC TS 18661-3, for Power9 and Power10.
GCC creates binaries using --mcpu=power8 --mtune=power10 by default.
Advance Toolchain new location
Since the end of August 2019, Advance Toolchain has been available from a new FTP server: public.dhe.ibm.com
Please be advised the FTP server at Unicamp won't be updated any longer.
New features in 15.0-1
- GCC provides:
- GNU C Library provides:
- Binutils provides:
- Userspace RCU provides:
- Fix: add missing pkgconfig file for memb flavour lib.
- Make temporary variable in _rcu_dereference non-const.
- OpenSSL provides:
- Python provides:
Previous releases
New features in 15.0-0
- GCC provides:
- GNU C Library provides:
- Version 2.34, see the release notes for details.
- New Power10 optimizations for memcmp, memcpy, memmove, memset, rawmemchr, strcpy, strlen, stpcpy.
- Libraries libpthread, libdl, libutil, libanl have been integrated into libc.
- Linux: Fix fcntl, ioctl, prctl redirects for _TIME_BITS=64.
- copy_and_spawn_sgid: Avoid double calls to close().
- gaiconf_init: Avoid double-free in label and precedence lists.
- gconv_parseconfdir: Fix memory leak.
- ldconfig: avoid leak on empty paths in config file.
- Binutils provides:
- GNU Debugger provides:
- Userspace RCU provides:
- OpenSSL provides:
- Expat provides:
- Libhugetlbfs provides:
- Removed support for hugepage malloc from libhugetlbfs.
libhugetlbfs provides a hugepage malloc feature that adapts glibc malloc to use hugepages. Recent changes in glibc 2.34 made it impossible for libhugetlbfs to continue to change the behavior of glibc's malloc. Notice that libhugetlbfs is still able to map data, text and BSS sections to huge pages.
An issue has been opened to track this.
- Python provides:
- Boost provides:
- libdfp provides:
- libnxz provides:
- Valgrind provides:
- TCMalloc provides:
- TBB provides:
New features in 14.0-3
- GCC provides:
- GNU C Library provides:
- Binutils provides:
- OpenSSL provides:
- Expat provides:
- Python provides:
- Userspace RCU provides:
- Version 0.12.2, see the release notes for details.
- Fix for rculist header: use parenthesis around macro parameters.
- Fix for rcuhlist header: use parenthesis around macro parameters.
- Fix for hlist header: use parenthesis around macro parameters.
- Fix for list.h: use parenthesis around macro parameters, caa_container_of().
- Fix for hlist iteration relies on undefined behavior.
- Fix for use __atomic_load() rather than atomic load explicit.
- Fix for use atomic load memory_order_consume for rcu_dereference on C11/C++11.
- Fix for HAVE_SCHED_SETAFFINITY is not defined.
- Fix for shadowed local variable (-Wshadow).


A versatile notification API server
Containerized deployment to PAAS such as OpenShift. No need for complex enterprise-wide shared service. Better meet privacy mandates.
More about NotifyBC →Quick-start Instructions
~ $ git clone https://github.com/bcgov/MyGovBC-notification-server.git notifyBC
~ $ cd notifyBC
~/notifyBC $ npm i -g yarn && yarn install
~/notifyBC $ npm start
# => Now browse to http://localhost:3000


Use this simple device during any social event and you’re virtually guaranteed to develop killer dance moves; become the most entertaining person in the room; and attract 180 percent more attention from potential love interests.


|
CUDNN API
8
|
#include <cudnn_frontend_OperationGraph.h>
Public Member Functions | |
| std::string | describe () const override |
| Return a string describing the backend Descriptor. More... | |
| OperationGraph_v8 (OperationGraph_v8 &&from) | |
| ~OperationGraph_v8 ()=default | |
| auto | getEngineCount (void) const -> int64_t |
| Query the total count of the engines for the Operation Set. More... | |
| std::string const & | getTag () const |
| Public Member Functions inherited from cudnn_frontend::BackendDescriptor | |
| cudnnBackendDescriptor_t | get_raw_desc () const |
| cudnnStatus_t | get_status () const |
| Current status of the descriptor. More... | |
| void | set_status (cudnnStatus_t const status_) const |
| Set status of the descriptor. More... | |
| void | set_error (const char *message) const |
| Set Diagonistic error message. More... | |
| const char * | get_error () const |
| Diagonistic error message if any. More... | |
| ManagedOpaqueDescriptor | get_desc () const |
| Returns a copy of underlying managed descriptor. More... | |
| cudnnStatus_t | initialize_managed_backend_pointer (cudnnBackendDescriptorType_t type) |
| Initializes the underlying managed descriptor. More... | |
Private Member Functions | |
| OperationGraph_v8 ()=default | |
| OperationGraph_v8 (OperationGraph_v8 const &)=delete | |
| OperationGraph_v8 & | operator= (OperationGraph_v8 const &)=delete |
Private Attributes | |
| cudnnHandle_t | handle = nullptr |
| std::array< ManagedOpaqueDescriptor, 10 > | ops {} |
| int64_t | numOps = -1 |
| std::string | opGraphTag = "" |
Friends | |
| class | OperationGraphBuilder_v8 |
Additional Inherited Members | |
| Protected Member Functions inherited from cudnn_frontend::BackendDescriptor | |
| BackendDescriptor (ManagedOpaqueDescriptor pointer_, cudnnStatus_t status_, std::string err_msg_) | |
| BackendDescriptor ()=default | |
| Protected Attributes inherited from cudnn_frontend::BackendDescriptor | |
| ManagedOpaqueDescriptor | pointer |
| cudnnStatus_t | status = CUDNN_STATUS_SUCCESS |
| Shared pointer of the OpaqueBackendPointer. More... | |
| std::string | err_msg |
| Error message if any being set. More... | |
OperationGraph_v8 Class This class tells the properties of the Tensor_v8 on which the operation will be performed Properties:
Use OperationGraphBuilder_v8 to build this class. Describe returns a string describing the tensor class
Definition at line 51 of file cudnn_frontend_OperationGraph.h.
|
inline |
Definition at line 61 of file cudnn_frontend_OperationGraph.h.
References ~OperationGraph_v8().
|
default |
Referenced by OperationGraph_v8().
|
privatedefault |
Referenced by getTag().
|
privatedelete |
|
inlineoverridevirtual |
Return a string describing the backend Descriptor.
Implements cudnn_frontend::BackendDescriptor.
Definition at line 55 of file cudnn_frontend_OperationGraph.h.
|
inline |
Definition at line 95 of file cudnn_frontend_OperationGraph.h.
References OperationGraph_v8(), operator=(), and opGraphTag.
|
privatedelete |
Referenced by cudnn_frontend::OperationGraphBuilder_v8::build(), and getTag().
|
friend |
Definition at line 53 of file cudnn_frontend_OperationGraph.h.
Referenced by cudnn_frontend::OperationGraphBuilder_v8::build().
|
private |
Definition at line 105 of file cudnn_frontend_OperationGraph.h.
|
private |
Definition at line 107 of file cudnn_frontend_OperationGraph.h.
|
private |
Definition at line 108 of file cudnn_frontend_OperationGraph.h.
Referenced by getTag().
|
private |
Definition at line 106 of file cudnn_frontend_OperationGraph.h.


Situated on the south eastern corner of England, Dover is the closest port to the French coast. The Dover area is extremely busy at all hours of the day or night. Ferries and ships enter and exit the harbour at high speeds. It is advisable to contact Dover Port Control on CH74 and notify them of your course and intentions, even if only passing by. Notifying them keeps you on their radar until your well out of range of the high-speed craft, ferries, or shipping.
In spite of being a busy commercial port, yachts are very welcome here and there are good facilities in protected berths.
Photo taken by SY Suwena July 2013.
Permission must be obtained BEFORE entering (or leaving), by calling Port Control on VHF channel 74, or attracting the attention of a harbour control launch (5 short flashes).
With over 160 ferry movements per day, great care is needed when negotiating either of the two entrances. Also, beware of the strong cross-tides in the approaches.
From 3 hours before until 1 hour after HW Dover, the tide runs into the western entrance and at all other times it runs out of the entrance at up to 2.3 knots. From 2 hours before to 4 hours after HW Dover, the tide outside the harbour flows in a northeasterly direction and at all other times it runs south-west.
Marina approaches
Dover has an Outer Harbour containing the ferry and deepwater commercial berths and an Inner Harbour, between the Prince of Wales and Admiralty piers where the Marina is located. An approach channel between the North and South piers has an average dredged depth of 5 metres gradully reducing as it enters the Tidal Harbour.
Yachts are often met at the entrance by a harbour control launch and advised on suitable berthing.
Most visitors use the marina in Granville Dock (see photo taken by SY Suwena), but pontoon berths are also available in the Wellington Dock and the Tidal Basin, and visitors' buoys in the outer harbour. There is an anchorage in the outer harbour, but it is generally uncomfortable due to the constant movement of ferries.
Anchored boats cannot be left unattended here.
For more information about the harbour, see here.
Harbour Master
Tel:+44 (0) 1304 240 400 ext. 4520
Fax:+44 (0) 1304 225 144
VHF Channel 74 (Port Control & Harbour launch), 12, 16
Duty Harbour Master Tel: Mob. 07836 262713
Last updated April 2016.
[Show additional 4 entries for this category]


HOLY THURSDAY:
EVENING MASS
FIRST READING Exodus 12:1-8.11-14
In those days: The LORD said to
Moses and Aaron in the
The word of the Lord
RESPONSORIAL PSALM Psalm 116
R. The cup of blessing is a participation in the blood of Christ.
How can I repay the LORD for
all his goodness to me? The cup of salvation I will raise; I will call on the
name of the LORD.
R. The cup of blessing is a participation in the blood
of Christ.
How precious in the eyes of the LORD is the death
of his faithful.
R. The cup of blessing is a participation in the blood
of Christ.
A thanksgiving sacrifice I make; I will call on the
name of the LORD. My vows to the LORD I will fulfil before all his people.
R. The cup of blessing is a participation in the blood
of Christ.
SECOND READING 1 Corinthians 11:23-26
Brethren: I received from the Lord what I also delivered to you, that the Lord Jesus on the night when he was betrayed took bread, and when he had given thanks, he broke it, and said, "This is my body which is for you. Do this in remembrance of me." In the same way also the chalice, after supper, saying, "This chalice is the new covenant in my blood. Do this, as often as you drink it, in remembrance of me." For as often as you eat this bread and drink the chalice, you proclaim the Lord's death until he comes.
The word of the Lord
ALLELUIA John 13:34
R. Glory and praise to you, O Christ
A new commandment I give to you, says the Lord, that you love one another even as I have loved you.
R. Glory and praise to you, O Christ
GOSPEL John 13:1-15
Before the feast of the
Passover, when Jesus knew that his hour had come to depart out of this world to
the Father, having loved his own who were in the world, he loved them to the end.
And during supper, when the devil had already put it into the heart of Judas
Iscariot, Simon's son, to betray him, Jesus, knowing that the Father had given
all things into his hands, and that he had come from God and was going to God,
rose from supper, laid aside his garments, and tied a towel around himself.
Then he poured water into a basin, and began to wash the disciples' feet, and
to wipe them with the towel that was tied around him. He came to Simon Peter;
and Peter said to him, "Lord, do you wash my feet?" Jesus answered
him, "What I am doing you do not know now, but afterward you will
understand." Peter said to him, "You shall never wash my feet."
Jesus answered him, "If I do not wash you, you have no part in me."
Simon Peter said to him, "Lord, not my feet only but also my hands and my
head!" Jesus said to him, "He who has bathed does not need to wash,
except for his feet, but he is clean all over; and you are clean, but not every
one of you." For he knew who was to betray him; that was why he said,
"You are not all clean." When he had washed their feet, and taken his
garments, and resumed his place, he said to them, "Do you know what I have
done to you? You call me Teacher and Lord; and you are right, for so I am.  For I have given you an example, that you also should do as I
have done to you.
The Gospel of the Lord


If at any time the Robot operation or Team actions are deemed unsafe or have damaged any Field Elements or Game Objects, the offending Teams may be Disabled and/or Disqualified at the discretion of the Head Referee. The Robot will require re-inspection before it may take the field again.
If a Robot is completely out-of-bounds (outside the playing field), it will be Disabled for the remainder of the Match.
All Drive Team Members must wear safety glasses or glasses with side shields while in the Alliance Stations during Matches. While in the pit area, it is highly recommended that all Team members wear safety glasses.
All Teams are expected to conduct themselves in a respectful and professional manner while competing in VEX Robotics Competition events. If a Team or any of its members (Students or any Adults associated with the Team) are disrespectful or uncivil to event staff, volunteers, or fellow competitors, they may be Disqualified from a current or upcoming Match. Team conduct pertaining to <G1> may also impact a Team’s eligibility for judged awards. Repeated or extreme violations of <G1> could result in a Team being Disqualified from an entire event, depending on the severity of the situation.
Robotics competitions often induce intense, high stress situations. These are good opportunities to model and/or gain experience in handling these situations in a positive and productive manner. It is important that we all exhibit maturity and class when dealing with any difficult situations that may present themselves in both the VEX Robotics Competition and our lives in general.
This rule exists alongside the REC Foundation Code of Conduct. Violation of the Code of Conduct can be considered a violation of
Adults may assist Students in urgent situations, but Adults may never work on or program a Robots without Students on that Team being present and actively participating. Students must be prepared to demonstrate an active understanding of their Robot’s construction and programming to judges or event staff.
Some amount of Adult mentorship, teaching, and/or guidance is an expected and encouraged facet of VEX competitions. No one is born an expert in robotics! However, obstacles should always be viewed as teaching opportunities, not tasks for an Adult to solve without Students present and actively participating.
When a mechanism falls off, it is…
…okay for an Adult to help a Student investigate why it failed, so it can be improved.
…not okay for an Adult to put the Robot back together.
When a Team encounters a complex programming concept, it is…
…okay for an Adult to guide a Student through a flowchart to understand its logic.
…not okay for an Adult to write a pre-made command for that Student to copy/paste.
During Match play, it is…
…okay for an Adult to provide cheerful, positive encouragement as a spectator.
…not okay for an Adult to explicitly shout step-by-step commands from the audience.
At the beginning of a Match, each Robot must be smaller than a volume of 18” (457.2 mm) long by 18” (457.2 mm) wide by 18” (457.2 mm) tall. Using Field Element, such as the field perimeter wall, to maintain starting size is only acceptable if the Robot would still satisfy the constraints of <R5> and pass inspection without the Field Element. Robots in violation of this limit will be removed from the field prior to the start of the Match, at the Head Referee’s discretion.
Robots may not intentionally detach parts during the Match or leave mechanisms on the field.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion. Multiple intentional infractions may result in Disqualification for the entire competition.
Each Team must include Drivers, Programmer(s), Designer(s), and Builder(s). No Student may fulfill any of these roles for more than one VEX
Robotics Competition Team in a given competition season. Students may have more than one role on
the Team, e.g. the Designer can also be the Builder, the Programmer and a Driver.
a. Team members may move from one Team to another for non-strategic reasons outside of the
Team’s control.
i. Examples of permissible moves may include, but are not limited to, illness, changing schools,
conflicts within a Team, or combining / splitting Teams.
ii. Examples of strategic moves in violation of this rule may include, but are not limited to, one
Programmer “switching” Teams in order to write the same program for multiple Robots, or one
Student writing the Engineering Notebook for multiple Teams.
iii. If a Student leaves a Team to join another Team, <G6> still applies to the Students remaining
on the previous Team. For example, if a Programmer leaves a Team, then that Team’s Robot
must still represent the skill level of the Team without that Student. One way to accomplish this
would be to ensure that the Programmer teaches or trains a “replacement” Programmer in their
absence.
b. When a Team qualifies for a Championship event (e.g., States, Nationals, Worlds, etc) the Students
on the team attending the Championship event are expected to be the same Students on the Team
that was awarded the spot. Students can be added as support to the Team, but may not be added as
Drivers or Programmers for the team.
i. An exception is allowed if one (1) Driver and/or one (1) Programmer on the Team cannot attend
the event. The Team can make a single substitution of a Driver or Programmer for the
Championship event with another Student, even if that Student has competed on a different
Team. This Student will now be on this new Team and may not substitute back to the original
Team.
Violations of this rule will be evaluated on a case-by-case basis, in tandem with the REC Foundation
Student Centered Policy as noted in <G2>, and the REC Foundation Code of Conduct as noted in <G1>
During a Match, each Team may have up to three
(3) Drive Team Members in their Alliance Station and all Drive Team Members must remain in their
Alliance Station for the duration of the Match. Drive Team Members are not allowed to use any sort of
communication devices while in the Alliance Station. Devices with communication features turned off
(e.g. a phone in airplane mode) are allowed.
Note: Drive Team Members are the only Team members that are allowed to be in the Alliance Station
during a Match.
Note 2: During a Match, Robots may be operated only by the Drive Team Members and/or by software
running on the Robot’s control system, in accordance with <R28> and <G8>. Violations or refusal to
comply with this rule could be considered a violation of <G1> and is up to the discretion of the Head
Referee
Prior to the beginning of each Match, Drive Team Members must plug their VEXnet Joystick or V5 Controller into the VEXnet Field Controller’s Cat-5 cable via their controller’s competition port. This cable must remain plugged in for the duration of the Match, and may not be removed until the “all-clear” has been given for Drive Team Members to retrieve their Robots.
Minor violations of these rules that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Note: The intent of this rule is to ensure that Robots abide by commands sent by the tournament software. Temporarily removing the cable to assist with mid-Match troubleshooting, with an Event Partner or other event technical staff present and assisting, would not be considered a violation.
Drive Team Members may only touch the Team’s controls and Robot at specified times during a Match as per <G9a>. Drive Team Members are prohibited from making intentional contact with any Game Object, Field Element, or Robot during a Match, apart from the contact specified in <G9a>.
a. During the Driver Controlled Period, Drive Team Members may only touch their own Robot if the
Robot has not moved at all during the Match. Touching the Robot in this case is permitted only for
the following reasons:
i. Turning the Robot on or off.
ii. Plugging in a battery and/or power expander.
iii. Plugging in a VEXnet Key or V5 Robot Radio.
iv. Touching the V5 Robot Brain screen, such as to start a program.
b. Drive Team Members are not permitted to break the plane of the field perimeter at any time during the Match, apart from the actions described in <G9a>.
c. Transitive contact, such as contact with the field perimeter that causes the field perimeter to contact Balls inside of the field, would be considered a violation of this rule.
Minor violations of these rules that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Note: Any concerns regarding the Ball(s) starting positions should be raised with the Head Referee prior to the Match; Team members may never adjust the Balls or Field Elements themselves.
During the Autonomous Period, Drive Team Members are
not permitted to interact with the Robots in any way, directly or indirectly.
This could include, but is not limited to:
Minor violations of this rule will result in a Warning. Violations of this rule that affect the outcome of the Autonomous winner or disrupt the autonomous routine of their opponent will result in the Autonomous Bonus being awarded to the opposing Alliance. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Any infractions committed during the Autonomous Period that are not Match Affecting, but do affect the outcome of the Autonomous Bonus, will result in the Autonomous Bonus being automatically awarded to the opposing Alliance.
a. Teams are responsible for the actions of their Robots at all times, including during the Autonomous Period. Any infractions committed during the Autonomous Period that are Match Affecting can result in a Disqualification, if warranted by the rule.
b. If both Alliances cause infractions during the Autonomous Period that would have affected the outcome of the Autonomous Bonus, then no Autonomous Bonus will be awarded.
But, be prepared to encounter defense. Strategies aimed solely at the destruction, damage, tipping over, or Entanglement of opposing Robots are not part of the ethos of the VEX Robotics Competition and are not allowed. If the tipping, Entanglement, or damage is ruled to be intentional or egregious, the offending Team may be Disqualification from that Match. Repeated offenses could result in Disqualification from the entirety of the competition.
a. VEX Robotics Competition Change Up is intended to be an offensive game. Teams that partake in solely defensive or destructive strategies will not have the protections implied by <G12> (see <G13>). However, defensive play which does not involve destructive or illegal strategies is still within the spirit of this rule
b. VEX Robotics Competition Change Up is an interactive game. Some incidental tipping, Entanglement, and damage may occur as a part of normal gameplay without violation. It will be up to the head referee’s discretion whether the interaction was incidental or intentional.
c. A Team is responsible for the actions of its Robot at all times, including the Autonomous Period. This applies both to Teams that are driving recklessly or potentially causing damage, and to Teams that drive around with a small wheel base. A Team should design its Robot such that it is not easily tipped over or damaged by minor contact.
Note: A Robot which has expanded horizontally in an effort to obstruct the field, or is legally covering the top of a Goal in a solely defensive manner, should expect vigorous interactions from opponent Robots. Damage that is caused by opponent Robots pushing, tipping, or Entangling with them would not be considered a violation of <G12>. Gratuitous damage or dangerous mechanisms may still be considered a violation of <R4>, <S1>, or <G1> at the Head Referee’s discretion.
Put simply: “wall-bots” and “cap-bots” are legal, but they are to be attempted at your own risk
In the case where referees are forced to make a judgment call regarding a destructive interaction between a defensive and offensive Robot, or an interaction which results in a questionable rules violation, the referees will err on the side of the offensive Robot.
Intentional strategies that cause an opponent to violate a rule are not permitted, and will not result in an infraction on the opposing Alliance. Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
<G3> should be used when enforcing this rule. In most cases, if a Robot causes their opponent to break a rule, the referee will simply not enforce the penalty on that opponent. Only in extreme cases, where the act of forcing the opponent into breaking a rule changes the outcome of the match for the benefit of the Robot, should that Robot who caused the opponent to break a rule receive a Disqualification.
A Robot may not Trap an opposing Robot for more than five seconds (0:05) during the Driver Controlled Period. A Trap is officially over once the Trapping Robot has moved away and the Robots are separated by at least two (2) feet (approximately one [1] foam tile). After ending a Trap, a Robot may not Trap the same Robot again for a duration of five seconds (0:05). If a Team does Trap the same Robot again, the count will resume from where it left off when the Trapping Robot initially backed off.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Robots may not intentionally grasp, grapple or attach to any Field Elements. Strategies with mechanisms that react against multiple sides of a Field Element in an effort to latch or clamp onto said Field Element are prohibited. The intent of this rule is to prevent Teams from both unintentionally damaging the field and/or from anchoring themselves to the field.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Robots must be designed to permit easy removal of Balls from any mechanism without requiring the Robot to have power after a Match.
Scores will be calculated for all Matches immediately after the Match once all Balls, Field Elements, and Robots on the field come to rest.
a. The determination of the Autonomous Bonus will occur for all Matches immediately after the Autonomous Period after all Balls, Field Elements, and Robots come to rest.
b. The determination of any Autonomous Win Point(s) will occur for all Matches immediately after the Autonomous Period after all Balls, Field Elements, and Robots come to rest.
Field Element tolerances may vary from nominal by ±1.0”, unless otherwise specified. Ball tolerances and weights may vary from nominal to±0.10” and 20 grams respectively. Ball placement at the beginning of Matches may vary from nominal to±1.5”. Teams are encouraged to design their Robots accordingly. Please make sure to check Appendix A for more specific nominal dimensions and tolerances
Note: The field perimeter must always be resting upon the Field Perimeter Rubber Feet, regardless of whether or not the tabs have been cut from the foam field tiles.
Match Replays, i.e. playing a match over again from its start, are at the discretion of the Event Partner and Head Referee, and will only be issued in the most extreme circumstances listed but not limited to the following:
a. Field Fault issues that have directly affected Match play.
i. Game Elements not in the correct positions
ii. Tape lines lifting
iii. Field Elements detaching or moving beyond normal tolerances that is not a result of team play
violations.
iv. Autonomous Period or Driver Controlled Period ending early
v. Field Control disconnecting and disabling Robots. Not to be confused with a Robot that trips its
own PTC and has to reboot to reconnect the robot to controller, or teams with controllers that
have bent pins that affect only their alliance Field Control tower.
b. Game Rule issues that affect the outcome of a match. i. Referee disables a robot for a misinterpretation of a rule violation. ii. Referee starts the Driver Controlled Period without determining the outcome of the Autonomous winner. iii. The field is reset before a score is determined.
All rules in this manual are subject to change on the following dates: May 25, 2020, August 17, 2020, December 1, 2020, and March 26, 2021 . Each version is official and must be used in official VRC events until the release of the newest version making the previous version void. Areas of focus for each update are as follows:
a. The May update will include rule changes from input from the community that post questions and responses on the official Q&A.
b. The August update will include rule changes to improve game play from early season events along with input from the community that post questions and responses on the official Q&A.
c. The December update will include clarifications that were posted on the official Q&A.
d. The March update will be specific to the VEX World Championship.
All Teams must adhere to all VEX Robotics Competition rules as written in this Game Manual, and must abide by any stated intent of these rules. Officially registered Teams have the opportunity to ask for official rule interpretations in the VEX Robotics Competition Question & Answer system. All responses in this system must be treated as official rulings from the VEX Robotics Competition Game Design Committee (GDC), and they represent the correct and official interpretation of the VEX Robotics Competition Rules.
Previous Definitions, Rules and Rulings found in documents and Q&A’s from previous seasons do not apply to the current game. If clarification is needed, the question should be asked on the current Q&A.
The 2020 - 2021 Q&A is the ONLY official source for rulings besides the Game Manual. If there are any conflicts between the Game Manual and other supplemental materials (e.g. Referee Training videos, VRC Hub app, etc), the most current version of the Game Manual takes precedent.
The VRC Q&A system can be found at https://www.robotevents.com/VRC/2020-2021/QA
Prior to the start of each Match, the Robot must be placed such that it is:
a. Contacting their Home Zone
b. Not contacting the gray foam field tiles outside of the Alliance’s Home Zone.
c. Not contacting any Balls other than the Preload.
d. Not contacting another Robot.
e. Contacting exactly one (1) Preload.
i. The Preload must be contacting exactly one (1) Robot.
ii. The Preload must be fully within the field perimeter.
iii. The Preload must not be breaking the vertical projection of the Goal, i.e. the Preload must not be
inside or above the Goal.
Note: If a Robot is not present for their Match, then their Preload will instead be placed in the center of the gray foam tile that is closest to the double tape line that bisects the Home Zone and is opposite the half of the Home Zone from the placed Robot as shown below.
Figure 13: Example of a placed Robot with Preload, and one Preload correctly placed for a non-present Robot.
During the Autonomous Period, Robots may not contact the foam tiles or Balls which are on the opposing Alliance’s side of the Autonomous Line. Robots may not contact the Goals that are in the opposing Alliance’s Home Zone.
Violations of this rule will result in the Autonomous Bonus being awarded to the opposing Alliance. Intentional, strategic, or egregious violations, such as intentional contact with an opposing Robot while completely across the Autonomous Line, will result in a Disqualification.
Note: The three (3) Goals contacting the Autonomous Line are not considered to be on either side, and may be utilized by either Alliance during the Autonomous Period. If attempting to utilize these Goals, Teams should be cognizant of the possibility that opponent Robots may attempt to do the same. <SG7>, <G10>, <G11>, and <G12> will be taken into account when these types of Robot interactions
Balls that start fully on one side of the Autonomous Line may not contact the foam tiles on the opposite side of the Autonomous Line during the Autonomous Period.
Incidental violations of this rule and have no impact on the opposing Alliance will result in a Warning. Violations of this rule that affect the opposing Alliance’s autonomous routine will result in the Autonomous Bonus being awarded to the opposing Alliance. Examples of affecting the opposing Alliance could include, but are not limited to, a Ball moving another Ball or getting in the path of a Robot.
Note: Balls that start on the Autonomous Line are not included in this rule.
Robots may not intentionally drop or place Game Objects on an opponent Robot.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Balls that are Scored may not be lifted by any means such that the Ball goes above the top edge of the Goal.
It is expected that while removing Balls from the bottom of the Goal, this may cause the top Ball to momentarily go above the top edge of the Goal. This would not be a violation of this rule and is considered to be normal game play.
If the Match ends while a Robot is removing a Ball from the bottom of the Goal that contains three (3) Balls and the top Ball remains partially above the top edge of the Goal, that Ball will be considered Scored and no penalty to the Team will be assessed.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Figure 14: If this situation occurs at the end of a Match, this Goal would still be Owned by the Blue Alliance, and the top-most Ball would be Scored, even though it is not completely within the upper edge of the Goal. No penalty is assessed to the Red Alliance.
Teams may not intentionally remove Balls from the field. While Balls may accidentally leave the field when attempting to Score, doing so intentionally or repeatedly would be a violation of this rule. Balls that leave the field during Match play, intentionally or unintentionally, will be returned to the field at the location nearest the point at which they exited. Referees will return the Balls to the field when it is deemed safe to do so, at the leisure of the referee.
Minor violations of this rule that do not affect the Match will result in a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
Balls may not be used to accomplish actions that would be otherwise illegal if they were attempted by Robot mechanisms (e.g., Interfering with an opponent’s Autonomous Period per <SG2>.)
The intent of this rule is to prohibit teams from using game objects as “gloves” to loophole any rule that states “a Robot may not [do some action]”. This rule is not intended to be taken in its most extreme literal interpretation, where any interaction between a Ball and a Robot needs to be scrutinized with the same intensity as if it were a Robot.
Robots may not have greater-than-momentary Possession of more than three (3) Balls of its opposing Alliance’s color at once. When two Robots from the same Alliance are working in tandem and blocking Balls, those Robots may not Possess a total of more than six (6) Balls of its opposing Alliance’s color at once.
Robots that violate this rule must stop all Robot actions except for those actions that are attempting to remove the excess Ball.
Minor violations of this rule that are not Match Affecting will receive a warning. Match Affecting offenses will result in a Disqualification. Teams that receive multiple warnings may also receive a Disqualification at the Head Referee’s discretion.
The intent of this rule is to prohibit each Robot from keeping more than 3 of the opposing Balls from being used by the opposing Alliance. It is anticipated that two Robots from the same Alliance will work together to Possess the opposing Alliance’s Balls. When those Robots do this, as long as they are not Possessing more than 6 of the Opposing Alliance’s Balls in total, and each Robot is not carrying or controlling more than 3 Balls, these Robots are not in violation of <SG8>.
Only one (1) Robot will be allowed to compete per Team in the VEX Robotics Competition. Though it is expected that Teams will make changes to their Robot at the competition, a Team is limited to only one (1) Robot. As such, a VEX Robot, for the purposes of the VEX Robotics Competition, has the following subsystems:
Given the above definitions, a minimum Robot for use in any VEX Robotics Competition event (including Skills Challenges) must consist of 1 and 2 above. Thus, if you are swapping out an entire subsystem of either item 1 or 2, you have now created a second Robot and are no longer legal.
a. Teams may not compete with one Robot while a second is being modified or assembled.
b. Teams may not have an assembled second Robot to be used to repair or swap parts to the first Robot.
c. Teams may not switch back and forth between multiple Robots during a competition. This includes using different Robots for Skills Challenge, Qualification and/or Elimination Matches.
d. Multiple Teams may not use the same Robot. Once a Robot has competed under a given team number at an event, it is “their” Robot - no other Teams may compete with it for the duration of the competition season.
The intent of <R1a>, <R1b>, and <R1c> are to ensure an unambiguous level playing field for all Teams. Teams are welcome (and encouraged) to improve or modify their Robots between events, or to collaborate with other Teams to develop the best possible game solution.
However, a Team who brings and/or competes with two separate Robots at the same tournament has diminished the efforts of a Team who spent extra design time making sure that their one Robot can accomplish all of the game’s tasks. A multi-Team organization that shares a single Robot has diminished the efforts of a multi-Team organization who puts in the time, effort, and resources to undergo separate individual design processes and develop their own Robots.
To help determine if a Robot is a “separate Robot” or not, use the Subsystem definitions found in <R1>. Above that, use common sense as referenced in <G3>. If you can place two Robots on a table next to each other, and they look like two separate legal/complete Robots (i.e. each have the 3 Subsystems defined by <R1>), then they are two Robots. Trying to decide if changing a screw, a wheel, or a microcontroller constitutes a separate Robot is missing the intent and spirit of this rule.
The Robot must be designed, built and programmed by members of the Team. Adults are permitted to mentor and teach design, building and programming skills to the Students on the Team, but may not design, build or program that team’s Robot
In VRC, we expect Adults to teach different linkages, drive-trains, and manipulator applications to the Students, then allow the Students to determine which designs to implement and build on their Robot. Adults are encouraged to teach the Students how to code various functions involving applicable sensors, then have the Students program the Robot from what they have learned.
Every Robot will be required to pass a full inspection before being cleared to compete. This inspection will ensure that all robot rules and regulations are met. Initial inspections will take place during team registration/practice time.
a. Significant changes to a Robot, such as a partial or full swap of Subsystem 3, must be re-inspected before the Robot may compete again.
b. All possible functional Robot configurations must be inspected before being used in competition.
c. Teams may be requested to submit to random spot-inspections by event personnel. Refusal to submit will result in Disqualification.
d. Robots which have not passed inspection (i.e. who are in violation of one or more Robot rules) will not be permitted to play in any Matches until they have done so. <T3> will apply to any Matches that occur until the Robot has passed inspection.
e. If a Robot has passed inspection, but is later found to be in violation of a Robot rule during a Match, then they will be Disqualified from that Match and <R2d> will apply until the violation is remedied and the Team is re-inspected.
The intent of this rule is to ensure that teams play Matches with legal Robots. If a Robot is determined to not be legal before the Match starts, the Robot will be removed from the field and a Drive Team member must remain so that the Team does not get assessed a “no-show”. If the Match is played with an illegal Robot on the Field, that Team will receive a Disqualification for the Match (see <T11>).
The following types of mechanisms and components are NOT allowed:
a. Those that could potentially damage Field Elements or Balls.
b. Those that could potentially damage other competing Robots.
c. Those that pose an unnecessary risk of Entanglement.
Robots must fit in a sizing box. At the beginning of any Match, Robots must be smaller than 18” (457.2 mm) long by 18” (457.2 mm) wide by 18” (457.2 mm) tall.
a. Robots may expand beyond their starting size constraints after the start of a Match.
b. Any restraints used to maintain starting size (i.e. zip ties, rubber bands, etc.) MUST remain attached to the Robot for the duration of the Match.
Robots may be measured by either being placed in a “sizing box” with interior dimensions matching the above size constraints or by using the VEX Robotics Competition Robot Sizing Tool while the Robot is placed on a flat surface. A Robot may not touch the box walls or ceiling or the Robot Sizing Tool sides when being measured.
There are two VEX Robotics Competition Robot Sizing Tools that may be used:
https://www.vexrobotics.com/276-2086.html and https://www.vexrobotics.com/276-5942.html
Robots may be built ONLY using official VEX V5 and Cortex components, unless otherwise specifically noted within these rules. Teams are responsible for providing documentation proving a part’s legality in the event of a question. Examples of documentation include receipts, part numbers, official VEX websites, or other printed documentation.
a. Products from the VEXpro, VEX IQ, or VEX Robotics by HEXBUG product line cannot be used for Robot construction, unless specifically allowed by a clause of <R7> or cross-listed as part of the VEX V5 or Cortex Product lines. For example, the Rubber Shaft Collar (228-3510) is a VEX IQ component that can be found on the VEX “Shafts & Hardware” page, and is thus legal: https://www.vexrobotics.com/shafts-and-hardware.html
b. VEX IQ pins used solely for the purpose of attaching VEX Team Identification Number Plates are permitted.
c. Official VEX V5 and Cortex components which have been discontinued are still legal for competition use. Teams must be cognizant of <R6> if attempting to use a discontinued part.
d. Any parts which are identical to legal VEX parts are permitted. For the purposes of this rule, products which are identical in all ways except for color are permissible. It is up to inspectors to determine whether a component is “identical” to an official VEX component.
e. Components obtained from the V5 beta program, including V5 beta firmware, are not legal for competition use.
i. All V5 beta hardware can be identified by its lighter gray pre-production color. Robot Brains, Robot Batteries, Controllers, and Vision Sensors from the V5 beta have a “BETA TEST” stamp on them. Smart Motors and Radios do not have this stamp, but can still be identified by color.
Using VEX apparel, competition support materials, packaging, or other non-robot products on a VEX Robotics Competition Robot goes against the spirit of this rule and is not permitted.
Official VEX products are ONLY available from VEX Robotics & official VEX Resellers. To determine whether a product is “official” or not, consult www.vexrobotics.com. A complete list of authorized VEX Resellers can be found at https://www.vexrobotics.com/how-to-order.
Robots are allowed the following additional “non-VEX” components:
a. Any material strictly used as a color filter or a color marker for a VEX Light Sensor.
Any non-aerosol based grease or lubricating compound, when used in extreme moderation on surfaces and locations that do NOT contact the playing field walls, foam field surface, Balls, or other
Robots.
c. Anti-static compound, when used in extreme moderation (i.e. such that it does not leave residue on playing field walls, the foam field surface, Balls, or other Robots).
d. Hot glue when used to secure cable connections.
e. An unlimited amount of 1/8” (or local metric equivalent), braided, nylon rope.
f. Commercially available items used solely for bundling or wrapping of 2-wire, 3-wire, 4-wire, or V5 Smart Cables, and pneumatic tubing are allowed. These items must solely be used for the purposes of cable protection, organization, or management. This includes but is not limited to electrical tape, cable carrier, cable track, etc. It is up to inspectors to determine whether a component is serving a function beyond protecting and managing cables.
Non-functional 3D printed license plates, per <R13> and <R27>, are permitted.
The V5 Radio or VEXnet Key 2.0 must be mounted such that no metal surrounds the radio symbol on the V5 Radio or touches the VEXnet logo on the VEXnet Key 2.0.
Teams may use a USB extension cable for the sole purpose of remote mounting of a VEXnet Key 2.0 to a VEX ARM® Cortex®-based Microcontroller
It is fine to loosely encapsulate the V5 Radio or VEXnet Key 2.0 in Robot structure. The intent of this rule is to minimize radio connection issues by minimizing obstructions between VEXnet devices. If a radio is buried in a Robot, VEXnet is not able to connect as well and may result in Robot communication issues.
Robots may use non-shattering plastic from the following list; polycarbonate (Lexan), acetal monopolymer (Delrin), acetal copolymer (Acetron GP), POM (acetal), ABS, PEEK, PET, HDPE, LDPE, Nylon (all grades), Polypropylene, FEP; as cut from a single 12” x 24” sheet up to 0.070” thick.
a. Shattering plastic, such as PMMA (also called Plexiglass, Acrylic, or Perspex), is prohibited.
b. Plastic may be mechanically altered by cutting, drilling, bending etc. It cannot be chemically treated, melted, or cast. Heating polycarbonate to aid in bending is acceptable.
Robots may use a small amount of tape when used for the following purposes:
a. For the sole purpose of securing any connection between the ends of two (2) VEX cables.
b. For labeling wires and motors.
c. For covering the back of License Plates (i.e. the “wrong color”).
d. For the purposes of preventing leaks on the threaded portions of pneumatic fittings. This is the only acceptable use of Teflon tape.
e. For securing and retaining a VEXnet Key 2.0 to the VEX ARM® Cortex®-based Microcontroller. Using tape in this manner is highly recommended to ensure a robust connection.
f. In any other application that would be considered a “non-functional decoration” per <R13>.
Robots may use any commercially available #4, #6, #8, M3, M3.5, or M4 screw up to 2” (50.8mm) long (nominal), and any commercially available nut, washer, and/or spacer (up to 2” / 50.8mm long) to fit these screws.
The intent of the rule is to allow teams to purchase their own commodity hardware without introducing additional functionality not found in standard VEX equipment. It is up to inspectors to determine whether the non-VEX hardware has introduced additional functionality or not.
Teams may add non-functional decorations, provided that they do not affect Robot performance in any significant way or affect the outcome of the Match. These decorations must be in the spirit of the competition. Inspectors will have final say in what is considered “non-functional”. Unless otherwise specified below, non-functional decorations are governed by all standard Robot rules. In order to be “non-functional,” any guards, decals, or other decorations must be backed by legal materials that provide the same functionality. For example, if your Robot has a giant decal that prevents Balls from falling out of the Robot, the decal must be backed by VEX material that would also prevent the Balls from falling out.
a. Anodizing and painting of parts is considered a legal nonfunctional decoration.
b. If using the VEX speaker (276-1504), the chosen audio must not be distracting and must be in good taste. The Head Inspector and Head Referee will make the final decision on the appropriateness of the audio.
c. Small cameras are permitted as non-functional decorations, provided that any transmitting functions or wireless communications are disabled. Unusually large cameras being used as ballast are not permitted.
d. VEX electronics may not be used as non-functional decorations.
e. Decorations that visually mimic field elements or could otherwise interfere with an opponent’s Vision Sensor are considered functional and are not permitted. This includes lights, such as the VEX Flashlight. The Head Inspector and Head Referee will make the final decision on whether a given decoration or mechanism violates this rule.
f. Internal power sources (e.g. for a small blinking light) are permitted, provided that no other rules are violated and this source only provides power to the non-functional decoration (e.g. does not directly or indirectly influence any functional portions of the Robot).
g. Decorations which provide feedback to the Robot (e.g. by influencing legal sensors) or to Drive Team Members (e.g. status indicators) would be considered “functional” and are not permitted.
The Vision Sensor must have its wireless transmitting functionality disabled.
Additional VEX components released during the competition season on www.vexrobotics.com are considered legal for use.
Some “new” components may have certain restrictions placed on them upon their release. These restrictions will be documented in the official Q&A forums, in a Game Manual Update, or on their respective product web pages.
Robots must ONLY use one (1) VEX V5 Robot Brain (276-4810), or one (1) VEX ARM ® Cortex ®-based Microcontroller (276-2194).
a. Any other microcontrollers or processing devices are not allowed, even as non-functional decorations. This includes microcontrollers that are part of other VEX product lines, such as VEXpro, VEX RCR, VEX IQ, VEX GO, or VEX Robotics by HEXBUG; this also includes devices that are unrelated to VEX, such as Raspberry Pi or Arduino devices
Robots must ONLY utilize the VEXnet system for all Robot communication.
a. VEX 75Mhz Crystal Radios are prohibited. (Some events may allow the use of 75Mhz Crystal Radios, please see the Special Event Rule Modifications later in this section.)
b. Electronics from the VEXpro, VEX RCR, VEXplorer, VEX IQ, VEX GO, or VEX Robotics by HEXBUG product line are prohibited.
c. Mixing and matching of VEXnet transmitters and receivers is prohibited. The VEXnet Joystick may only be used in conjunction with a VEX ARM® Cortex®-based Microcontroller. A VEXnet upgraded 75MHz Transmitter may only be used in conjunction with a PIC Microcontroller. A V5 Controller may only be used in conjunction with a V5 Robot Brain.
Teams are permitted to use the Bluetooth® capabilities of the V5 Robot Brain and/or V5 Controller in team pits or outside of Matches. However, VEXnet must be used for wireless communication during Matches.
Robots may use exactly one (1) of the following four (4) options:
a. 2-Wire Motors must be controlled by a 2-Wire Motor Port, either directly on a VEX microcontroller, or on a VEX Motor Controller 29 module (276-2193).
b. Teams may NOT use multiple 2-wire Motor Ports, 3-wire PWM Motor Ports, or Motor Controller 29 modules on a single motor. V5 Smart Motors, connected to Smart Ports, are the only motors that may be used with a V5 Robot Brain. The 3-wire ports may not be used to control motors of any kind.
Table 1: The four combinations of control system, motors and pneumatics that are legal
If using a VEX ARM Cortex-based Microcontroller, a maximum of one (1) VEX Y-cable can be used per Motor Port of the Microcontroller or Power Expander, i.e. you cannot “Y off a Y” to have more than two (2) motors controlled by the same Motor Port.
a. Teams using the VEX ARM® Cortex®-based Microcontroller may only power one (1) 2-wire Motor per each of the two 2-wire motor ports on the Microcontroller. It is illegal to “Y” off a 2-wire Motor Port.
b. Teams may not “Y” off of a Motor Controller 29 (276-2193)
The only allowable source(s) of electrical power are as follows:
a. If using a VEX ARM® Cortex®-based Microcontroller, robots may use (1) VEX 7.2V Robot Battery Pack of any type.
i. Robots utilizing the VEX Power Expander may use a second VEX 7.2V Robot Battery of any type. Robots are permitted to use a maximum of one (1) VEX Power Expander.
ii. The only legal means for charging a VEX 7.2V Battery Pack is via one of the following VEX Battery Chargers: Smart Charger (276-1445); Smart Charger v2 (276-2519); 276-2221 (discontinued), 276-2235 (discontinued). All other chargers are strictly prohibited.
iii. Teams must connect a charged 9V backup battery to their VEXnet system using the VEXnet Backup Battery Holder (276-2243).
iv. VEXnet Joysticks must only be powered by AAA batteries.
v. Some events may provide field power for VEXnet Joysticks. If this is provided for all Teams at the event, this is a legal source of power for VEXnet Joysticks. Table 1: The four combinations of control system, motors and pneumatics that are legal
b. If using a V5 Robot Brain, robots may use (1) V5 Robot Battery (276-4811).
i. There are no legal power expanders for the V5 Robot Battery.
ii. V5 Robot Batteries may only be charged by the V5 Robot Battery Charger (276-4812).
iii. V5 Wireless Controllers may only be powered by their internal rechargeable battery.
c. Teams are permitted to have an external power source (such as a rechargeable battery pack) plugged into their V5 Controller during a Match, provided that this power source is connected safely and does not violate any other rules, such as &tl;G8> or <R22>.
Table 2: The legal sources of electrical power for Robots
No more than two (2) VEX wireless remotes may control a single Robot during the tournament.
a. No modification of these transmitters is allowed of ANY kind.
b. No other methods of controlling the Robot (light, sound, etc) are permissible.
i. Using sensor feedback to augment driver control (such as motor encoders or the Vision Sensor) is acceptable.
c. Teams may not “mix-and-match” wireless remote types, such as using a VEXnet Joystick and V5 Controller at the same time.
Motors (including the internal PTC or Smart Motor firmware), microcontrollers (including V5 Robot Brain firmware), extension cords, sensors, controllers, battery packs, reservoirs, solenoids, pneumatic cylinders, and any other electrical component or pneumatics component of the VEX platform may NOT be altered from their original state in ANY way.
a. External wires on VEX electrical components may be repaired by soldering, using twist/crimp connectors, electrical tape or shrink tubing such that the original functionality / length is not modified in any way. Wire used in repairs must be identical to VEX wire. Teams may make these repairs at their own risk; incorrect wiring may have undesired results.
b. Teams must use the latest official VEXos firmware updates, found at www.vexrobotics.com. Custom firmware modifications are not permitted.
c. Teams may change or replace the gears in the “2-Wire 393” or “2-Wire 269” motors with the corresponding official VEX Replacement Gears.
d. Teams may change or replace the gear cartridge in the V5 Smart Motor with other official replacement gear cartridges.
Physical modifications such as bending or cutting are permitted and may be done to legal VEX Robotics Competition metal structure or plastic components.
a. Physical modifications to electrical components such as a legal microcontroller or radio is prohibited unless otherwise explicitly permitted, per
b. Internal or external mechanical repairs of VEX Limit and Bumper switches are permitted. Modifying the metal arm on the Limit Switch is permitted. Using components from these devices in other applications is prohibited.
c. Metallurgical modifications that change fundamental material properties, such as heat treating, are not permitted.
d. Teams may cut pneumatic tubing to a desired length.
e. Teams are permitted to fuse/melt the end of the 1/8” nylon rope to prevent fraying.
f. Welding, soldering, brazing, gluing, or attaching in any way that is not provided within the VEX platform is NOT permitted.
The Robot on/off switch or button must be accessible without moving or lifting the Robot. All microcontroller lights and/or screens must also be easily visible by competition personnel to assist in diagnosing Robot problems.
Pneumatic devices may only be charged to a maximum of 100 psi. Teams may only use a maximum of two (2) legal VEX pneumatic air reservoirs on a Robot.
The intent of this rule is to limit Robots to the air pressure stored in two reservoir tanks, as well as the normal working air pressure contained in their pneumatic cylinders and tubing on the Robot. Teams may not use other elements (e.g. surgical tubing) for the purposes of storing or generating air pressure. Teams who use cylinders and additional pneumatic tubing for no purpose other than additional storage are in violation of the spirit of this rule and will fail inspection.
To participate in an official VEX Robotics Competition (VRC) event, a Team must first register on robotevents.com. Upon registering they will receive their VRC Team Number and four (4) VRC License Plates. Teams may choose to use the VRC License Plate Kit that comes in the VRC Team Welcome Kit, or may create their own, including one made from 3D printed parts. Plates must follow the following requirements.
a. Robots must use the colored plates that match their Alliance color for each Match (i.e. red Alliance Robots must have their red plates on for the Match). It must be abundantly clear which color Alliance the Robot belongs to.
Note: If the plates are attached to opposite-color plates, then the incorrect color must be covered, taped over, or otherwise obscured to ensure that the correct Alliance color is abundantly clear to Head Referees during a Match. Since License Plates are considered non-functional decorations, this is a legal non-functional use of tape.
b. License Plates must fulfill all Robot rules (i.e. they must fit within the 18” cube per <R4>, they cannot cause entanglement, not functionally change the stability of rigidity of the Robot, etc.)
c. Plates must be at least 2.48 inches (63.2mm) tall and 4.48 inches (114mm) wide, i.e. at least the size of the plates in the VRC License Plate Kit ignoring thickness.
The intent of this rule is to make it very easy for Head Referees to know which Alliance and which Team each Robot belongs to. Being able to “see through” a Robot arm to the wrong color License Plate on the opposite side of the Robot would be considered a violation of <R27a>.
It will be at the full discretion of the Head Referee and inspector at a given event to determine whether a given custom license plate satisfies the criteria listed in <R27>. Teams wishing to utilize custom plates should be prepared for the possibility of this judgment, and ensure that they are prepared to replace any custom parts with official VEX License Plates if requested. Not bringing official replacement plates to an event will not be an acceptable reason for overlooking a violation of one or more points in <R27>.
The Robots must be programmed to follow control directions provided by the VEXnet Field Controllers.
During the Autonomous Period, Drive Team Members will not be allowed to use their hand-held controllers. As such, Teams are responsible for programming their Robot with custom software if they want to perform in the Autonomous Period. Robots must be programmed to follow control directions provided by the VEXnet Field Controllers (i.e. ignore wireless input during the Autonomous Period, disable at the end of the Driver Controlled Period, etc).
Teams must use a provided “competition template”, or functional equivalent, to accomplish this. All Robots will be required to pass a functional enable/disable test as part of inspection. For more information on this, Teams should consult the help guides produced by the developers of their chosen programming software.
Any violation of Robot rules will result in a Team being unable to play until they pass inspection (per <R3d>). In addition, Teams who intentionally or knowingly circumvent or violate rules to gain an advantage over their fellow competitors are in violation of the spirit and ethos of the competition. Any violation of this sort may be considered a violation of <G1> and/or the REC Foundation Code of Conduct.
Some events may choose to make the following rule exceptions to fit their unique circumstances:
a. Utilize the VEX 75 MHz Crystal Radio Transmitter & Receiver instead of or in conjunction with the VEXnet Wireless link.
b. Allow AA batteries to power the robot instead of a VEX 7.2V Battery Pack.
Note: If an event makes these changes, they must inform all attending Teams. It is especially important that any 75 MHz events make sure their Teams are using the correct communication type.
Anyone who is not a student
A pre-assigned grouping of two (2) Teams that are paired together during a given Match.
The three (3) Goals in each Alliance’s Home Zone
The designated region where the Drive Team Members must remain for the duration of the Match
A point bonus of six (6) points awarded to the Alliance that has earned the most points at the end of the Autonomous Period
Note: If the Autonomous Period ends in a tie, including a zero-to-zero tie, each Alliance will receive an Autonomous Bonus of three (3) points.
The pair of white tape lines that run across the center of the field. Per <SG2>, Robots may not contact the foam field tiles on the opposite Alliance’s side of the Autonomous Line during the Autonomous Period.
A hollow plastic spherical-shaped, dimpled object, with a diameter of 6.3” (160mm), that can be Scored in Goals.
The Student(s) on the Team who assemble(s) the Robot. An Adult cannot be the Builder on a Team. Adult are permitted to teach the Builder associated concepts, but may never be working on the Robot without the Builder present and actively participating.
A Row where all three (3) Goals in the Row are Owned by the same Alliance.
The Student(s) on the Team who design(s) the Robot to be built for competition. An Adult cannot be the Designer on a Team. Adults are permitted to teach the Designer associated concepts, but may never be working on the design of the Robot without the Designer present and actively participating.
A penalty applied to a Team for a rule violation. A Team that is Disabled is not allowed to operate their Robot for the remainder of the Match, and the Drive Team Members will be asked to place their controller(s) on the ground.
A penalty applied to a Team for a rule violation. A Team that is Disqualified in a Qualifying Match receives zero (0) Win Points, Autonomous Win Point, Autonomous Points, and Strength of Schedule Points. When a Team is Disqualified in an Elimination Match, the entire Alliance is Disqualified and they receive a loss for the Match. At the Head Referee’s discretion, repeated violations and Disqualification for a single Team may lead to its Disqualification for the entire tournament. (see <T11>)
The Student who stand in the Alliance Station during a Match for each Team per <G7> . Only Drive Team Members are permitted to stand in the Alliance Station and allowed to touch the controls during the Match or interact with the Robot as per <G9>. Adults are not allowed to be Drive Team Members.
The Student who stand in the Alliance Station during a Match for each Team per <G7>. Only Drive Team Members are permitted to stand in the Alliance Station and allowed to touch the controls during the Match or interact with the Robot as per <G9>. Adults are not allowed to be Drive Team Members.
A Robot status. A Robot is Entangled if it has grabbed, hooked, or attached to an opposing Robot or a Field Element.
The foam field tiles, field perimeter, white tape, Goal, and all supporting structures or accessories (such as driver station posts, field monitors, etc).
One of nine (9) cylinders in which Robots can Score and remove Scored Balls. The Goals are all 18.41” (467.6mm) tall and have an inside diameter of 7.02” (178.3mm). The Goal consists of four (4) retaining rings and four (4) PVC pipes. The outer edge of the ring is considered to be the outer edge of the Goal. The upper edge of the top ring is considered to be the upper edge of the Goal.
Figure 6: Close-up of a Goal, depicting the outer and upper edges of the Goal
One of two (2) areas, one (1) for each Alliance, where Robots start the match and defines the location of the Alliance Home Row. The Home Zones are defined by the inner edges of the field perimeter and the outer edge of the tape line that runs across the field adjacent to the Alliance Station, i.e. the tape line is part of the Home Zone. The Alliance Home Zone is closest to their Alliance Station
The Home Zone refers to the foam field tiles; it is not a 3-dimensional volume.
Figure 7: Top view of the field, with the Home Zone highlighted
A Match consists of an Autonomous Period followed by a Driver Controlled Period for a total time of two minutes (2:00).
A rule violation status determined by the head referee. A rule violation is Match Affecting if it changes the winning and losing Alliances in the Match. Multiple rule violations within a Match can cumulatively become Match Affecting.
A Goal status. A Goal is considered Owned by an Alliance if its colored Ball is the vertically highest Scored Ball in that Goal.
Figure 8: This Goal is Owned by the blue Alliance, as the top-most Ball is completely within the upper edge of the Goal.
Figure 9: This Goal is owned by the Red Alliance, as the top-most Ball is not completely within the upper edge of the Goal. The top red Ball is Scored because it is below the upper edge of the Goal
Figure 10: This Goal is owned by the Blue Alliance, as the top-most Ball is not completely within the upper edge of the Goal. The two bottom-most Balls would both be considered Scored, as they are partially within the outer edge of the Goal
A Robot is considered to be Possession a Ball if a Ball is in an unscored position and either of the following criteria are met:
Note: Balls that are Scored in Goals cannot be considered Possessed until the Robot removes the Ball from that Scored position and is carrying, holding, controlling or guarding that Ball.
The Ball, one (1) per Robot, that must be placed on the field such that it satisfies the conditions in <SG1> prior to the start of the Match.
Note: The red Alliance always uses red Balls as their Preloads. The blue Alliance always uses blue Balls as their Preloads
The Student(s) on the Team who write(s) the computer code that is downloaded onto the Robot. An Adult cannot be the Programmer on a Team. Adults are permitted to teach the Programmer associated concepts, but may never be working on the code that goes on the Robot without the Programmer present and actively participating.
A machine that has passed inspection, designed to execute one or more tasks autonomously and/or by remote control from a human operator.
Three (3) Goal that make up a straight line. There are a total of eight (8) Rows including two (2) Alliance Home Row.
A Ball status. A Ball is considered Scored in a Goal if it is not touching a Robot of the same color as the Ball and meets all of the following criteria.
Note: In the act of removing a Ball from the bottom of a Goal with three Scored Balls inside, it is possible for the top Ball to momentarily break criteria 2 above. If this occurs at the end of the Match, this Ball should still be considered Scored. The intent of this note is to avoid unintended de-scoring via the top of the Goal. The intent is not to encourage Teams to seek unique scenarios that would not typically be considered Scored. This would be considered a violation of rule <SG5>.
Figure 12: Close-up of a Goal, depicting the volume in which a Ball would be considered Scored
A person is considered a Student if he or she meets both of the following criteria:
One or more Student make up a Team. A Team is classified as a Middle School Team if all members are Middle School Students. A Team is classified as a High School Team if any of its members are High School Student, or made up of Middle School Students who declare themselves “playing up” as High School Students by registering their Team as a High School Team.
Once declared and playing as a High School Team, that Team may not change back to a Middle School Team for the remainder of the season. Teams may be associated with schools, community/youth organizations, or a group of neighborhood Students.
A Robot status. A Robot is Trapping if it has restricted an opposing Robot into a small, confined area of the field, approximately the size of one foam field tile or less, and has not provided an avenue for escape. Trapping can be direct (e.g. pinning an opponent to a field perimeter wall) or indirect (e.g. preventing a Robot from escaping from a corner of the field).
Note: If a Robot is not attempting to escape, that Robot has not been Trapped.


Select the policy you want to know about Bar Closures Emergency Declaration Face Covering Requirement Large Gatherings Ban Mandatory Quarantine for Travelers Primary Election Postponement Restaurant Limits School Closures Status of Reopening Non-Essential Business Closures Stay at Home Order
If you can see this, your browser does not support iframes!


Upset Alert: No. 6 Oregon Is In Trouble Tonight
by Alek ArendNo. 6 Oregon is the Pac-12’s College Football Playoff hopeful. But the Ducks are in serious jeopardy of being eliminated from playoff contention.
Arizona State has put together a brilliant game-plan, keeping the Ducks’ defense on its heels en route to a 13-7 lead in the third quarter.
As for the Ducks, they’ve been able to run the football effectively as RB CJ Verdell has 15 carries for 85 yards so far. But questionable play-calling has killed any momentum Oregon has garnered.
QB Justin Herbert has had a horrible night thus far. Oregon’s signal-caller has completed 10-of-20 passes for 127 yards. He hasn’t thrown any picks yet, but he’s made plenty of questionable decisions resulting in near-turnovers.
This is one of the first times all season Herbert and this Oregon offense has been unable to find a spark. The Ducks might eliminate themselves from a potential CFP selection if they can’t mount a late comeback.
ASU QB Jayden Daniels is playing beyond his years tonight. The freshman QB has nearly 300 passing yards and a touchdown.
Can Herbert find a groove and get the offense going? Or will the Sun Devils spoils Oregon’s post-season aspirations?
You can catch the rest of the Oregon-Arizona State contest on ABC.