PrimeBite Fishing Northern Pike Research & Methodology

Northern Pike — Research & Methodology (v3)

Last updated: 2026-05-17

This page documents the variables we use for Northern Pike (v3), the open-access URLs behind each driver, verbatim quotes, and what is research-backed vs calibrated. We keep proprietary calibration details private.

How it works (overview)

Northern Pike (v3) is a freshwater all-day rating with no Major/Minor bite times. The live Pike driver story is simple: dusk is the main driver, wind is second, and moon phase is smaller. Research chooses the drivers; we calibrate the final mapping into 1.0-5.0. Exact numeric tuning stays private.

The live app shows a direct Pike math breakdown with plain-English row labels: Dusk window (civil twilight), Daily wind (X mph average), and Moon phase (Name — new/full helps) are real Pike score rows from Kuparinen 2010. The final row, Scale calibration (PrimeBite), is a math step (not a fishing variable) that stretches Pike's naturally narrow score range across the full 1–5 scale; it is labeled honestly rather than hidden. If weather is still missing on a future Pike day, the app uses dusk plus moon only until wind arrives, and it still shows the real dusk window from local civil twilight.

Pike is rated once per day, not by the hour. A second study (Arlinghaus 2017, same lake as Kuparinen, 3,232 fishing sessions at 15-minute resolution) directly tested whether Pike catch rates change within a day and found no significant effect. We honor that finding by NOT showing an hourly Pike chart or a wind-driven rating range.

Study limitations (Kuparinen 2010)

Northern Pike v3 is anchored to a single peer-reviewed open-access study — every driver (dusk, wind, moon phase) cites this same paper. We disclose the following limitations so users do not assume ratings apply universally:

• Single location: One small lake (25 ha), Kleiner Döllnsee, north-east Germany (N52°59′, E13°34′).
• Single season: Data from 27 May to 17 September 2005 only.
• Protected environment: The lake was protected from any commercial or public recreational fishing during the study—unlike typical multi-use waters.
• Limited generalizability: The authors note that “a substantial amount of variation in catch rates remained unexplained” (Fisheries Research 105, 2010, p.116).

PrimeBite uses the evidence-backed direction of effects from this study and calibrates the display scale to produce a stable 1.0-5.0 day rating. Ratings are relative indicators, not guarantees; they are anchored to a limited dataset and a transparent calibration step.

Variables (what’s research-backed vs calibrated)

Research-backed means the driver/pattern is supported by open-access sources. Calibrated means we chose the exact thresholds/weights/caps to make a stable 1–5 score.

Moon phase

Research-backed: Pike catch rates peak around full and new moon.

Calibrated: the exact curve shape and size used to map that pattern into the final score.

Implementation: a smooth new/full peak curve is used as a smaller all-day input. Moon phase is not the main Pike story in v3.

Source (open access): Kuparinen et al. 2010 — Fisheries Research (PDF)

“Catch rates of pike were significantly increased … around full and new moon …”

(printed p.111 Abstract; see app repo extracts: docs/_pdf_cache/pike/extracts/_extract_Kuparinen_2010_p1.txt)

Wind speed

Research-backed: within the observed range in Kuparinen (2010), higher wind speed is associated with increased catch rates.

Calibrated: the exact mapping from mph to score adjustment. We use a simple positive boost capped at the observed range and do not apply penalties without evidence.

Implementation: wind is the second Pike driver in v3 and is capped at the observed range from the study.

Source (open access): Kuparinen et al. 2010 — Fisheries Research (PDF)

“Catch rates of pike were significantly increased … at … high wind speeds …”

(printed p.111 Abstract; see app repo extracts: docs/_pdf_cache/pike/extracts/_extract_Kuparinen_2010_p1.txt)

Dusk / civil twilight

Research-backed: Pike catch rates are higher during dusk.

Calibrated: the magnitude of the dusk lift, and the choice to apply dusk as a fixed all-day driver (instead of a minute-by-minute bite-time model), are PrimeBite design choices.

Implementation: dusk is the main Pike driver in v3. Civil twilight is still used for the displayed “best time,” but the day score does not pretend to be an hourly chart. Future Pike dates keep showing that dusk timing from local civil twilight even when weather is still pending.

Source (open access): Kuparinen et al. 2010 — Fisheries Research (PDF)

“Catch rates of pike were significantly increased … as well as during dusk.”

(printed p.111 Abstract; see app repo extracts: docs/_pdf_cache/pike/extracts/_extract_Kuparinen_2010_p1.txt)

Explicitly not used for Pike (v3)

• Major/Minor solunar position windows (“bite times”): not used for Pike because we do not have verified open-access evidence for daily Pike position-window effects.
• Hourly chart: not used because Pike does not yet have Bass-level hour-by-hour support.
• Water temperature: not used in live Pike v3 even though it appears in Pike research, because this rebuild was intentionally frozen around dusk, wind, and moon only.
• Wind direction, precipitation, pressure, humidity, and seasonality: not used in the live Pike v3 score.
• Night-vs-day “night preference”: not used; Kuparinen (2010) compares daytime vs dusk, not night activity.
• Fake visible point rows: not used. Pike shows direct Dusk window (civil twilight), Daily wind (X mph average), and Moon phase rows plus a truthfully-labeled Scale calibration (PrimeBite) row that is the final display-mapping step. We label the math step honestly instead of hiding it inside a driver.

Key definitions & verification sources

These definitions are not Pike biology claims — they are the astronomy/time definitions required to compute inputs consistently. In the app repo, the cached definition PDFs and extracted quotes live under docs/_pdf_cache/definitions/.

• Civil twilight: sunset → sun’s center 6° below the horizon (FAA/UCCS definition PDFs cached in the app repo; see docs/PIKE_VARIABLES_FACTCHECK.md section D2).
• Moon phase vs illumination: phase position (0..1) is not the same thing as illuminated fraction (0..1). Pike’s pike-newfull model uses phase position (see docs/PIKE_VARIABLES_FACTCHECK.md section D1).

Changelog

• 2026-05-17: Pike Option 3 (Evidence Purist) lock-in. Direct math row labels switched to plain English (Dusk window (civil twilight), Daily wind (X mph average), Moon phase (Name — new/full helps), Scale calibration (PrimeBite)). Added Arlinghaus 2017 NULL finding on within-day variation. Pike app hero no longer shows a wind-driven rating range — Pike is a single daily rating. Scoring math unchanged from v3. Same-day calibration backfill: ran a formal 125-combo A/B/C grid over the three Pike magnitudes and documented the result in the internal rating decisions log (scoring math still unchanged; live values ratified as the conservative choice). Independent Opus 1M auditor verified the sweep math and reproduced the result byte-for-byte. Phase 1 wind-aggregation fix: Pike's wind input was switched from an app-open-time snapshot to a true 24-hour daily mean across every Pike surface (Today, Forecast, Logbook, notifications), faithfully replicating Kuparinen 2010's stated "daily averages" methodology. Pike ratings are now stable across the day regardless of when the user checks. Scoring math constants unchanged. The Pike notifications path was also re-routed to use the same scoring model as the app screens.
• 2026-03-20: Page updated to the live Pike rebuild v3 story. Dusk is documented as the main Pike driver, wind as second, and moon as smaller. Added the truthful direct-math explanation note and the future-dusk-timing rule for weather-missing days.
• 2026-02-15: Original Pike v1 methodology page published.