frame_analytics

Image and video quality metrics for PyTorch — CPU and CUDA — at float64-reference accuracy. Fused kernels for forward and backward, so the same code works as an evaluation metric and as a training loss.

pip install frame-analytics        # uses the torch you already have

Requires an existing PyTorch ≥ 2.0 — deliberately not installed automatically, so your CUDA build is never replaced by the CPU wheel from PyPI. No torch yet? Grab the right build from pytorch.org, or accept the PyPI wheel with pip install frame-analytics[torch].

import torch, frame_analytics as fa

a = torch.randint(0, 256, (8, 3, 1080, 1920), dtype=torch.uint8, device="cuda")
b = torch.randint(0, 256, (8, 3, 1080, 1920), dtype=torch.uint8, device="cuda")

fa.mse(a, b)
fa.psnr(a, b, data_range=255.0)
fa.ssim(a, b, data_range=255.0)      # Wang et al. 2004, exactly
fa.ms_ssim(a, b, data_range=255.0)   # Wang et al. 2003
fa.gmsd(a, b, data_range=255.0)      # Xue et al. 2014
fa.lpips(a, b, data_range=255.0)     # Zhang et al. 2018, weights included
fa.ssimulacra2(a, b, data_range=255.0)   # Sneyers 2022/2023, libjxl's metric
fa.l1(a, b); fa.charbonnier(a, b); fa.huber(a, b)

fa.ssim(a, b, reduction="none")      # per-image, (8,)
fa.ssim(a, b, return_map=True)       # (8, 3, 1070, 1910)

# the convention the super-resolution literature reports
fa.psnr(a, b, data_range=255.0, luma="matlab", crop_border=4)

Accepts (H,W) / (C,H,W) / (N,C,H,W), uint8 through float64. uint8 stays uint8 into the kernel — 2 bytes/pixel of bandwidth instead of 8.

Speed

Speedup over each library, across 512²→4K and batch 1→8, RTX 3090 / 16-thread CPU:

Selected absolute numbers, RTX 3090, ms/call (lower is better):

SSIM sustains 25.6 Gpixel/s (~11 700 fps at 1080p). PSNR at 4K ×8 hits 880 GB/s — 94% of the card's theoretical bandwidth, the ceiling for anything that must read both frames.

Streaming 1080p RGB via CUDA graphs, host uint8 in, python float out: 931 fps (2 941 fps for resident tensors).

Full per-size CPU and CUDA tables: python bench/bench.py.

Where it doesn't win

• cv2.PSNR on one sub-megapixel single-channel frame: 0.006 ms against our 0.008. Not the kernel — that runs the same 262 144 pixels in 3.8 µs, less than cv2.PSNR takes for the whole call — but the ~4 µs of Python in front of it, which is a fixed cost and so only visible when there is nothing else to pay for. One frame bigger, or one channel wider, and it inverts: 3.3× at 1080p, 7.3× at 1080p ×8.
• Without the compiled extension the portable PyTorch fallback is only ~1.1× faster than pytorch-msssim and uses more memory. The speed claims are claims about the kernels; the fallback exists to be correct, not to win.

Memory

Peak allocation above the two input frames, RTX 3090, 3-channel, MiB per call. Nothing here is the frames themselves — those you already have:

A fused kernel has nowhere to put an intermediate. What is left for SSIM and GMSD is the per-block partial sums — sized by the tile grid, so 4K ×8 costs 0.75 MiB where the alternatives cost 9–17 GiB — and for the pixel metrics, the output scalar. The libraries above are not doing anything wrong; five or six frame-shaped temporaries is what the textbook formulation asks for, and 2253 MiB at 1080p ×8 is almost exactly 6× the 380 MiB input.

MS-SSIM is the one metric that must materialise something: the four downsampled copies of both frames. That geometric series sums to a third of a frame each, and nothing full-resolution survives — 120 MiB at 1080p ×8, where the frame pair itself is 380.

The CPU story is the same one. There is no max_memory_allocated for host memory, so these are peak process footprints, each measured in its own interpreter — how much more memory the OS had to hand over, which is the number that decides whether the box swaps:

The pixel metrics reduce two buffers to a scalar and allocate nothing at all. SSIM's 2 MiB does not move when the pixel count goes up 8×, so it is fixed working set rather than anything per-pixel. MS-SSIM is cheaper from uint8 than from float because the cast is fused into the first pooling step: fed uint8 it never materialises a full-resolution float copy of either frame, and only the pyramid survives.

Every row includes the gradient with respect to the prediction — 24 MiB at 1080p, 760 at 4K ×8 — which is unavoidable and which every implementation pays. For fa.l1 it is the entire figure: the backward writes the gradient and allocates nothing else. SSIM costs three more planes on top of it and MS-SSIM four, at every size — the fused backward recomputes the local moments instead of saving them, while the autograd implementations keep the forward's activations, which is where the 15 GiB comes from. GMSD on a single 1080p frame is the one row that loses, by 6 MiB.

StreamingMetrics at 1080p RGB holds 18 MiB — the two device frames plus the CUDA graph's private pool — and allocates nothing per frame, whether it is scoring one metric or nine.

Without the compiled extension the portable path allocates like the rest of the field, and slightly worse than the best of it: 2830 MiB for SSIM at 1080p ×8, and 4.5–4.7 GiB as a loss step depending on what torch.compile managed to fuse.

Full tables: python bench/bench_memory.py.

Accuracy

Defaults reproduce ssim_index.m: 11×11 Gaussian, σ=1.5, K=(0.01, 0.03), valid support. Every kernel is gated against a float64 transcription of the paper (python tests/validate.py).

The bottom entries aren't bugs — different windows, MATLAB-style downsampling, zero padding. Defensible defaults, different metric.

MSE and PSNR sum in float64 whatever the input is typed as — a 4K frame has 8.3M residuals, and summing those in float32 would lose ~4 significant digits straight into the dB figure. Squaring the residual is a separate question from summing it, and the two backends answer it differently:

• uint8, and float64 input, are exact on both backends — an integer accumulator for the first, a float64 residual for the second.
• float16/float32 input is exact on CPU, and squared in float32 on CUDA. That costs at most one float32 ulp on the term, ~6e-08 relative worst case and ~1e-10 on real frames, so CPU and CUDA MSE agree to about 1e-08 rather than bit-for-bit. It buys up to 2x: a GA102 retires float64 at 1/64 the float rate, and a float64 residual left the kernel 2-3x over its DRAM floor with fp16 input no faster than fp32.

Worst abs. error vs float64 reference, over CPU and CUDA, native and portable:

GMSD's similarity map is float32, so deviations below ~1e-7 measure rounding, not the images (gmsd(x, x) ≈ 3e-08, not 0). A typical GMSD is ~0.03.

SSIMULACRA 2 against libjxl

Same gate — a float64 transcription of tools/ssimulacra2.cc, agreeing to 4e-11 of a score point — but the interesting comparison is against the canonical implementation, which does not agree with itself:

libjxl blurs with a marginally-stable recursive filter (Charalampidis's truncated cosines) in float32, and the rounding it accumulates along a 1448-px row is worth ~0.1–0.25 of a score point — which is why the reference port's own test allows ±0.25 and its CI "gives different results across different runs". That recursion's impulse response is finite, radius 5 with the ±5 taps exactly zero, so we convolve the 11 taps instead: same filter, no drift, and float32 lands 0.003 from float64 rather than 0.23. Zero-padded borders, the odd-size downsample clamp and the weight indexing on images too small for six scales all follow upstream exactly.

LPIPS

PSNR, SSIM and MS-SSIM all reward blur, so a model trained on them alone converges to something smooth. LPIPS (Zhang et al. 2018) is the term that punishes that, and the third number every super-resolution and restoration paper reports.

fa.lpips(a, b, data_range=255.0)          # lower is better, 0 is identical
crit = fa.LPIPS(data_range=1.0)
loss = fa.L1()(pred, target) + 0.1 * crit.loss(pred, target)

The weights ship in the wheel. 9.4 MiB, float32, no download, no torchvision dependency, works with no network at all. Every other library pulls the trunk from torchvision.models at first call, which means a 233 MiB download for AlexNet (528 MiB for VGG) into the torch hub cache. That checkpoint is ~94% classifier head; LPIPS taps five post-ReLU activations out of the conv trunk and discards the rest, so what actually gets used is 2.47M parameters. Only those ship. See frame_analytics/weights/ for provenance and the upstream BSD notices, and tools/build_lpips_weights.py for the extraction.

The alex trunk is the one the literature reports and the only one bundled. VGG is deliberately absent — 56 MiB for the training-loss variant. Point FA_LPIPS_WEIGHTS at a blob of the same layout to supply your own.

It is also more accurate than the alternatives, which is why it is faster

torch.backends.cudnn.allow_tf32 defaults to True, so on Ampere and later every LPIPS implementation that leaves it alone runs its convolutions with a 10-bit mantissa. Measured against a float64 transcription of the forward:

1.5e-05 is the fourth decimal — the decimal LPIPS is printed to. We turn TF32 off by default; allow_tf32=True is there if you measure that you need it.

On this card you do not: RTX 3090, ms/call, fp32 in, and the tf32 column is our own with the default flipped.

1.5–2.2× faster than the reference package while being 1000× closer to the reference forward. The convolutions are the same cuDNN calls everyone makes; the win is the tail — unit-normalise, square the difference, apply the channel weights, reduce — fused into one region per layer instead of ~10 separate elementwise kernels. That is also where the memory goes:

As a loss step (forward + backward), 1080p: 17.9 ms / 445 MiB against the reference package's 25.0 ms / 616 MiB.

Full tables: python bench/bench_lpips.py.

Caveats:

• LPIPS has no paper formula to be correct against — it is its weights. It is gated two independent ways: against richzhang/PerceptualSimilarity itself (agreement to 3e-08, i.e. float32 rounding), and against a float64 numpy transcription of the forward in reference.py that shares no code with the torch path.
• allow_tf32 covers the forward only. The backward's convolutions run under whatever cuDNN setting is live when .backward() is called — deliberate, in that the reported number is what has to survive to four decimals and a loss gradient does not.

SSIMULACRA 2

libjxl's metric (Sneyers 2022/2023): six scales, three XYB channels, three error maps, two norms — 108 sub-scores, a fitted weight vector, a cubic and a power law. It is the number the image-compression world reports, and it exists here because it answers a question SSIM cannot: SSIM sees a blur and a ringing artefact of the same magnitude as the same damage, and this does not.

fa.ssimulacra2(orig, dist, data_range=255.0)   # 100 = identical, ~90 = visually lossless

RTX 3090, uint8 sRGB in, ms/call:

215 fps at 1080p, 64 fps at 4K. There is no other GPU implementation to put in this table: what exists is libjxl's C++ tool, the Rust port behind ssimulacra2_rs, and vship's CUDA/HIP kernels, none of which take a torch tensor. For scale, the Rust port scores its own 1448×1080 test pair in 322 ms on this machine's CPU (single-threaded, the crate's default), against 4.7 ms here on the GPU and 219 ms on 16 CPU threads.

The numpy package is not computing quite the same metric — it blurs with scipy's mirrored-border Gaussian rather than libjxl's zero-padded recursive filter, which is worth ~0.3 of a score point — so read that row as scale, not as a head-to-head.

Memory is the weak spot, and honestly so: 452 MiB above the input pair at 1080p, against SSIM's 0.02. The metric wants five blurred moment planes per scale over three channels, and the portable path materialises the 15-plane pack and its blurred copy. That is what a fused kernel would remove, and there isn't one yet — ssimulacra2 is the only metric here with no C-ABI backend, so it has no backend_hint either.

dtype=torch.float64 costs 5.1× (23.6 ms at 1080p) and buys ~2e-4 of a score point; it exists for the accuracy gate, not for reporting.

One sharp edge worth knowing: a pyramid puts six shapes through the same compiled functions, so scoring one resolution per process is the fast path. Six cache entries per resolution against Dynamo's recompile limit of 8 means a process that scores a second resolution finishes it in eager — still correct, ~2.5× slower, and it says so in a warning. Video scoring, one resolution for the length of the run, is the case this is tuned for.

Full tables: python bench/bench_ssimulacra2.py.

• 3-channel RGB is the calibrated case. 1-channel input is replicated to three, which is what the field does with grayscale but is not something the human judgements behind the weights ever covered.
• Minimum 32×32 after cropping; the stride-4 conv and two max-pools leave nothing behind below that.

Training

Every metric is differentiable, and the SSIM family has a fused CUDA backward rather than autograd over the portable path — which is where the memory goes:

crit_ms = fa.MSSSIM(data_range=1.0)
crit_l1 = fa.L1()
loss = 0.84 * crit_ms.loss(pred, target) + 0.16 * crit_l1(pred, target)
loss.backward()

That mix is Zhao et al., Loss Functions for Image Restoration with Neural Networks (2016) — the reason MS-SSIM is here at all. Both terms still reward blur; add LPIPS if that matters for what you are training.

loss = 0.84 * crit_ms.loss(pred, target) + 0.16 * crit_l1(pred, target) \
     + 0.10 * fa.LPIPS(data_range=1.0).loss(pred, target)

fa.LPIPS holds its 2.47M trunk weights as buffers, not parameters, so .parameters() and .state_dict() are both empty: it cannot leak frozen ImageNet weights into your optimiser or your checkpoint. The weights are also shared process-wide per (trunk, device, dtype), so constructing several costs nothing after the first.

MS-SSIM loss step, 1080p ×8, float32 RGB: 12.7 ms / 942 MiB against pytorch-msssim's 81.3 ms / 3763 MiB — 6.4× faster on 4.0× less memory. The fused backward recomputes the local moments instead of storing them, so nothing full-resolution survives the forward pass at any of the five scales. Both figures include the 190 MiB gradient neither implementation can avoid; see Memory.

Gradients are verified two independent ways — against autograd over the portable path, and against central differences on the float64 reference forward — both to ~1e-6 relative. The scalar-reduction backward issues no device→host sync, so it does not stall the training pipeline.

Caveats:

• GMSD.loss() returns 1 − mean(GMS), not the deviation. d√var/dvar is unbounded as the variance goes to zero, which is exactly where a converging model lives; the mean is the well-behaved objective from the same map. fa.gmsd() still gives you the published metric.
• MS-SSIM's per-scale factors are clamped at zero, so on anti-correlated content the value and its gradient are exactly zero. Standard formulation, every implementation clamps — but MS-SSIM alone cannot pull a diverged model back. The L1 term above removes the dead zone.
• The native backward is CUDA + float32 only; CPU, float64, uint8 and downsample=True fall back to autograd over the portable path.
• The fused backward is a kernel, not a graph, so create_graph=True (gradient penalties, HVPs, torch.func.hessian) raises rather than silently returning zeros. For a second derivative use backend_hint="torch" with fa.set_compile_enabled(False).

Reporting conventions

luma= and crop_border= are on every metric. Nearly every super-resolution and restoration paper reports PSNR/SSIM on the luma plane of a border-cropped frame, so a library without them produces right-looking numbers that quietly disagree with the literature.

fa.psnr(a, b, data_range=255.0, luma="matlab", crop_border=scale)   # Y-PSNR
fa.ssim(a, b, data_range=255.0, luma="matlab", crop_border=scale)   # Y-SSIM

"matlab" is the studio-range Y′ of MATLAB's rgb2ycbcr, i.e. what BasicSR's test_y_channel=True computes. "bt601" and "bt709" are the full-range definitions. The crop is a view, so it costs nothing.

VapourSynth

frame_analytics.vapoursynth is VapourSynth-VMAF's vmaf.Metric — same signature, same feature numbering, same frame-property names — with these kernels underneath:

import vapoursynth as vs
from frame_analytics import vapoursynth as fa_vs

core = vs.core
ref  = core.lsmas.LWLibavSource("source.mkv")
enc  = core.lsmas.LWLibavSource("encode.mkv")

enc = fa_vs.Metric(ref, enc, [0, 2, 3])       # psnr, ssim, ms_ssim
enc.set_output()                              # vspipe -p . out.vpy

pip install frame-analytics[vapoursynth]

Every score lands in a frame property, so vspipe, vspreview, an akarin.Text overlay or a std.FrameEval decision all read it the usual way.

Ids 0–4 are libvmaf's own numbering; 1 and 4 are the two features with nothing behind them here, and asking for either says so instead of returning nothing. Everything from 5 up is an extension, and every feature can be named instead — fa_vs.Metric(ref, enc, ["psnr", "ssim"]) — which is the form worth writing. fa_vs.SSIM(ref, enc), fa_vs.SSIMULACRA2(ref, enc) and the rest are the one-metric spellings.

Where it is wider than the plugin: GRAY/YUV/RGB, 8–16 bit integer and 32-bit float, against the plugin's YUV-integer-only. The per-plane metrics run on each plane at its own resolution and the single-value ones on luma, which is what libvmaf does — float_ssim is a luma number there too. On an RGB clip they use all three channels instead.

RTX 3090, 24-thread host, VapourSynth R78, YUV420P8 (RGB24 for the last two), end-to-end frames per second through vspipe — frame request, host→device copy, kernel, frame properties:

For scale: ssimulacra2_rs scores a 1448×1080 pair in 322 ms on this machine's CPU. python bench/bench_vapoursynth.py regenerates this; --device cpu is the other half of the picture.

Two things need saying:

• LPIPS and SSIMULACRA 2 want real RGB and refuse YUV rather than guess a matrix: enc.resize.Bicubic(format=vs.RGBS, matrix_in_s="709") first. SSIMULACRA 2 additionally wants sRGB-encoded values, which is what that conversion of ordinary video gives you, and it is not symmetric — the reference clip goes first.
• This is a Python module, not a native plugin. There is no core.fa namespace, because the metric behind it takes a torch tensor and a VapourSynth plugin cannot hand it one. Everything else about it behaves like a filter.

Logging is on Metric itself, in the plugin's four formats — 0 XML, 1 JSON, 2 CSV, 3 subtitle (MicroDVD, as libvmaf writes it) — written once the clip has been read through, with the per-frame scores and libvmaf's four pools (min, max, mean, shifted harmonic mean):

enc = fa_vs.Metric(ref, enc, ["psnr", "ssim"], log_path="scores.json", log_format=1)

Or skip the file and get the pools directly, which is the whole-encode case:

fa_vs.pooled_scores(fa_vs.Metric(ref, enc, "ssim"))["float_ssim"]["mean"]

Pick where it runs with accelerator:

fa_vs.Metric(ref, enc, "ssim")                        # auto: GPU if present
fa_vs.Metric(ref, enc, "ssim", accelerator="cpu")     # force CPU
fa_vs.Metric(ref, enc, "ssim", accelerator="gpu")     # require a GPU
fa_vs.Metric(ref, enc, "ssim", device="cuda:1")       # second card, or "mps"

"gpu" raises when there is no CUDA device rather than quietly falling back — a script whose timings assume a card should stop, not run 40× slower. device takes a torch device for what a word cannot express and wins over accelerator when both are given. bench/bench_vapoursynth.py has the same --accelerator switch.

Metric also takes dtype, data_range, crop_border, backend_hint, and an options dict that forwards per-metric keywords — options={"ssim": {"win_size": 7}}, or {"psnr": {"eps": 1e-10}} if a finite number for an identical pair suits you better than inf.

Install

pip install frame-analytics

Needs torch ≥ 2.0 and numpy — and nothing else. Only numpy is installed automatically: torch is left alone on purpose, so pip never swaps an existing CUDA build for the CPU-only PyPI wheel. If torch is missing, import frame_analytics says so and points at pytorch.org; if the PyPI wheel is what you want, pip install frame-analytics[torch] pulls it explicitly.

No torchvision, and nothing is fetched at first call: the LPIPS weights are inside the wheel. It is 9.7 MiB, of which 8.8 is those weights and 0.8 is the kernels.

The kernels arrive precompiled, one wheel per platform and no version matrix — the same wheel works on every Python and every torch build.

That is not the usual arrangement, because the usual arrangement cannot be published. A torch C++ extension is ABI-locked to the exact {python} × {torch} × {CUDA} it was compiled against, and a wheel filename has nowhere to record "torch 2.6": pip would match on Python and platform alone and hand you an undefined symbol ImportError. So the kernels sit behind a plain C ABI instead — raw pointers, an int dtype code, a stream handle, int return codes — and the binaries link neither libtorch nor libpython. On Windows they import exactly one library, KERNEL32.dll; on Linux, glibc. An NVIDIA driver at runtime is the only external requirement, and only for the CUDA half.

Install on a platform with no wheel and the sources — which ship too — compile on first call (~1 min, cached thereafter). No compiler at all and every native kernel still has a portable PyTorch fallback returning the same numbers. fa.backend_status() reports which tier is live and where its binary came from; backend_hint="torch" / "native" forces either. On Windows the MSVC build environment is located automatically.

To compile from source at install time instead:

FA_BUILD_EXT=1 FA_CUDA_ARCHS="8.6 9.0+PTX" pip install frame-analytics

From a checkout:

pip install -e .
python tests/validate.py           # accuracy gate
python bench/bench.py              # speed + accuracy tables
python bench/bench_training.py     # MS-SSIM / GMSD / pixel losses
python bench/bench_memory.py       # peak memory, forward and loss step
python bench/bench_fused_ssim.py   # head-to-head vs fused-ssim
python bench/bench_lpips.py        # LPIPS vs lpips / torchmetrics / piq
python bench/bench_ssimulacra2.py  # SSIMULACRA 2, one fresh process per case
python bench/bench_vapoursynth.py  # end-to-end fps through the VapourSynth filter

The LPIPS weight blob is checked in, not generated at install time — building it needs torchvision and lpips, which no CI runner has. To rebuild it:

pip install torchvision lpips
python tools/build_lpips_weights.py

API

Every metric takes reduction ("mean" → scalar, "none" → per-image (N,)), dtype, luma, crop_border and — where there is a kernel — backend_hint.

mse        (x, y, *, reduction="mean", dtype=None, out_dtype=torch.float64,
            luma=None, crop_border=0)
psnr       (x, y, *, data_range=None, eps=0.0, ...)
ssim       (x, y, *, data_range=None, win_size=11, sigma=1.5, K=(0.01, 0.03),
            return_map=False, downsample=False, backend_hint="auto", ...)
ms_ssim    (x, y, *, data_range=None, win_size=11, sigma=1.5, K=(0.01, 0.03),
            weights=MS_SSIM_WEIGHTS, backend_hint="auto", ...)
gmsd       (x, y, *, data_range=None, T=None, eps=None, downsample=True,
            return_map=False, backend_hint="auto", ...)
gms        (x, y, ...)                      # mean of the same map
lpips      (x, y, *, net="alex", data_range=None, return_map=False,
            allow_tf32=False, ...)
ssimulacra2(orig, dist, *, data_range=None, reduction="mean", dtype=None,
            crop_border=0)               # sRGB in, 0..100 out, higher is better
l1         (x, y, ...)
charbonnier(x, y, *, eps=1e-3, ...)         # mean sqrt(d^2 + eps^2)
huber      (x, y, *, delta=1.0, ...)        # matches torch.nn.HuberLoss
rgb_to_luma(t, mode="bt601", *, data_range=None, dtype=None)

lpips has no backend_hint: it is cuDNN convolutions plus a torch.compiled tail, with no C-ABI kernel behind it. fa.available_nets() lists the trunks present in the install and fa.lpips_weights_path() says where they came from.

data_range defaults to 255 for integer input, 1.0 for float. downsample=True on ssim applies MATLAB ssim.m's automatic box-downsample (off by default, as in ssim_index.m and every PyTorch library); on gmsd it is the paper's 2× prefilter and is on by default.

ssimulacra2 is the odd one out on two counts: it takes sRGB-encoded input (it linearises and converts to XYB itself, so linear-light data scores something else), and it is not symmetric — the first argument is the original, because two of its three error maps distinguish "the distortion added an edge" from "the distortion removed one". No luma (it needs all three channels) and no backend_hint yet.

Module forms MSE, PSNR, SSIM, MSSSIM, GMSD, L1, Charbonnier, Huber, LPIPS, SSIMULACRA2 cache what they can and expose .loss() (except SSIMULACRA2, whose final power law has an unbounded derivative at the perfect-match point):

crit = fa.SSIM(data_range=1.0)
loss = crit.loss(pred, target)     # 1 - SSIM, fused backward on CUDA float32
loss.backward()

sm = fa.StreamingMetrics((1, 3, 1080, 1920), device="cuda", dtype=torch.uint8,
                         metrics=("psnr", "ssim", "ms_ssim", "gmsd"))
for ref, dist in frames:
    out = sm.update(ref, dist)     # one graph replay, all four metrics

StreamingMetrics accepts any of mse, psnr, ssim, ms_ssim, gmsd, gms, l1, charbonnier, huber, lpips; they all capture into the same CUDA graph, so scoring a frame on ten metrics is still one replay. LPIPS is capturable because the trunk is loaded and moved to the device during the pre-capture warm-up, leaving convolutions and nothing else inside the captured region.

License

Apache 2.0 — except the bundled LPIPS weights, which carry their upstream BSD terms; see frame_analytics/weights/.

Wang, Bovik, Sheikh, Simoncelli. Image Quality Assessment: From Error Visibility to Structural Similarity. IEEE TIP 13(4), 2004.

Zhang, Isola, Efros, Shechtman, Wang. The Unreasonable Effectiveness of Deep Features as a Perceptual Metric. CVPR 2018.