Skip to main content

NeuroCW (Part 2): Call for Real On-Air CW Recordings — Help Build the First Real-Air Benchmark

Call for data: real received CW recordings (WAV/FLAC) + a 100% verified transcript. Email kd8cec@gmail.com, subject "NeuroCW data".
Synthetic channel

Figure 1. Everything NeuroCW learned came from the bottom panel: a simulated channel. Now it needs real signals.

1. Why real data

In Part 1, NeuroCW scored 5.07% CER on synthetic tests, but its accuracy on real on-air signals hasn't been measured. Just two real recordings were enough to expose a blind spot:

Keying weight fix

Figure 2. On a synthetic heavy-weight keying test, one targeted fine-tune cut the error from 13.4% to 0.1%. Verified real recordings would turn findings like this into a benchmark.

2. What we need

What we need checklist

Figure 3. Checklist for one submission.

3. How to contribute

How to contribute

Figure 4. Four steps. Several recordings per email is fine, and share links work for large files.

Transcript rules: write exactly what was sent, including the sender's mistakes. Put prosigns in angle brackets (<AR> <SK>). For Korean or Japanese, write Hangul or kana. If you are unsure of a part, trim it; never guess.

Sample submission

Figure 5. Paste this template into your email. The values are illustrative.

4. FAQ

  • Sample rate? Send your recorder's native file, with no re-encoding. It should be fine.
  • Other callsigns in the audio? They're fine since they were sent on air. You can also mask them (XXXX).
  • Credit? Optional. Give your callsign or stay anonymous. Contributors are credited by callsign unless they ask to stay anonymous.
  • Will the data be public? Yes. The recordings and transcripts will be released as an open real-air CW benchmark dataset, and every measurement result on it will be published.

By submitting, you confirm you made the recording and allow its use for training and evaluating NeuroCW, and its public release as part of the open dataset under an open license (details announced with the release). Please send amateur-band signals only.

Call for data: real received CW recordings (WAV/FLAC) + a 100% verified transcript. Email kd8cec@gmail.com, subject "NeuroCW data".

73, Ian Lee / KD8CEC

Comments

Popular posts from this blog

UV-K5 CEC HF Firmware v0.5 — Full-Band HF Receive

Historical note: this post documents an early 2024 build and is kept for reference. For current firmware, use C-Board Firmware v0.32 , and see CEC UV-K5 Firmware Source Is Now Open for the source code. ▶ Watch the HF 0.5 fullband walkthrough on YouTube → Subscribe to the KD8CEC YouTube channel for more UV-K5 HF videos. Related: UV-K5 · si4732 · HF full band  Introduction to UV-K5 HF 0.5 (Fullband receive version) This is an introduction to UV-K5 HF full-band reception firmware 0.4HF using SI4732-A10. This version is released separately from the existing UV-K5 CEC firmware version. because space is needed to store a large PATCH file to use SI4732-A10's SSB. This article only describes the features newly added in Version 0.5. Please check the links below for full features. How to modify your hardware http://www.hamskey.com/2024/02/uv-k5s-hf-full-band-reception-lsb-usb.html Version 0.3HF (Most feature descriptions are provided) http://www.hamskey....

C-Board (DSP Board) for UV-K5 — Hardware Overview (Updated June 2024)

  C-BOARD for UV-K5 I created an externally mountable DSP-Board to process digital signals from UV-K5. DSP-Board was named C-Board. C-Board is divided into versions ranging from the simplest version to one that can be equipped with GPS.

Release CEC Firmware v1.200 for uBITX All version(include V2, V3, V4, V5)

▶ Watch the full v1.200 walkthrough on YouTube → More firmware and uBITX videos on the KD8CEC YouTube channel . Related: uBITX · Firmware Release CEC Firmware v1.200 for uBITX All Version (include v2, v3, v4, v5) I did the firmware work for v5 when uBITX V5 was released, but I release it now. I received the feedback from a thankful beta tester and tested it myself by converting my uBITX v3 to v5 but I was not sure. I ordered the uBITX V5 and delivered the correct uBITX V5, so I made a little more fine-tuning. If you use V2, V3, V4, you do not need to update this firmware.