Wireless Mic Frequency Coordination Plan Generator

Stable input-order greedy candidate pair-spacing screen using independently verified allowed-frequency flags. Not optimal spectrum allocation, intermodulation/occupancy analysis, licensed coordination or interference-free operation; no live radio changes.

Description

Candidate wireless frequencies can be screened for permitted status and pairwise spacing.

Candidate wireless frequencies can be screened for permitted status and pairwise spacing.^[1]

Frequency spacing alone does not resolve intermodulation, occupancy or licensing.

When to use Wireless Mic Frequency Coordination Plan Generator

Use this tool to calculate or review the supplied observations under the stated rules. Establish the production, adopted practice, equipment configuration and applicable source or policy edition.

How to use Wireless Mic Frequency Coordination Plan Generator and understand its results

Establish the production, adopted practice, equipment configuration and applicable source or policy edition.
Enter callerCandidateFrequenciesMHz, independentlyVerifiedCandidateAllowedFlags, callerMinimumPairSpacingMHz, using the field meanings and rules below, then run the tool.
Read greedySelectedCandidateIndices and notSelectedCandidateIndices as zero-based positions. Review spectrum conditions separately from this spacing filter.
Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.

Input field	Meaning	Value type	Requirement
callerCandidateFrequenciesMHz	Caller candidate frequencies m hz	list of number	Required
independentlyVerifiedCandidateAllowedFlags	Independently verified candidate allowed flags	list of number	Required
callerMinimumPairSpacingMHz	Caller minimum pair spacing m hz	number	Required

Supply nonempty aligned positive frequencies and binary externally permitted flags, with positive minimum spacing in the same frequency units. Traverse entries in input order. Select an allowed entry only if its distance from every earlier selected frequency is at least the spacing; exact equality is accepted. Return zero-based chosen and not-selected indices, including disallowed entries among not-selected. This greedy order-dependent filter does not optimize the set or analyze interference products.

select_i=allowed_i and ∀j previously selected(|frequency_i−frequency_j|≥spacing)

Use the matching field units and the exact boundary, ordering and reference rules above.

Output field	Meaning	Value type
result	Calculated observation or qualified reference	object
result.greedySelectedCandidateIndices	Zero-based indices selected by the input-order permitted-frequency spacing filter.	list
result.notSelectedCandidateIndices	Zero-based candidate indices omitted because disallowed or too close to an earlier selection.	list

json

{
  "input": {
    "callerCandidateFrequenciesMHz": [
      100,
      100.1,
      100.3
    ],
    "independentlyVerifiedCandidateAllowedFlags": [
      1,
      1,
      1
    ],
    "callerMinimumPairSpacingMHz": 0.2
  },
  "output": {
    "result": {
      "greedySelectedCandidateIndices": [
        0,
        2
      ],
      "notSelectedCandidateIndices": [
        1
      ]
    }
  }
}

Limitations and assumptions

The actual production context, equipment configuration and applicable reference must be independently established. A recorded reference or calculation does not authorize a procedure or demonstrate compliance.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries, subject to the narrower lengths and code rules above. Extremely large composite outputs are rejected.

Alternative or Complementary methods

For a related step, use Fixture Profile Personality Library Patching Attributes Lookup: Fixture personalities describe attributes and footprints for a particular firmware and operating mode. For a complementary comparison, use Media Server Playback Disguise Resolume Layer Mapping Lookup: Media-server layers and output mappings depend on project, software version and hardware routes.

References

Wireless Mic Frequency Coordination Plan Generator — tool.io

Similar or alternative tools

Fixture Profile Personality Library Patching Attributes Lookup
Fixture personalities describe attributes and footprints for a particular firmware and operating mode.
Media Server Playback Disguise Resolume Layer Mapping Lookup
Media-server layers and output mappings depend on project, software version and hardware routes.