Remove all testing stuff

This commit is contained in:
2026-06-17 09:21:12 -07:00
parent 5b0e3353a7
commit ca78f1df0a
4 changed files with 81 additions and 83 deletions

View File

@@ -36,7 +36,6 @@
#include <ctime>
#include <string>
#include <mutex>
#include <vector>
/* ============================================================
* TARGET DATA STRUCTURES
@@ -109,8 +108,7 @@ struct target_data_to_thread_1_structure {
* ============================================================ */
/* Index constants for radar_management[] and current_radar.
* Slot 0 (RADAR_NONE) is the management/system entry; its testing field
* holds the system-wide test mode. Radar entries are slots 1-4. */
* Slot 0 (RADAR_NONE) is the management/system entry. Radar entries are slots 1-4. */
constexpr int RADAR_NONE = 0; // management/system entry
constexpr int RADAR_CHAIN_HOME = 1;
constexpr int RADAR_MARINE_ASCOPE = 2;
@@ -120,8 +118,7 @@ constexpr int RADAR_COUNT = 5; // total slots: 0 (management) + 1-4 (ra
/* Per-radar operational state.
* Indexed by RADAR_* constants above.
* Slot 0 (RADAR_NONE) is the management/system entry — its testing field
* holds the active TESTING_* mode for the entire exhibit.
* Slot 0 (RADAR_NONE) is the management/system entry.
* Components: Thread 1 (startup init, scope switching),
* Traffic Cop (Thread 2, range filtering) */
struct radar_management_structure {
@@ -129,14 +126,10 @@ struct radar_management_structure {
int operatable; // 1 = radar is built and fully functional, 0 = not yet built
int available; // 1 = enabled by exhibit operator at startup, 0 = disabled
int selected; // 1 = currently active/displayed, 0 = not active
int testing; // TESTING_* constant: component under development (TESTING_NONE = normal operation)
// Only radar_management[0].testing is meaningful — it is the system-wide test mode.
};
/* Array of radar states, indexed by RADAR_* constants.
* radar_management[0] is the management/system entry; its testing field
* holds the system-wide TESTING_* mode (see below).
* Access the active testing mode via: radar_management[RADAR_NONE].testing
* radar_management[0] is the management/system entry.
* Components: Thread 1, Traffic Cop (Thread 2) */
extern radar_management_structure radar_management[RADAR_COUNT];
@@ -145,25 +138,6 @@ extern radar_management_structure radar_management[RADAR_COUNT];
// Components: Thread 1, Traffic Cop (Thread 2), all scope renderers
extern int current_radar;
/* Component identifiers for radar_management[RADAR_NONE].testing.
* When that field is non-zero, only the named component is active and
* no other radars can be made available.
* Values 2-5 correspond to RADAR_* constants for the four radar types.
* Components: Thread 1 (startup), all components that gate on test mode */
constexpr int TESTING_NONE = 0; // normal exhibit operation
constexpr int TESTING_MANAGEMENT = 1; // setup and radar selection (this module)
constexpr int TESTING_CHAIN_HOME = 2; // chain home A-scope
constexpr int TESTING_MARINE_ASCOPE = 3; // marine A-scope
constexpr int TESTING_MARINE_TRAFFIC = 4; // marine traffic control PPI
constexpr int TESTING_POLICE_BOAT = 5; // police boat PPI
constexpr int TESTING_TRAFFIC_COP = 6; // traffic cop (Thread 2)
constexpr int TESTING_SIMULATOR = 7; // simulator (Thread 3)
constexpr int TESTING_RASPBERRY_PI = 8; // raspberry pi receiver (Thread 5)
/* radar_management[RADAR_NONE].testing is initialized from TESTING_COMPONENT in settings.h.
* Set TESTING_COMPONENT to TESTING_NONE for normal exhibit operation.
* Components: Thread 1 (startup gating), all components */
/* ============================================================
* THREAD MUTEXES
* Defined in global_data.cpp; extern declared here.
@@ -239,13 +213,3 @@ extern float uniform_bearing_cursor;
// Components: Marine A-scope
extern float uniform_marine_a_bearing;
/* ============================================================
* TEMPORARY TEST FILE REGISTRY
* Each active test .cpp stub pushes its filename into test_functions.
* Each active test .h stub pushes its filename into test_functions_include.
* Both are printed at startup when any entry is present so it is
* immediately visible that test infrastructure is compiled in.
* Components: any temporary test stub; Thread 1 (startup logging)
* ============================================================ */
extern std::vector<std::string> test_functions;
extern std::vector<std::string> test_functions_include;