Files
presentation-html/references/registry-animejs-logistics.md

41 lines
4.2 KiB
Markdown

# Logistics · original Anime.js industry recipes
[Overall gallery](../dist/animejs-gallery-0.6.0/index.html) · [Logistics gallery](../dist/animejs-gallery-0.6.0/logistics/index.html)
Editable original SVG, conceptual and not operational guidance. No external imagery, patient data or operational statistics. Every count, rate, capacity and timing is illustrative.
[Renderer source](../assets/animejs/industries/logistics.js) · [Catalog/configuration](../assets/animejs/catalogs/logistics.json) · [Shared lifecycle and seeking](choreography.md)
| ID | Question / audience | Individual preview |
| --- | --- | --- |
| `logistics-hub-connection-recovery` | Explain why physical sorting and departure cutoffs are separate dependencies; useful for hub planning and service design. | [Open](../dist/animejs-gallery-0.6.0/examples/logistics-hub-connection-recovery.html) |
| `logistics-port-crane-yard` | Explain interdependent marine and landside work to planners; show that crane motion alone does not complete a transfer. | [Open](../dist/animejs-gallery-0.6.0/examples/logistics-port-crane-yard.html) |
## Hub sorting: recover a missed connection
**Narrative:** Induct → Read & sort → Cutoff missed → Stage safely → Reconnect → resolved overview.
Follow a late parcel from induction through sorting, a missed departure, exception staging and a later connection.
**Visual explanation:** Cyan = planned path · Amber = late parcel · Green = recovery connection. Stable labels preserve the exception and recovery explanation at the final state. Physical objects use local SVG groups; route drawing encodes direction, not decorative travel.
**Anime.js v4 techniques:** a paused finite `createTimeline`; explicit from/to SVG attributes, opacity and group translations; path dash-offset drawing using measured SVG lengths. Constant-value tweens hold states; no callbacks, random values, listeners, autoplay or external resources.
**Editable config:** `recoveryConnection` names the alternative departure lane (short text, up to 22 characters). `duration` (default `6000`, positive finite milliseconds) scales every tween and phase together. Default beat times are 0, 1200, 2400, 3600, 4800 and 6000 ms. If changing duration, scale catalog seek targets and retest playback, intermediate/final views, bounds and reverse seeking. Geometry is intentionally edited in source rather than exposing misleading operational parameters.
**Limits:** Original conceptual hub. All timings, positions, capacities and departure windows are illustrative; one parcel represents a tracked consignment. Do not present this as a route optimizer, carrier SLA, throughput benchmark or promise of delivery.
## Port coordination: berth, crane and yard
**Narrative:** Berth ready → Lift approved → Lane blocked → Reassign slot → Yard receipt → resolved overview.
A container moves only after berth access, crane clearance and a yard slot align; a blocked lane prompts reassignment.
**Visual explanation:** Amber = container · Red = unavailable lane · Green = assigned yard slot. Stable labels preserve the exception and recovery explanation at the final state. Physical objects use local SVG groups; route drawing encodes direction, not decorative travel.
**Anime.js v4 techniques:** a paused finite `createTimeline`; explicit from/to SVG attributes, opacity and group translations; path dash-offset drawing using measured SVG lengths. Constant-value tweens hold states; no callbacks, random values, listeners, autoplay or external resources.
**Editable config:** `yardSlot` names the assigned recovery slot (short text, up to 8 characters); it appears at the physical receipt location. `duration` (default `6000`, positive finite milliseconds) scales every tween and phase together. Default beat times are 0, 1200, 2400, 3600, 4800 and 6000 ms. If changing duration, scale catalog seek targets and retest playback, intermediate/final views, bounds and reverse seeking. Geometry is intentionally edited in source rather than exposing misleading operational parameters.
**Limits:** All geometry, timing and resource counts are illustrative. Original conceptual port; not an equipment or safety simulation. Avoid crane operating instruction, nautical guidance, capacity forecasts or safety clearance claims.