Smart Scan strategy for Electronic Warfare

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Your scheduler's performance is a property of the emitter model you wrote, so a policy tuned to your simulator's regularities may be learning your assumptions rather than a general strategy — vary the emitter behaviours adversarially and report across them

2. It gets worse

   The domain vocabulary is dense and a general judging panel may not follow why the problem is hard, so budget real time on explaining the two-dimensional search before you present any result

3. Still reading?

   Frequency-agile emitters that hop unpredictably have an information-theoretic ceiling on interception, and a submission claiming near-perfect interception against them has a modelling error somewhere

4. And the finisher

   The statement asks separately for an approach to optimally intercept a periodic scan receiver, which is a distinct analytical sub-problem teams will read past and skip entirely

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  4/5

  Actually buildable, which on this slate is rarer than it sounds. Do not squander it on scope.

  Unusually for a defence statement the ground truth is meant to be simulated — the statement itself asks you to build an RF environment model with known emitter status per band and time slot — so the usual objection that you have no real data does not apply here, and a synthetic radar emitter dataset is linked to seed the emitter behaviours.

• Innovation scope

  5/5

  There is something genuinely new here. Do not bury it under another dashboard.

  No method is prescribed anywhere — the statement defines the objective and the figures of merit and leaves the entire approach open, so whether you frame this as a restless multi-armed bandit, a partially observable decision process or a reinforcement learning policy is your call and the framing itself is the contribution.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  The figures of merit are named with unusual precision and the two-dimensional nature of the search problem is explained well, but the receiver parameters, the band count, the emitter behaviour models and the evaluation protocol are all left undefined, and the dense domain vocabulary makes the statement hard to parse without prior exposure to electronic support.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  Genuinely underrated — the statement sanctions simulation as the ground truth so the circularity objection that sinks most defence statements does not apply, the objective is a clean sequential decision problem where you can beat a stated baseline numerically, the figures of merit are given, and electronic warfare is a domain almost no student team will enter.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  A defensible RF environment simulator, a receiver model, a learned scheduler, baseline implementations to compare against and an evaluation harness across seven figures of merit is four workstreams, with the simulator quietly the most important because everything else is measured against it.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  A spectrum waterfall with the receiver's dwell decisions overlaid and an intercept-rate curve pulling away from the open-loop baseline is genuinely persuasive to anyone who knows the domain, but it is abstract and a general judge will need the problem explained before the result means anything.

The demo they will have already seen 🪞

Somewhere around 120–270 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• The statement explicitly asks for a simulated RF environment with truth information, which means simulation is the sanctioned methodology rather than a workaround — this removes the data objection that undermines nearly every other defence statement here
• The figures of merit are enumerated, so your evaluation protocol is specified for you and results are comparable rather than self-defined
• The open-loop sweep gives you an obvious, fair and unarguable baseline, so you can demonstrate improvement as a number rather than as a claim