Looks fine to me. I agree with you that your pairing_system and
initial_schedule lines are now redundant. I'd say the same goes for
force_koth too since in your autopair lines you have specified KOTH
for the final rounds anyway.

Stewart



2009/5/5 G. Vincent Castellano <gvc@...>:
> Thanks to the DRYrun command, I think I've got the config.tsh shaken out.  Now
> I'm looking for a sanity-check on my whole program.
>
> We have 84 registrants in 4 divisions for 7 rounds.  I'm doing the data entry
on
> my own, and nothing but computer operations.  I'll use Fontes for 1-3, and
> NewSwiss for Round 4 (based on results from 2).  There is a lunch break after
4,
> so I will do NewSwiss for 5 based on 4, then 2 KotH (no-repeat followed by one
> allowed) for 6 and 7.
>
> We have the hall from 8 to 6, so are planning on starting at 9 and ending at 5
> sharp.
>
> Is this all workable?  Any hidden glitxhes with the config below?  (autopair
> commands for b, c, and d divisions are identical to a.)  I believe the
> 'pairing_system' and 'initial_schedule' are obviated by the autopair commands.
>
>
>
> config pairing_system = 'chew'
> config max_rounds = 7
> config initial_schedule = 3
> config prize_bands{'a'} = [1,2,3]
> config prize_bands{'b'} = [1,2,3]
> config prize_bands{'c'} = [1,2,3]
> config prize_bands{'d'} = [1,2,3]
> config director_name = "Mary-Lou Goetz"
> config event_date = "May 9, 2009"
> config event_name = "Annapolis Scrabble Tour 2009"
> config force_koth = 1
> # config session_breaks = [12]
> config no_boards = 1
> config gibson = 1
> config pair_page_break = 25
>
> autopair a 0 1 if 3 a
> autopair a 2 4 ns 0 2 a
> autopair a 4 5 ns 0 4 a
> autopair a 5 6 koth 0 5 a
> autopair a 6 7 koth 1 6 a
>
> --gvc
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>