Infragravity Surf Beat Band Lookup
Audit independently observed surf-beat frequencies against caller independently verified instrument/study infragravity band, unknown calibration explicitly retained. Unknown criterion indices distinguish zero placeholders from known zero margins. Caller independently establishes units, regime, calibration and applicability; this does not establish design-code compliance, authenticity, operational safety, treatment efficacy or a validated forecast.
Description
Infragravity surf-beat frequency bands depend on the study and measurement convention.
Infragravity surf-beat frequency bands depend on the study and measurement convention.1
This tool compares known coordinates with your inclusive bands while preserving unknown criteria separately.
When to use Infragravity Surf Beat Band Lookup
Use this tool to calculate or review the supplied observations under the stated rules. Match the observation interval, units, datum, coordinate signs and model regime.
How to use Infragravity Surf Beat Band Lookup and understand its results
- Match the observation interval, units, datum, coordinate signs and model regime.
- Enter observedInfragravityFrequencyHz, callerVerifiedInfragravityFrequencyHzLower, callerVerifiedInfragravityFrequencyHzUpper, knownInfragravityFrequencyHzCriterionFlags, using the field meanings and rules below, then run the tool.
- Read signedKnownBandMargins, knownReviewIndices, unknownCriterionIndices. Inspect nested result fields where present, and review unknown records separately from known matches.
- 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 |
|---|---|---|---|
| observedInfragravityFrequencyHz | Observed infragravity frequency hz | list of number | Required |
| callerVerifiedInfragravityFrequencyHzLower | Caller verified infragravity frequency hz lower | list of number | Required |
| callerVerifiedInfragravityFrequencyHzUpper | Caller verified infragravity frequency hz upper | list of number | Required |
| knownInfragravityFrequencyHzCriterionFlags | Known infragravity frequency hz criterion flags; binary 1 means the matched observation is known, 0 means unknown | list of number | Required |
Use nonempty aligned finite observations, lower and upper bounds, and binary known flags. Require lower≤upper for every row. For known rows return min(observed−lower,upper−observed); strictly negative margins enter the review list. Unknown rows receive zero placeholders and appear in the separate unknown-criterion list. A known boundary is included; an unknown zero is not passing evidence.
margin_i=known_i?min(observed_i−lower_i,upper_i−observed_i):0 Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| signedKnownBandMargins | Signed known band margins; preserve the subtraction order and sign defined in the mechanics | list of number |
| knownReviewIndices | Known review indices; zero-based positions in the relevant supplied record or adjacent-pair list | list of number |
| unknownCriterionIndices | Unknown criterion indices; zero-based positions in the relevant supplied record or adjacent-pair list; unresolved records kept separate from known results | list of number |
{
"input": {
"observedInfragravityFrequencyHz": [
2,
5
],
"callerVerifiedInfragravityFrequencyHzLower": [
1,
1
],
"callerVerifiedInfragravityFrequencyHzUpper": [
3,
4
],
"knownInfragravityFrequencyHzCriterionFlags": [
1,
0
]
},
"output": {
"signedKnownBandMargins": [
1,
0
],
"knownReviewIndices": [],
"unknownCriterionIndices": [
1
]
}
}Limitations and assumptions
The stated observation or model covers only the supplied record and reference regime. It does not fill missing measurements, supply uncertainty estimates or produce a validated forecast.
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; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.
Alternative or Complementary methods
For a related step, use Setup Plus Swash Stockdon Split Calculator: Wave setup and swash contribute to extreme runup on a beach. For a complementary comparison, use Rogue Wave Threshold Significant Checker: A rogue-wave screen compares individual wave height with significant height from the same observation window.
References
-
Infragravity Surf Beat Band Lookup — tool.io
Similar or alternative tools
- Setup Plus Swash Stockdon Split Calculator
Wave setup and swash contribute to extreme runup on a beach.
- Rogue Wave Threshold Significant Checker
A rogue-wave screen compares individual wave height with significant height from the same observation window.