make_lineup

Determine optimal entries against a given opponent lineup

The goal of the 'SwimmeR' package is to provide means of acquiring, and then analyzing, data from swimming (and diving) competitions.  To that end 'SwimmeR' allows results to be read in from .html sources, like 'Hy-Tek' real time results pages, '.pdf' files, 'ISL' results, 'Omega' results, and (on a development basis) '.hy3' files.  Once read in, 'SwimmeR' can convert swimming times (performances) between the computationally useful format of seconds reported to the '100ths' place (e.g. 95.37), and the conventional reporting format (1:35.37) used in the swimming community.  'SwimmeR' can also score meets in a variety of formats with user defined point values, convert times between courses ('LCM', 'SCM', 'SCY') and draw single elimination brackets, as well as providing a suite of tools for working cleaning swimming data.  This is a developmental package, not yet mature.

Greg Pilgrim

SwimmeR

Data Import, Cleaning, and Conversions for Swimming Results

Caitlin Baldwin

make_lineup function

<dl><dt>df</dt>
<dd>a data frame of times for the team to be entered. Must contain
column <code>Event</code> with the same event naming convention as <code>op_df</code>,
a column with name matching <code>result_col</code> containing times or diving
scores, and a column called <code>Name</code> containing athlete names</dd>
<dt>op_df</dt>
<dd>a data frame containing the opponent lineup. Must contain
column <code>Event</code> with the same event naming convention as <code>df</code>,
a column with name matching <code>result_col</code> containing times or diving
scores, and a column called <code>Name</code> containing athlete names</dd>
<dt>point_values</dt>
<dd>either a recognized string or a list of numeric values
containing the points awarded by place. Recognized strings are
<code>"hs_four_lane"</code>, <code>"hs_six_lane"</code>, <code>"ncaa_six_lane"</code></dd>
<dt>result_col</dt>
<dd>the name of a column, present in both <code>df</code> and
<code>op_df</code> that contains times and/or diving scores</dd>
<dt>events</dt>
<dd>a list of events. If no list is entered then <code>events</code>
will be taken from <code>unique(op_df$Event)</code></dd>
<dt>max_entries</dt>
<dd>the number of entries a team is permitted per race.
usually half the number of lanes in the competition pool</dd>
<dt>max_ind_entries</dt>
<dd>the number of indivdual events a given athlete may
enter</dd></dl>

Arguments

Determine optimal entries against a given opponent lineup — make_lineup

<dl>

<dt>df</dt>
<dd>a data frame of times for the team to be entered. Must contain
column <code>Event</code> with the same event naming convention as <code>op_df</code>,
a column with name matching <code>result_col</code> containing times or diving
scores, and a column called <code>Name</code> containing athlete names</dd>


<dt>op_df</dt>
<dd>a data frame containing the opponent lineup. Must contain
column <code>Event</code> with the same event naming convention as <code>df</code>,
a column with name matching <code>result_col</code> containing times or diving
scores, and a column called <code>Name</code> containing athlete names</dd>


<dt>point_values</dt>
<dd>either a recognized string or a list of numeric values
containing the points awarded by place. Recognized strings are
<code>"hs_four_lane"</code>, <code>"hs_six_lane"</code>, <code>"ncaa_six_lane"</code></dd>


<dt>result_col</dt>
<dd>the name of a column, present in both <code>df</code> and
<code>op_df</code> that contains times and/or diving scores</dd>


<dt>events</dt>
<dd>a list of events. If no list is entered then <code>events</code>
will be taken from <code>unique(op_df$Event)</code></dd>


<dt>max_entries</dt>
<dd>the number of entries a team is permitted per race.
usually half the number of lanes in the competition pool</dd>


<dt>max_ind_entries</dt>
<dd>the number of indivdual events a given athlete may
enter</dd>

</dl>

make_lineup: Determine optimal entries against a given opponent lineup

Description

Usage

Value

Arguments