Tracks‎ > ‎

Industrial Track - Diagnostic Problem I

Diagnostic problem I mimics the use of the ADAPT-Lite system in a single-string UAS (Unmanned Aircraft System) mission. The primary objective of the diagnostic algorithm in this operational scenario is to provide decision support to a remote pilot or an autonomous controller by making an “abort" recommendation. An abort recommendation would result in aborting the mission and landing the UAS vehicle. This is the same problem as used for DXC10.

System Description
You may be confused that the system description document says "DXC10" instead of "DXC11". We are using the same problem formulation and description this year. Hence, DXC11 is a rematch of DXC10 and the write-up used last year applies without modification.

Sample Data

The sample data provided here is the competition data from Diagnostic Problem I of DXC10. Some of the scenarios may be used for DXC11. The zip file has a spreadsheet (and pdf) that lists the scenarios and relevant fault information. Each scenario is provided in three formats: tab-delimited .txt file, Matlab .mat file, and tab-delimited .scn file. The different formats are provided for your convenience; they have the same data. The scenario (.scn) files are the format read by the DXC framework. See the system catalogs and schematics for additional information.

For those involved in last year's competition, note that DXC 10 Diagnostic Problem I competition data posted last year (dated 20101105) had some problems which were fixed in the DPI sample data set posted here. The battery "AbruptParasiticLoad" scenario (Exp. 1311) was removed as it was found to have different behavior prior to fault injection than nominal scenarios. Exp 1229_015f was too short (224 seconds) and was removed. Several runs caused an issue when a value was expected to be a real but was interpreted as an integer in the framework (1251, 1285, 1316, 1323, and 1330); this has been fixed.

There will be no "AbruptParasiticLoad" faults in the DXC11 DPI competition data.