Coverage
One setup. Several jobs.
The compare page asks which of your systems fits one job. This asks the opposite, and it is the question you actually face when packing: does this rod cover the river day and the lake day, or are you carrying two? Same reading, run once per job. Nothing is averaged across them — a job without enough evidence stays unassessed on its own terms.
The finding, why it matters, and the fix
The system under test
Jobs it would have to cover (0 selected)
Name a trip from a saved job
Coverage against your own kept jobs is the product. Worked examples are a demonstration of the reading, not somebody’s season. Save the current job as a named trip below, then run coverage on that — do not read a preset grid as your year.
Your trips
0 of 24 kept
The days you actually fish, kept by name. Set a job up in the console, then keep it here; coverage runs the setup against every trip you select. Trips stay in this session, in this browser, and travel only inside a session export.
Nothing to keep yet — state a water type or a target class in the setup.
No trips kept yet. Until there are, coverage can only be run against the job in your setup and the worked examples below — which is a demonstration rather than an answer about your own season.
Choose the jobs this setup would have to cover.