
I am listing here a number of concerns about the existing ippToPsps code

1) the name ippToPsps is lame because both IPP and PSPS is in the
   wrong and mismatched cases.  Alternative?  ipp2psps? ipp-psps?

2) installation : there is none.  this must be fixed soon.  it is
   completely unreasonable to have to cd to a specific directory to
   run the software suite.

3) gpc1 database : how will this work with multiple camera?

4) czartool.  czartool code is completely irrelevant to ipp2psps and
   should be moved.
   

5) gpc1 database selections : shouldn't these be folded into the
   ippTools commands?  (or else changes will break this code)

6) sql for gpc1 seems to use select distinct in places where it is not
   correctly limiting the query (see, eg, getImageIDsForThisStackID)

* need to create ipptopsps database with manual commands:
* mysql> create database ipptopsps;
pikake: mysql -h localhost -u dvo -p ipptopsps < config/ippToPspsDbSchema.sql

* need to copy / install jython tarball somewhere

* if config.epoch is NULL, ipptopspsdb.jy:999 will raise an error

* need to manually create the scratch database, then call
  setupScratchdb.py to fill in some tables.

** why are init values stored in the scratch db and not the working
   db??

*** initialization of the scratch db is really slow (writing the
    skycell table?)

*** VOT load is super slow because of conversion from xml to mysql.

** config/IN/tables.vot is hard-wired in code and probably too static.

* some changes to dvoDetections.py, mirroring changes to the
  dvograbber code, break the sql

** test for other connections is quite severe (mysql.py:119) and
   prevents testing.

