4.6 KiB
Infrastructure — 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 |
|---|---|
infrastructure-bridge-inspection |
Bridge: load paths and inspection closure |
infrastructure-construction-resequence |
Construction: dependency and resequencing |
Bridge: load paths and inspection closure
Audience / use: Use only to introduce the relationship between visible bridge components, conceptual load transfer and controlled access during review.
Narrative: Apply load → Trace path → Inspect → Close lane → Review repair → complete readable state.
Model assumptions: Original schematic, not a bridge design. Geometry, vehicle load, paths and timing are unscaled illustrations. A qualified professional must determine actual structural behavior and access decisions.
Recipe-specific control: loadX sets the illustrative vehicle load location, clamped to 300–420 SVG units (default 385); vehicle and load arrow move together. This does not calculate force.
Avoid: Never use as structural engineering analysis, load capacity, safety assurance, inspection checklist, repair selection or reopening authorization.
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.
Construction: dependency and resequencing
Audience / use: Help project teams distinguish work that can be resequenced from a critical prerequisite that cannot be bypassed.
Narrative: Baseline → Permit hold → Identify float → Resequence → Gate lift → complete readable state.
Model assumptions: All axis values and timings are illustrative without calendar units. Fabrication is assumed independent and resources available; the permit gate remains unresolved rather than implying authorization.
Recipe-specific control: advanceSlots controls off-site work advancement by 0.5–2 schematic axis slots (default 1.5); the permit gate does not move.
Avoid: Not a computed critical-path schedule, construction-method statement, permit prediction, resource model or lift plan.
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.