Index: /trunk/doc/design/.cvsignore
===================================================================
--- /trunk/doc/design/.cvsignore	(revision 2230)
+++ /trunk/doc/design/.cvsignore	(revision 2231)
@@ -1,4 +1,3 @@
-*.log *.dvi *.aux *.toc *.log *.out *.lof
-ippSCD.pdf
+*.log *.dvi *.aux *.toc *.log *.out *.lof *.tbr *.tbd *.ent
 ippSRS.pdf
 ippSDRS.pdf
@@ -8,2 +7,6 @@
 .mana
 .status
+.dvo
+sim
+ippSRSout.tex ippSRStrace.tex
+pdfs
Index: unk/doc/design/notes.txt
===================================================================
--- /trunk/doc/design/notes.txt	(revision 2230)
+++ 	(revision )
@@ -1,70 +1,0 @@
-
-- Add PS-1 discussion in Subsystem Overview: 
-
-  In the case of the IPP, PS-1 differs from the complete PS-4 system
-  in several important ways.  First, with only one telescope and
-  camera, the data throughput rate is substantially reduce to a
-  maximum of 1 64-OTA image per 40 seconds rather than 4.  In
-  addition, much of the PS-1 mission will be devoted to calibration
-  and testing which will imply a different level of processing.  For a
-  significant fraction of PS-1, data will be obtained for the AP
-  Survey covering the entire $3\pi$ steradians of the sky accessible
-  to PS-4.  These images will not be analysed initially to the
-  complete analysis level of having multiple images combined.  Rather,
-  it will be calibrated to the extent possible for a single focal
-  plane array.  Only after the AP Survey is done, the analysis process
-  has been validated, and the complete AP Survey reference catalog has
-  been generated will it be possible to generate the first epoch
-  static sky image, rougly 18 months into the PS-1 mission.
-
-- fix order in 3.2 (MD before AP DB)
-- Add PS-1 discussion to hardware: only 64 OTAs per image
-
-- AD DB Operations:
-  - Addstar:
-
-    This operation takes the metadata and object data for an image
-    (complete FPA or individual OTA?) and inserts the data into the AP
-    Database.  This operation is performed by a client in interaction
-    with the AP Database Servers.  The steps performed are as follows:
-
-    Client-side data distribution
-    - load relevant Region table rows
-    - divide object list into appropriate regions
-    - identify appropriate image table
-    - send object data to appropriate servers
-    - send image data to appropriate server
-
-    Server side interactions
-    - accept detections for specific object table 
-    - load corresponding objects
-    - load corresponding detections 
-    - spatially match detections to objects
-    - add matched detections to detection table (with object IDs)
-    - update object average parameters
-
-  - Delstar
-
-  - Relphot
-
-
-- Scheduler
-
-  Get new images
-  every 15 seconds
-
-    check for newest current image in metadata db
-    request images newer than T
-
-
-      status
-      /path/image.fits
-      /path/metadata.fits
-
-    add entry to metadata DB
-    save metadata to MD DB
-    copy image to image server
-    set metadata entry to downloaded
-
-      
-