Files
presentation-html/references/registry-animejs-agriculture.md
T

4.4 KiB
Raw Blame History

Agriculture — original Anime.js scenes

Two editable, conceptual educational models; neither is an operational simulation. Geometry is original SVG with no external assets.

Overall gallery · Industry gallery

Source module · Catalog JSON · Shared lifecycle and seeking

ID Question / individual preview
agriculture-irrigation-zones Irrigation: measure, open, soak, close
agriculture-harvest-grading Harvest: grade, store and distribute

Irrigation: measure, open, soak, close

Audience / use: Explain feedback-based irrigation zoning and why neighboring strips need not receive identical watering.

Narrative: Read soil → Open north → Soak north → Open south → Close valves → complete readable state.

Model assumptions: All phase times and moisture-gauge levels are illustrative without physical units. Soil response is compressed and no weather, runoff or hydraulic model is included.

Recipe-specific control: wetZone chooses the bypassed field strip: 0 north, 1 middle (default), or 2 south. Other zones receive sequential illustrative watering.

Avoid: Not irrigation design, sensor calibration, crop-specific moisture advice, water-rights guidance or pump sizing.

Anime.js techniques: one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (pathLength=1 and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay.

Editable configuration: duration is the total illustrative timeline length in milliseconds, default 6000; the renderer clamps it to at least 3000. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs.

Readable final state: all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide.

Harvest: grade, store and distribute

Audience / use: Use with supply-chain audiences to explain grade-dependent destinations without losing harvest-lot traceability.

Narrative: Receive lot → Inspect → Separate → Store → Dispatch → complete readable state.

Model assumptions: All timing and illustrated produce are conceptual. Two quality destinations are simplified; disposal, pathogen checks and detailed cold-chain controls are outside scope.

Recipe-specific control: freshCount sets how many of four illustrative produce markers enter the fresh-grade store, clamped to 1–3 (default 3); remaining markers enter the processing bin. This is not a yield estimate.

Avoid: Not a food-safety process, storage-temperature prescription, yield forecast or grading standard.

Anime.js techniques: one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (pathLength=1 and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay.

Editable configuration: duration is the total illustrative timeline length in milliseconds, default 6000; the renderer clamps it to at least 3000. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs.

Readable final state: all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide.