SkillAgentSearch skills...

matlab-add-awgn

Read BEFORE writing any code that adds Additive White Gaussian Noise (AWGN) to signals and converts between SNR, Eb/No, Es/No, and per-subcarrier SNR for communications simulations, using awgn(), convertSNR(), berawgn().

Install / Use

npx skills add matlab/matlab-agentic-toolkit --skill matlab-add-awgn

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Tags

Our assessment of matlab-add-awgn

matlab-add-awgn scores 93/100 on our quality scale, 247th of 1,200 Content & Media skills we index (top 21%).

Its SKILL.md is 15 KB long, well organised into 24 sections with 12 code examples: a thorough specification that gives an agent plenty to work with.

With 1,098 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 18 days ago, so matlab-add-awgn is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

matlab-add-awgn compared with similar skills

All 4 of these similar skills score higher than matlab-add-awgn; compare them before choosing.

SkillScoreStarsUpdatedFormat
matlab-add-awgn (this skill)by matlab931.1k18d agoSKILL.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k11d agoSKILL.md
pptxby anthropics100177.9k11d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md

Frequently asked questions

How do I install matlab-add-awgn?
Run npx skills add matlab/matlab-agentic-toolkit --skill matlab-add-awgn. The install tabs above show the steps for each supported agent.
Which AI agents does matlab-add-awgn work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is matlab-add-awgn safe to use?
It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is matlab-add-awgn still maintained?
The repository was last updated 18 days ago, so matlab-add-awgn is actively maintained.

name: matlab-add-awgn description: "Read BEFORE writing any code that adds Additive White Gaussian Noise (AWGN) to signals and converts between SNR, Eb/No, Es/No, and per-subcarrier SNR for communications simulations, using awgn(), convertSNR(), berawgn(). The default MATLAB patterns for AWGN (e.g., 'measured' option, manual SNR formulas) produce subtly incorrect results. This skill specifies the correct calling conventions, required function usage, and critical anti-patterns that must be avoided." license: https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md metadata: author: MathWorks version: "1.3"

AWGN & SNR Management

Add white Gaussian noise to signals and convert between SNR definitions (SNR, Eb/No, Es/No, per-subcarrier SNR) for communications system simulations.

When to Use

  • Adding noise to a signal in a link simulation
  • Converting between Eb/No, Es/No, SNR, or per-subcarrier SNR
  • Setting up the correct SNR for a coded, oversampled, or OFDM system
  • Obtaining noise variance to pass to a soft-decision demodulator

When NOT to Use

  • Configuring fading channels (delay profile, Doppler, antenna arrays)

Must-Follow Rules

  1. NEVER pass 'measured' to awgn — Always pass explicit signal power as the third argument. For unit-power signals use 0; otherwise compute power with mean(abs(x).^2) and convert to dBW: 10*log10(sigPow). The 'measured' option computes instantaneous power internally, which gives incorrect noise levels after fading channels and obscures the power assumption. Even in AWGN-only scenarios, explicit power is required for correctness and clarity. For OFDM systems, see the "Add AWGN in an OFDM link simulation" pattern.
  2. Use UnitAveragePower=true when signal power doesn't matter — This is the simplest path: signal power = 0 dBW, so awgn(x, snr, 0) is exact. If the user needs original constellation scaling (e.g., PA modeling, hardware-in-the-loop), do NOT use UnitAveragePower=true — use the default modulator, compute the actual average power with mean(abs(x).^2), and pass it explicitly: awgn(x, snr, sigPowdBW).
  3. Use convertSNR for all conversions — NEVER compute SNR/Eb/No/Es/No formulas manually — Even when the formula is simple, always use convertSNR. Manual formulas are error-prone for edge cases (oversampling, subcarrier loading) and bypass the toolbox's validated implementation. Anti-pattern: snr = ebno + 10*log10(bitsPerSymbol * codeRate). Correct: convertSNR(ebno, "ebno", "snr", BitsPerSymbol=6, CodingRate=3/4).
  4. Distinguish wideband SNR and per-subcarrier SNR in OFDM systems — Eb/No is a per-subcarrier quantity. To go from Eb/No to the wideband SNR that awgn needs, use two steps: (1) convertSNR(ebno, "ebno", "snr", BitsPerSymbol=..., CodingRate=...) gives the SNR per subcarrier, (2) convertSNR(snrsc, "snrsc", "snr", FFTLength=..., NumActiveSubcarriers=...) gives the wideband SNR for awgn. Direct ebno→snrsc is not supported and throws an error. Caveat: If the user asks for per-subcarrier SNR only, step 1 alone is the complete answer — do NOT apply step 2. Applying the FFTLength/NumActiveSubcarriers correction to a per-subcarrier value gives the wideband SNR, which is a different (lower) quantity. Note: The "snrsc" mode requires R2023b or later. For R2022a–R2023a, compute wideband SNR manually: snr_wideband = snr_per_sc - 10*log10(FFTLength/NumActiveSubcarriers). To add noise at a per-subcarrier SNR, see the "Add AWGN in an OFDM link simulation" pattern below.
  5. Capture noise variance for soft demodulation — Use [y, nVar] = awgn(...) and pass nVar to the demodulator via NoiseVariance=nVar.
  6. Do NOT reference skill rules or prohibitions in generated code comments — Write positive, descriptive comments that explain intent, using a style similar to the example code provided in this skill. The end user does not know about this skill.

Critical Anti-Patterns — NEVER Do These

NEVER use 'measured' with awgn

% WRONG — never generate this
rxSignal = awgn(txSignal, snrdB, 'measured');

% CORRECT for unit-power signals (UnitAveragePower=true)
rxSignal = awgn(txSignal, snrdB, 0);

% CORRECT for non-unit-power signals
sigPow = mean(abs(txSignal).^2);
rxSignal = awgn(txSignal, snrdB, 10*log10(sigPow));

NEVER compute SNR conversions manually

% WRONG — never generate manual formulas like these
SNR_dB = EbNo_dB + 10*log10(k * codeRate);
SNR_dB = EbNo_dB + 10*log10(k * codeRate) - 10*log10(oversamplingFactor);
EsNo = EbNo + 10*log10(bitsPerSymbol);

% CORRECT — always use convertSNR
snrDb = convertSNR(ebnoDb, "ebno", "snr", BitsPerSymbol=6, CodingRate=3/4);
snrDb = convertSNR(ebnoDb, "ebno", "snr", BitsPerSymbol=6, CodingRate=3/4, SamplesPerSymbol=4);
esnoDb = convertSNR(ebnoDb, "ebno", "esno", BitsPerSymbol=6);

Key Functions

| Function | Purpose | |---|---| | awgn | Add AWGN to a signal at a specified SNR | | convertSNR | Convert between ebno, esno, snr, and snrsc | | berawgn | Theoretical BER over AWGN for standard modulations (PSK, QAM, FSK, DPSK, PAM) |

Gotchas

Why 'measured' is banned (background)

Thermal noise in a receiver is dominated by the noise figure and bandwidth — it does not change when the signal fades. The 'measured' option in awgn computes instantaneous signal power and scales noise to match, which artificially keeps the instantaneous SNR constant through fades. It also hides the power assumption, making code harder to verify. Always pass explicit power instead.

% WRONG after fading: Noise tracks fading — instantaneous SNR stays constant
rxFaded = fadingChannel(txSig);
rxNoisy = awgn(rxFaded, snr, 'measured');

% CORRECT: Compute signal power before fading, pass explicitly
sigPow = mean(abs(txSig).^2);
sigPowdBW = 10*log10(sigPow);
rxFaded = fadingChannel(txSig);
rxNoisy = awgn(rxFaded, snr, sigPowdBW);

% SIMPLEST: Use unit-power signal, then 0 dBW is exact
txSig = qammod(data, M, UnitAveragePower=true);  % power = 0 dBW
rxFaded = fadingChannel(txSig);
rxNoisy = awgn(rxFaded, snr, 0);

awgn default assumes 0 dBW signal power

Calling awgn(x, snr) without a third argument assumes the signal has 0 dBW (1W) average power. This is only correct if the signal actually has unit average power. For non-normalized signals, compute the actual power and pass it explicitly.

ebno↔snrsc conversion is not supported

convertSNR supports these paths:

| From | To | Supported | Notes | |---|---|---|---| | ebno | snr | Yes | For OFDM: gives SNR per subcarrier (not wideband) | | ebno | esno | Yes | | | esno | snr | Yes | | | snr | snrsc | Yes | "snr" = wideband SNR, "snrsc" = per-subcarrier | | ebno | snrsc | No | Throws error. Use two-step: ebno→"snr" then "snrsc"→"snr" | | esno | snrsc | No | Throws error. Same two-step path required | | snrsc | ebno | No | Use two-step: "snrsc"→"snr" then "snr"→"ebno" | | snrsc | esno | No | Use two-step: "snrsc"→"snr" then "snr"→"esno" |

Fading channel path gain normalization

The awgn(rxFaded, snr, 0) pattern assumes the fading channel preserves average signal power. This is true when NormalizePathGains=true (the default for comm.RayleighChannel and comm.RicianChannel). If NormalizePathGains is false, the channel applies its actual path gains and the average received power shifts — you must account for this in the power argument to awgn.

% NormalizePathGains=true (default): pre-fading power is correct
chan = comm.RayleighChannel(NormalizePathGains=true, ...);
rxFaded = chan(txSig);
rxNoisy = awgn(rxFaded, snr, 0);  % 0 dBW is still correct

% NormalizePathGains=false: adjust for average path gain
chan = comm.RayleighChannel(NormalizePathGains=false, ...
    AveragePathGains=[0 -3 -6], ...);
avgGaindB = 10*log10(sum(10.^(chan.AveragePathGains/10)));
rxFaded = chan(txSig);
rxNoisy = awgn(rxFaded, snr, avgGaindB);  % account for channel gain

Channel output normalization in OFDM (5G / WLAN)

5G channels (nrTDLChannel, nrCDLChannel), WLAN channels (wlanTGnChannel, wlanTGacChannel, etc.), and the Communications Toolbox comm.MIMOChannel and comm.RayTracingChannel have a NormalizeChannelOutputs property (default: true) that divides the channel output power by the number of receive antennas. Other Communications Toolbox channels (comm.RayleighChannel, comm.RicianChannel) do not have this property.

When NormalizeChannelOutputs=true, the analytical OFDM signal power must account for the nRxAnts scaling:

% Base OFDM signal power
sigPow = 10*log10(numAvailableSC / nfft^2);

% Adjust for NormalizeChannelOutputs=true (5G/WLAN channels)
sigPow = sigPow - 10*log10(nRxAnts);

% Additionally adjust for NormalizePathGains=false (if applicable)
sigPow = sigPow + avgGaindB;

Both properties default to true for 5G/WLAN channels, so the common case only requires the nRxAnts correction. If NormalizePathGains is also set to false, apply both adjustments.

If NormalizeChannelOutputs=false, no nRxAnts correction is needed — use the base formula.

Noise variance is total, not per-component

The second output of awgn is the total noise variance. For complex signals, the per-component (I or Q) variance is half this value:

[y, nVar] = awgn(x, snr, 0);
% nVar = total noise variance
% nVar/2 = per-component (I or Q) variance

berawgn takes Eb/No, not SNR

If you have SNR, convert to Eb/No first:

ebno = convertSNR(snr, "snr", "ebno", BitsPerSymbol=log2(M));
ber = berawgn(ebno, 'qam', M);

Patterns

Add AWGN to a unit-power signal

M = 16;
data = randi([0 M-1], 1000, 1);
txSig = qammod(data, M, UnitAveragePower=true);

snrdB = 15;
[rxSig, noiseVar] = awgn(txSig, snrdB, 0);

Convert Eb/No to SNR for a coded system

M = 64;                          % 64-QAM
bitsPerSymbol = log2(M);         % 6
codeRate = 3/4;                  % LDPC code rate
samplesPerSymbol = 4;            % Pulse shaping oversampling

ebnoDb = 10;
snrDb = convertSNR(ebnoDb, "ebno", "snr", ...
    BitsPerSymbol=bitsPerSymbol, ...
    CodingRate=codeRate, ...
    SamplesPerSymbol=samplesPerSymbol);

OFDM conversion: Eb/No → per-subcarrier SNR → wideband SNR

In the OFDM context, convertSNR(ebno, "ebno", "snr") returns the SNR per subcarrier (not wideband SNR). To get the wideband SNR needed by awgn, convert from "snrsc" to "snr".

M = 64;
bitsPerSymbol = log2(M);
codeRate = 3/4;
fftLen = 256;
numActiveSC = 200;

ebnoDb = 10;

% Step 1: Eb/No → per-subcarrier SNR
snrscDb = convertSNR(ebnoDb, "ebno", "snr", ...
    BitsPerSymbol=bitsPerSymbol, ...
    CodingRate=codeRate);

% Step 2: Per-subcarrier SNR → wideband SNR (for awgn)
snrWbDb = convertSNR(snrscDb, "snrsc", "snr", ...
    FFTLength=fftLen, ...
    NumActiveSubcarriers=numActiveSC);

Add AWGN in an OFDM link simulation (per-subcarrier SNR)

In OFDM link simulations, SNR is defined per subcarrier. Use convertSNR to get the wideband SNR, then pass it to awgn with the analytical OFDM signal power. Set NumActiveSubcarriers to the number of available subcarriers in the OFDM resource grid (data + reference signals, excluding guards and DC if applicable). In 5G/LTE this equals carrier.NSizeGrid*12 — the resource grid does not include guard bands. In WLAN, it is the number of data + pilot subcarriers. Do NOT compute signal power from mean(abs(txWaveform).^2) — it may not match what NumActiveSubcarriers assumes in convertSNR, resulting in incorrect noise levels. Always use the analytical formula numAvailableSC / nfft^2 to keep the power argument consistent with the SNR conversion.

% Assuming full grid occupancy, convert per-subcarrier SNR to wideband SNR
snrWb = convertSNR(snrPerSC_dB, "snrsc", "snr", ...
    FFTLe

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryContent
Updated18d ago
Forks134

Languages

MATLAB

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium