Please enable JavaScript.
Coggle requires JavaScript to display documents.
Rules, Rev. 1. 202311, system track - Coggle Diagram
Rules, Rev. 1. 202311, system track
Quick notes
The DARPA Triage Challenge Chief Judge has the final authority to make any decisions related to the rules or scoring. All decisions made by the Chief Judge are final.
-
Competitors agree they will not attempt to re-identify, share, or re-use Army/TATRC data as provided by DARPA
Timeline
Year 1
Workshop is at Month 8, for 6 days
Challenge is at Month 12, for 7 days, + 1 day of awards/lessons-learned
-
-
-
Event qualification
-
For workshop 1, the event qualification date is March 5th, 2024
Scenario
-
Stand-off, autonomous, and time limit
Autonomously process sensor data and provide real-time casualty identification and injury assessment
No part of a competitor's system may touch a casualty or manipulate the scene (e.g., clear rubble)
-
Technical challenges
Lots of targeted challenges listed in Section 9.2, including degraded sensing, obscuring obstacles, terrain obstacles, dynamic obstacles, dynamic casualties, and endurance limits.
-
Courses
Two themes for challenge 1, year 1
-
-
year 1
-
-
pavement, grass or gravel
Obstacles: small piles of rublle, buildings, vechiles
-
-
-
Interface Control Document (IDC) and reference implementation will be posted on the DTC website and DTC community forum
Event Operations
-
three scored runs 15-30min in duration. The total score for the event will be sum of a team's best two runs
Allow enter, exit, or reenter the course at any time within the duration of the run
-
A system may only be handled or retrieved if it has crossed back into the Staging Area past the front face of the Starting Gate.
A team may be eligible for an additional attempt if a run is canceled or stopped due to an emergency or external factor outside of the team’s control.
-
-
-
Personnel Guidelines
-
-
Pit Crew
-
-
speical roles
Safety Officers
-
-
-
-
-
-
The Safety Officer is not permitted to take control of a system that has crossed into the competition course except to trigger a Tier 1 emergency stop for the sole purpose of preserving the safety of personnel. Once triggered, the robot must stay inactive for the remainder of the competition run.
Operators
communicate with systems, teleoperate, activate safety emergency stops, access Status Data.
-
-
take off, landing, full movement.
-
Human Supervisors
-
-
-
Once a team’s run has begun, the Human Supervisors may not be substituted with other personnel.
-
-
-
Base Station can provide limited status data to the Pit Cress via a wired display to suport operation tasks such as calibration, startup check.
:warning: Pit Crew is not permitted to directly interface with the Base Station in any way (e.g., toggling between windows via peripherals).
Limite Status Data: battery health, network status, real-time telemetry
-
-
System
System constraints
-
-
-
-
Platforms must not produce any visible illumination other than what is legally required for UAV flight.
-
-
sensor constraints
All audio communication must be autonomous: no human communication is permitted between teams and casualties.
-
System Retrieval
It is encouraged but not required for the deployed systems to return to the Staging Area at the end of the run
Teams are encouraged to provide audible and visual recovery aids such as flashing LEDs and audible cues to help Competition Staff locate deployed systems or components.
-
-
Emergency Stop
-
-
On-Platform E-Stop
Teams must integrate at least one emergency stop button on each platform that weighs more than 10 kg
-
-
:question: can a UAV autonomously pick the emergency landing location? Or quicly gain altitude above 30m?
Qulification
all teams are required to demonstrate emergency stop compliance to be eligible for participation in the Competition Events
-
-
-
Internet
-
:!: Team personnel in the Staging Area are not permitted to access the internet or make phone calls on any devices (e.g., cell phone, tablet) during the competition run.
Data protection
:!: Team personnel in the Staging Area are not permitted to access the internet or make phone calls on any devices (e.g., cell phone, tablet) during the competition run.
-
At the end of an event, teams will remove and clear any removable memory in the UxV
-
-
Scoring
-
-
-
-
-
-
-
Report limits
:question: How to evaluate bonus points if submit two reports for the same casualty? How to represent a partial submission?
In Phase 1 it is expected that each run will have 10-12 casualties and the total number of allowed triage reports for each run will be the number of casualties + 5.
Limits will apply separately to each field in the report, and teams will be able to get status during the run with counts of remaining reports for each field (see ICD)
-
-
