跳到正文
DEV Community· Dominique Siacci·· 1 小時前AI 評分35

Readback:練習塔準許降落時,我的脈搏升至最高

My pulse peaked when the practice tower cleared me to land

AI 導讀

Readback 是供學生及私人飛行員練習無線電通話的夥伴,使用 Presage SmartSpectra SDK 透過鏡頭追蹤脈搏和呼吸,並在飛行練習後列出脈搏上升最多的通話訊息。它只供練習,不是經認可的訓練設備,也不作健康評估。

正文

This is a submission for the Presage SmartSpectra SDK Challenge

My pulse climbed most when a practice tower cleared me to land. The take-off clearance was not far behind.

I was at my desk with a headset on, talking to a simulated tower while the camera followed my pulse. Nothing was moving. Still, it was as if I could really see myself taking off, and then landing.

Both are short messages. The taxi clearance at the start is much longer: a runway, a QNH, a holding point and a route, to read back in order. In that session, my pulse didn't follow the length of the message. It followed what the words meant.

In October I built a practice tower for a friend who is shy about speaking English on the radio. It talks, it listens, and it says "negative" when the QNH is wrong. This month I pointed a camera at the person talking to it.

What I Built

Readback is a radio practice partner for student and private pilots. A simulated tower talks to you, and you read back out loud. Meanwhile, the camera follows your pulse and your breathing with the Presage SmartSpectra SDK.

Talking to the tower is one of the things that scare people when they learn to fly. You know the phraseology at home. Then a controller reads you a clearance in one breath, and you have to say it back, in order, while the frequency waits.

A session goes like this:

  1. A consent screen comes first. It says what is measured, what stays on the computer, what goes to Presage, and how to stop.
  2. A calm minute. You sit the way you will for the radio and breathe normally. That minute becomes your reference, for this session only.
  3. A circuit at Isola, a made-up aerodrome: taxi, take-off, a touch and go, a full stop. You hold the space bar to talk. The runway, the QNH and the wind change every game, and a wrong readback gets "negative".
  4. On the side, your pulse and your breathing, shown as differences from your calm minute.
  5. A breathing guide, if your breathing picked up while you listened. It offers three slow breaths before your readback. The tower waits.
  6. A timeline after the circuit. It puts first the messages after which your pulse climbed most.

It's a mirror for practice, not a measure of health. It compares you with yourself, and with nothing else. Like the October tower, it's a game, not an approved training device: your instructor and your country's phraseology manual are the reference.

Demo

The video shows the consent screen, the calm minute, an exchange with the tower, the breathing guide and the timeline. The camera preview is blurred.

Code

Readback

A radio practice partner for student and private pilots. A simulated tower talks to you, you read back out loud, and the camera follows your pulse and your breathing while you do, with the Presage SmartSpectra SDK. Before your readback, if your breathing has picked up while you listened, a short breathing guide offers itself: the tower can wait. After the circuit, a timeline shows which messages made your pulse climb, next to what the tower said and what you read back.

A mirror for practice, not a measure of health. Readback compares you only with yourself, with a calm minute taken at the start of each session. It makes no medical claim, shows no normal or abnormal value, and never says whether anyone is fit to fly. It is a practice game, not an approved training device: your flight instructor and your country's official phraseology manual are…

Electron and plain JavaScript, under the Apache 2.0 licence. On a Mac with Apple Silicon: npm install, then npm run setup:tower once, your Presage key in ~/.config/readback/presage.key, and npm start. No camera at hand? The first screen offers simulated signals, labelled as such everywhere.

The tower is my October project, phraseology. Readback runs it unchanged, as a separate program on the same computer. Everything that reacts to the camera is new.

How It Responds to Human Signals

Readback asks the SDK for three signals, and nothing else:

Signal What the SDK gives What Readback does with it
Pulse rate an average over 12 seconds your reference, the live difference, and the climb after each message
Breathing rate an average over 30 seconds your reference during the calm minute
Chest movement the breathing waveform breaths counted while you listen, and the breathing guide

The wiring is the SDK's renderer entry point, with telemetry off:

const sdk = new SmartSpectraSDK({
  apiKey,  // read by the main process from a file in your home folder
  requestedMetrics: [MetricType.CHEST_BREATHING, MetricType.BREATHING_RATE, MetricType.PULSE_RATE],
  enableTelemetry: false,
});
sdk.on('metrics', (buf) => store.add(decodeMetrics(buf)));
sdk.on('validationStatus', (code) => showHint(code)); // "face the camera", "more light"…
await sdk.start(); // only after the consent screen

The most useful page was Presage's model card. It says the breathing rate doesn't hold while the person is talking. But a radio exchange is talking, a few seconds of listening, and talking again. There are never 30 quiet seconds.

So I used the chest movement instead, which the SDK streams next to the rate. Readback takes the moments when you are listening, removes the slow drift, and counts the breaths. The same count on the calm minute gives the reference. It's a rough count, but it's enough to notice that you breathe faster than at rest. Readback never shows a breathing number while you talk.

When that count is up by 4 breaths a minute or more, the breathing guide opens. You can change that threshold, or turn the guide off. It breathes four seconds in and six out, three times, and draws your own chest moving under the circle. The space bar skips it.

The timeline needed one correction. My first version ranked the messages by how high the pulse went above the calm minute. On the first test, with simulated signals, every message after a "negative" looked stressful, because the pulse was still up. Now a message's climb starts from the pulse at its first word. The level against the calm minute sits next to it.

Here is the timeline after my own circuit:

The timeline after my circuit on the Mac

The clearance to land came first, with a climb of 14 beats per minute. The take-off clearance came third. Between them, the tower's request to read back the vacate instruction, which came right after landing, while my pulse was still up. Before both clearances, the breathing guide opened, and both times I skipped it to read back.

HRV and facial expressions are left out on purpose. HRV needs a full minute, longer than an exchange. And a label like "fear" on someone learning would be a judgement, with nothing true to add to the practice.

Prize Categories

Best Thoughtful Real-World Use. Radio nerves are part of learning to fly, and the usual advice is "practise more", with nobody to practise with. Readback gives you a tower to practise with, and a mirror of what it does to you. The design follows from consent and from the SDK's limits: the camera opens only after you agree, the preview is blurred by default, the numbers are differences from your own calm minute, breathing is read only while you listen, and nothing is saved unless you ask.

Most Creative or Delightful Use. The signal changes the conversation, not just a dashboard. When your breathing has picked up, the tower waits for you, and you watch your own chest move under the breathing circle. The tower's voice goes through a small radio filter with a squelch, and the screens use B612, the typeface designed for cockpit displays.

Consent and Data Handling

  • Consent first. The first screen says what is measured, what stays on the computer, what goes to Presage and how to stop. The camera opens only after "I agree, turn the camera on". The microphone is a separate choice; without it, you type your readbacks. Until you agree, the app refuses every camera and microphone request.
  • Visible and stoppable. "Camera on" and "Stop camera" stay at the top while the camera runs. Closing the window stops everything, and the camera turns off at the end of each circuit.
  • Images: never recorded, saved or sent by Readback.
  • Your voice: kept in memory while you hold the key, transcribed on the same computer by the tower, then dropped. Never written to disk.
  • Measurements: in memory during the session. Saved only if you press "Save on this computer", as a small file with your reference, the tower's messages, whether each readback was accepted, and the climbs. No image, no audio, no transcript. One button deletes every saved session.
  • What goes to Presage: the SDK computes pulse and breathing on the computer. It contacts Presage's service to check the API key and the plan. The SDK's usage telemetry is on by default; Readback turns it off.
  • No AI service. No language model writes anything about you. The tower's readback checks are plain rules.
  • Nothing else leaves the computer. The app's page can't reach the network. Setup downloads the packages and the speech models once; after that, the tower runs offline.

I built Readback to practise the long readbacks. My pulse cared about two short sentences.

Pilots: which radio call still gets you, years after the licence?

來源:DEV Community · dev.to