I sent the following to JCIII, but then it ocurred to me that the tsh user
community might be able to ffer their suggestions as well.
--gvc

Because the DC event is going to be operated by personnel without a lot
of technical background, or experience with tsh, I am recommending that
they set up their sessions in advance (except for the last session of
three) to minimize the pressure to get everything keyed in while the
event is in progress.

Unfortunately, I am not available to support the event.

I'll send the event files along later, after we're done with today's
training session.

The sessions go:

Fri PM: 4 games
Sat AM: 3 games
Sat PM: 4 games
Sun AM: 3 games

In config.tsh we have:

config max_rounds = 14
config initial_schedule = 3

To simplify initial setup, I wanted to provide 'canned' commands so the
initial pairings could be done rapidly as soon as attendance is
established.

I proposed:

sp 1 a
sp 2 a
sp 3 a
cp 0 a

(All of this is just going to be iterated over other divisions, of course.)

One concern I have right off is that the above method gives us
apparently inequitable pairings based on the "sum of opponents'
rankings", which, valid or not, I have seen used as a "measure of
goodness" by players.

The final 3 rounds will be 12-KotH-NoRepeat 13+14-KotH-AsTheyLie, and I
am anticipating that by then the operator will be enough up to speed on
data entry that she will be able to handle the data entry and printing
for the last two rounds on the spot.

My specific question is: given a scenario where we are going to have
three sessions which I want pairings based on results of the previous
session (or on initialization), what are the preferred config options
and pairing commands?

Thanks for your help. If you want to call me to discuss any of this you
can reach me at 703.282.3611.
--gvc