CALCULATORS / OPTICS, IMAGING AND ILLUMINATION

Object-space pixel resolution calculator

Planar field size per sensor pixel; no optical MTF model.

optics-pixel-resolution.napkin / editable

SCENARIO COMPARISON

Compare the numbers.

This source describes an analytical model. Its quantities and checks are the view.

Scenario	samplingmm	minimumFeaturemm
	0.104167	0.208333
	0.0833333	0.166667

All calculated quantities are listed with the inputs. Switch to Source to inspect the equations.

SCENARIOS / CALCULATED VALUESSAME SOURCE

Change an input to see the consequences.

sampling budget0.10 mm✓ passes

BASELINE INPUTS

field200 mmpixels1920

CALCULATED

sampling0.10417 mm

minimumFeature0.20833 mm

Edits change the baseline source.

THE SOURCE

Edits below update the same model.

# Object-space pixel resolution
# Scope: Planar field size per sensor pixel; no optical MTF model.
# Status: illustrative worked example; engineering review pending.
# Inputs are example values. Checks are editable example requirements, not standards.

field = 200 mm
pixels = 1920

sampling := field/pixels [mm]
minimumFeature := 2*sampling [mm]

check sampling budget: sampling <= 0.15 mm

scenario alternative: field = 160 mm

Calculated from your source · not saved

Baseline · Baseline

sampling budget0.10 mm ✓ passes

alternative · alternative

sampling budget0.08 mm ✓ passes

Illustrative first-order example. Checks are editable requirements, not design standards. The broader topic may require additional equations, data, and validation.

Formula and units

This example uses the following equations. Input names and units match the editable source above.

sampling: sampling = field/pixels [mm]
minimum feature: minimumFeature = 2*sampling [mm]

Original worked example

These are the baseline values in the downloadable source. Edits above let you test your own values.

Given

field: 200 mm
pixels: 1920

Calculated

sampling: 0.104167 mm
minimum feature: 0.208333 mm

Assumptions and limits

Planar field size per sensor pixel; no optical MTF model.

The requirement checks use the limits written in this example. Passing a check does not establish that the model covers every load, material behavior, or operating condition in a real design.

Download this .napkin example ↓

Take it further with your agent

Napkin keeps the inputs, equations, checks and assumptions together in one study. Your agent sets it up; you change the numbers.

Try with Claude ↗

codex 'Use Napkin (https://napkin.engineering/mcp, or the local Napkin plugin) to build a study: Object-space pixel resolution. Inputs: field of view; pixel count; optical assumptions. Outputs: length per pixel; feature sampling. Model scope: Paraxial geometry or calibrated radiometric/photometric models. Read napkin_capabilities and the current snapshot. Ask me for the values that matter, label assumptions with units, author .napkin source, validate it and apply it with napkin_source using the current revision, then open the study. Add checks for the limits I supply. Keep unsupported analyses explicit.'

Claude needs the Napkin connector; Codex needs the Napkin plugin. Set up your agent ↗

The broader study

The topic brief below describes the broader scope. The worked example above states the particular calculation it implements.

Inputs: field of view, pixel count, optical assumptions
Outputs: length per pixel, feature sampling
Modes: calculate, compare, sweep
Drawing: Ray diagram and camera view

EXECUTABLE WORKED EXAMPLE · FIRST-ORDER MODEL · CHECK THE SCOPE & ASSUMPTIONS