OpenTag & Sportscode → LSA Converter

Button name mode: the Row column (the Sportscode button name) is used directly as the event code — no dimension mapping needed. Each Start→End pair becomes one GSEQ session. THEME receives the full event stream with real timestamps. Press Start at the whistle, End after resolution.

Which SDIS type should I use? Use %SS (state sequence) if the duration of each behaviour matters for your LSA — GSEQ will calculate expected vs observed co-occurrences weighted by time. Use %EV (event sequence) if you only care about the order of behaviours, not how long each lasted. Most sport science LSA papers use %SS.

Constant duration: when your data has no per-event duration (pure event data), assigning a uniform duration lets THEME and GSEQ run on ordinal structure. This follows Lapresa et al. (2013), who conventionally assigned a constant of 10 frames (≈100 ms) per occurrence and showed it reproduces the same patterns as real-time data. State the constant in your methods.

A new sequence starts whenever the gap between the end of one instance and the start of the next exceeds the threshold. This approximates the referee reset between scored points. Review the table below and adjust the threshold or override individual assignments. For future data, add a Sequence code button to Sportscode and press it at each reset — that gives ground truth instead of inference.

The selected column's value will be appended to each event code — e.g. CutKick_Chong_Retreat_NoScore_Seq03. Each unique value in the column becomes a separate GSEQ session, so THEME and GSEQ analyse within-sequence patterns.

A working floor of 20 instances per code is widely used for stable adjusted residuals in GSEQ (Bakeman & Quera, 2011). Codes in amber (<20) are approaching that floor; red (<5) are too sparse to trust. Options: code more matches, combine rare codes with GSEQ's LUMP command, or use fewer/broader codes.