hytek_parse: Parses Hytek format track and field results inside 'tf_parse'
In JumpeR: Importing and Working with Track and Field Data

Description Usage Arguments Value See Also

Outputs a data frame of track and field results

hytek_parse(
  hytek_file = file,
  hytek_relay_athletes = relay_athletes,
  hytek_rounds = rounds,
  hytek_round_attempts = round_attempts,
  hytek_split_attempts = split_attempts,
  hytek_splits = splits,
  hytek_split_length = split_length
)

`hytek_file`	data with row numbers added
`hytek_relay_athletes`	should `tf_parse` try to include the names of relay athletes for relay events? Names will be listed in new columns "Relay-Athlete_1", "Relay_Athlete_2" etc. Defaults to `FALSE`.
`hytek_rounds`	should `tf_parse` try to include rounds for jumping/throwing events? Please note this will add a significant number of columns to the resulting data frame. Defaults to `FALSE`.
`hytek_round_attempts`	should `tf_parse` try to include rounds results (i.e. "PASS", "X", "O") for high jump and pole value events? Please note this will add a significant number of columns to the resulting data frame. Defaults to `FALSE`
`hytek_split_attempts`	should `tf_parse` split attempts from each round into separate columns? For example "XXO" would result in three columns, one for "X', another for the second "X" and third for "O". There will be a lot of columns. Defaults to `FALSE`
`hytek_splits`	either `TRUE` or the default, `FALSE` - should `hytek_parse` attempt to include splits.
`hytek_split_length`	either the distance at which splits are collected (must be constant distance) or the default, `1`, the length of track at which splits are recorded. Not all results are internally consistent on this issue. If in doubt use the default `1`