There are going to be 256 co-keypad TASCs (I expect teams to
solve 100-160 of them), and 640 chronomentometer puzzles
(I expect the teams to solve 300-400 of them).

Here's my thoughts on logistics.

We have on-hand:
ACT1:
  * 400 blank co-keypad submission sheets (in B&W)
  * all 256 co-keypad TASCs printed (in color)
  * 32 GROSS User's Manuals (2 per team)
  * Login/passcode sheets; contain the URL (text and QR-code format, for ease
    of smartphone access), and hand-written team name and 6-letter passcodes.
  * When a team arrives, we hand them 2 User's Manuals, 5 blank co-keypad
    submission sheets, and their login/passcode sheet.  They also get two TASCs
    that were automatically assigned to them.
ACT2:
  * 100 blank *reusable* chronomentometer sheets
  * 32 GROSS User's Manuals (2 per team)
  * Login/passcode sheets; contain the URL (text and QR-code format, for ease
    of smartphone access), and hand-written team name and 6-letter passcodes.
  * When a team arrives, we hand them 2 User's Manuals, 5 blank chronomentometer
    submission sheets, and their login/passcode sheet.

Requesting a TASC:
ACT1: 
  When a team requests a TASC, it takes them to a page that tells them to
  come to the GC's desk to pick up the specs.  The system also notifies
  the GC staffer that the team is coming so they can find the sheet (out of 256).
  GC staffer gives them the sheet and assigns the TASC in the system.
ACT2:
  The system automatically assigns teams TASCs when they request one
  (subject to the QUIT and other limits).

Abandoning a TASC:
ACT1:
  When a team abandons a TASC, it takes them to a page that tells them to
  RETURN the TASC sheet to the GC's desk.  The system also notifies
  the GC staffer that the team is coming so they can put the sheet back.
ACT2:
  The system automatically abandons TASCs for teams on request.

Viewing/Fixing an assigned TASC:
ACT1:
  When a team views a TASC, they see an on-line duplicate of what is already
  on their TASC sheet (a backup in case the sheet gets lost).  They fix the TASC
  by submitting a filled-in sheet to GC.  They don't have to return the TASC.
  GC checks the sheet against a master solution key, and if it is correct, the
  TASC is marked fixed; otherwise, GC logs that the team was incorrect and
  notifies the team.
ACT2:
  The system shows the TASC to the team on-line.  They also submit
  their solutions online and the system automatically credits them.

Other logistics:
ACT1:
  Teams will run out of blank co-keypad sheets as they are used up for submission.
  We'll have a bin where teams can grab extras.

Undecided issues:
* In Act 1, how does GC notify the team that their solution was incorrect?  Some
 ideas:
  ** E-mail (needs GC effort)
  ** In-system notification (needs more programming :( )
  ** Go find the team and talk to them (needs time/volunteers)
  ** Throw it in the logs on the big display dashboard

Other notes:
  There are five "fake teams" -- the "Lab" and one team from each faction.  The "fake
teams" solve TASCs periodically -- namely, the system makes suggestions and the
human GC member approves them.  The goal is to keep the five total SCOREs close.
Yes, it's not fair.  Neither is Mario Kart.  Needed: handwavy technobabble to
explain how it is possible for, say, Journalists to be fixing TASCs when there clearly
aren't any Journalist teams there.  Something about the components synchronizing
with alternative timelines.

===================

RESETTING TRENCHWOOD

USE trenchwood;

    Clean out the solved puzzle table
        Log in to mysql on wei-Hwa's server (username: laboratory, password: forscience), then run: 

TRUNCATE TABLE solves;
TRUNCATE TABLE requests;
TRUNCATE TABLE released;
TRUNCATE TABLE assignments;

    Clean out the log 

rm /home/www/doctorwhen/trenchwood.com/public_html/keypad/log/*

    If you need to regenerate the team information:
        Make sure /home/whuang/public_html/nodir/doctorwhen/gross/teams.csv is correct
        run this SQL: 

TRUNCATE TABLE solvers;
LOAD DATA INFILE '/home/whuang/public_html/nodir/doctorwhen/gross/teams.csv'
 INTO TABLE solvers
 FIELDS TERMINATED BY ','
 OPTIONALLY ENCLOSED BY '"'
 LINES TERMINATED BY '\n'
  IGNORE 1 LINES (solver_id, name, role_id, passcode, present, fake);

    If you need to regenerate the puzzle information (god I hope not), this will recreate the release_info and scores tables: 

 mysql -Dpeachfrontier -u laboratory --password=forscience < /home/whuang/prog/keypad/puzinfo.sql

====================


RESETTING PEACH

[or, in one shot]
mysql -u laboratory --password=forscience < reseteverything.sql


USE peachfrontier;

    Clean out the solved puzzle table
        Log in to mysql on wei-Hwa's server (username: laboratory, password: forscience), then run: 

TRUNCATE TABLE solves;
TRUNCATE TABLE requests;
TRUNCATE TABLE released;
TRUNCATE TABLE assignments;

    Clean out the log 

rm /home/www/doctorwhen/peachfrontier.com/public_html/cmm/log/*

    If you need to regenerate the team information (and remove teams presence):
        Make sure /home/whuang/public_html/nodir/doctorwhen/gross/teams.csv is correct
        run this SQL: 

TRUNCATE TABLE solvers;
LOAD DATA INFILE '/home/whuang/public_html/nodir/doctorwhen/gross/teams.csv'
 INTO TABLE solvers
 FIELDS TERMINATED BY ','
 OPTIONALLY ENCLOSED BY '"'
 LINES TERMINATED BY '\n'
  IGNORE 1 LINES (solver_id, name, role_id, passcode, present, fake);

    If you need to regenerate the puzzle information (god I hope not), this will recreate the release_info and scores tables: 

(in directory /home/www/doctorwhen/peachfrontier.com/public_html/cmm)
mysql -Dpeachfrontier -u laboratory --password=forscience < puzinfo.sql
(sql file was generated by /home/whuang/public_html/cmm/select-puzzles.pl)