Foundry & Forging worked example

Riser Yield Impact at 18% target riser weight share: a worked example

This scenario runs the riser yield impact calculation on the strong side: 18% target riser weight share, with every other input held at its documented default. Use it when evaluating riser sizing, feeding practice, simulation changes, exothermic sleeves, chills, or pattern changes.

The inputs for this scenario

  • Riser and feeder weight: 950 lb (unchanged)
  • Total pour weight: 6,200 lb (unchanged)
  • Target riser weight share: 18 % (raised for this scenario; the documented default is 16)

Working through the calculation

  • Applying the documented formula (Riser Yield Impact rate = riser and feeder weight ÷ total pour weight × 100) to the inputs above produces each figure below.
  • At this operating point the engine returns 15.32 % for riser yield impact rate, the number this scenario is built around.
  • At this operating point the engine returns 2.68 points for riser yield impact gap to target.
  • At this operating point the engine returns 950 count for riser and feeder weight.
  • At this operating point the engine returns 6,200 count for total pour weight.

How this compares with the baseline

  • Against the tool's baseline example, where target riser weight share sits at 16% and the headline result is 15.32 %, this scenario lands almost exactly on the baseline at 15.32 %.
  • Use it when reviewing a rigging design or methoding simulation to judge whether feeder metal is in a reasonable range for the alloy and section thickness. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.

Results at a glance

  • Riser Yield Impact rate: 15.32 % (headline result)
  • Riser Yield Impact gap to target: 2.68 points
  • Riser and feeder weight: 950 count
  • Total pour weight: 6,200 count

Run it with your numbers

  • Every input above is editable in the live Riser Yield Impact calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.