Polyrhythm 3-against-2 Clap Grid Generator
Endpoint-exclusive 3-against-2 pulse grid over one caller common cycle; common cycle end is next cycle start, not a duplicated seventh point. Caller independently establishes score/style/protocol/reference applicability; not physical readiness, safe training or injury risk diagnosis.
Description
Three-against-two polyrhythm places different pulse divisions within one shared cycle.
Three-against-two polyrhythm places different pulse divisions within one shared cycle.1
A generated time grid describes pulse locations rather than an audio performance. Use Polyrhythm 3-against-2 Clap Grid Generator to evaluate the supplied inputs under the specific model below.
When to use Polyrhythm 3-against-2 Clap Grid Generator
Use Polyrhythm 3-against-2 Clap Grid Generator to evaluate the supplied inputs under the specific model below. Establish the units, measurement scope and applicable model or recipe assumptions before entering values.
How to use Polyrhythm 3-against-2 Clap Grid Generator and understand its results
- Establish the units, measurement scope and applicable model or recipe assumptions before entering values.
- Enter Caller cycle duration seconds using the field table and validation rules below, then run the tool.
- Read Three pulse times seconds, Two pulse times seconds, Coincident pulse times seconds and interpret units, signs, ordering and placeholders as explained below.
- If the tool reports an input error, correct that field and rerun. A successful false result, empty match list or unknown-evidence placeholder has the specific meaning described here; check the limitations before applying the result.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerCycleDurationSeconds | Caller cycle duration seconds | number | Required; constraints below |
Enter a positive cycle duration in seconds. Return three pulses at 0, T/3 and 2T/3, two pulses at 0 and T/2, and the shared onset [0]. The endpoint T belongs to the next cycle and is omitted. These are ideal timing coordinates rather than synthesized sound or movement analysis.
threePulses = [0,T/3,2T/3]; twoPulses = [0,T/2]; coincidences = [0] Field order, units and branch conditions follow the implementation explanation above.
| Output field | Meaning | Value type |
|---|---|---|
| threePulseTimesSeconds | Three pulse times seconds | array of number |
| twoPulseTimesSeconds | Two pulse times seconds | array of number |
| coincidentPulseTimesSeconds | Coincident pulse times seconds | array of number |
{
"input": {
"callerCycleDurationSeconds": 6
},
"output": {
"threePulseTimesSeconds": [
0,
2,
4
],
"twoPulseTimesSeconds": [
0,
3
],
"coincidentPulseTimesSeconds": [
0
]
}
}Limitations and assumptions
A generated time grid describes pulse locations rather than an audio performance. Apply the exact scope and assumptions described above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are stated above; extremely large inputs or outputs can also be rejected. These errors differ from successful results such as false, no matches or unknown evidence.
Alternative or Complementary methods
Use Waltz Bar 3/4 Measure Map for a related task: A three-beat measure divides a beat ordinal into bar and within-bar positions.
Use Bars Per Phrase 32 Count Conversion for a related task: Phrase counts convert to bars only through a declared count-to-beat and beat-to-bar convention.
References
Similar or alternative tools
- Waltz Bar 3/4 Measure Map
A three-beat measure divides a beat ordinal into bar and within-bar positions.
- Bars Per Phrase 32 Count Conversion
Phrase counts convert to bars only through a declared count-to-beat and beat-to-bar convention.