Barry Stripes Count and Width Solver

Divide explicit fieldHeight into caller ordered stripe weights; does not infer tinctures or mandated stripe counts.

Description

Barry describes a field divided into horizontal bands; the bands occupy the height of the field.

Barry describes a field divided into horizontal bands; the bands occupy the height of the field.1

Unequal supplied weights can model a layout, but do not establish a conventional stripe count or tincture sequence. Use this tool to calculate barry stripes count and width solver from the supplied measurements and assumptions.

When to use Barry Stripes Count and Width Solver

Use this tool to calculate barry stripes count and width solver from the supplied measurements and assumptions. Establish the source, heraldic authority or layout convention, and use one consistent coordinate and length basis.

How to use Barry Stripes Count and Width Solver and understand its results

  1. Establish the source, heraldic authority or layout convention, and use one consistent coordinate and length basis.
  2. Enter fieldHeight, stripeWeights, using the field meanings and rules below, then run the tool.
  3. Read result.widths, result.boundaries. Interpret the fields using their units, signs and evidence conventions below.
  4. If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
Input fieldMeaningValue typeRequirement
fieldHeightField heightnumberRequired
stripeWeightsStripe weightslist of numberRequired

Require positive field height and positive stripe weights with a positive total. Divide height proportionally among weights in their supplied order, then accumulate widths from zero to obtain boundaries. Widths and boundaries use the same unit as fieldHeight; the count comes from the list length. The implementation does not choose tinctures or enforce equal alternating heraldic bars.

width_i=fieldHeight×weight_i/Σweights; boundaries=[0,cumulative sums of widths]

Use the exact units, boundary rules, ordering and missing-evidence conventions above.

Output fieldMeaningValue type
resultStructured calculation or selected reference, with fields listed belowobject
result.widthsWidths; follow the units, sign, ordering and evidence convention stated abovelist of number
result.boundariesBoundaries; follow the units, sign, ordering and evidence convention stated abovelist of number
json
{
  "input": {
    "fieldHeight": 100,
    "stripeWeights": [
      1,
      1,
      2
    ]
  },
  "output": {
    "result": {
      "widths": [
        25,
        25,
        50
      ],
      "boundaries": [
        0,
        25,
        50,
        100
      ]
    }
  }
}

Limitations and assumptions

Unequal supplied weights can model a layout, but do not establish a conventional stripe count or tincture sequence. Interpretation depends on the units, sampling scope and exact model described above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.

Alternative or Complementary methods

Use Banner Shape Ratio to Shield Converter for this related task: A shield envelope's width-to-height ratio can be reused as a rectangular banner proportion.

Use Azure Frequency Rank Finder in Roll when its separate inputs and assumptions fit the question: A tincture frequency rank describes its position within a particular counted corpus of arms.

References

  1. Barry Stripes Count and Width Solver — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies