Index: /branches/eam_branches/ipp-20120405/Ohana/src/photdbc/doc/dvodist.txt
===================================================================
--- /branches/eam_branches/ipp-20120405/Ohana/src/photdbc/doc/dvodist.txt	(revision 33876)
+++ /branches/eam_branches/ipp-20120405/Ohana/src/photdbc/doc/dvodist.txt	(revision 33876)
@@ -0,0 +1,20 @@
+
+dvodist manages the parallel distribution of DVO databases.  The basic
+concept of the parallel DVO system is that the spatially distinct
+tables (the 'catalog files', ie, the cpt, cpm, cps, cpn tables) are
+distributed to a set of remote hosts.  Operations which interact with
+those tables fork remote jobs on those remote hosts, perform a local
+operation on the relevant tables, and return results to the main dvo
+programs.  
+
+dvodist is used to ship the tables out to the remote hosts, pull them
+back together to the central host, or make copies for backup.
+
+Currently, this program is implemented to use its own remote copy
+process, which is not very effective.  I would like to switch it to
+use rsync for the actual copies.  
+
+--
+
+new mode: dvodist -duplicate
+
Index: /branches/eam_branches/ipp-20120405/Ohana/src/relphot/doc/mosaic.txt
===================================================================
--- /branches/eam_branches/ipp-20120405/Ohana/src/relphot/doc/mosaic.txt	(revision 33876)
+++ /branches/eam_branches/ipp-20120405/Ohana/src/relphot/doc/mosaic.txt	(revision 33876)
@@ -0,0 +1,30 @@
+
+For 'mosaic' zero points, I define the mosaics by grouping the images
+by observation time.  I do this by generating a list of the image
+start times.  I sort this list and then find the unique entries.  Each
+time defines a new mosaic entry.  I then assign images to the mosaics
+by matching their start times.  
+
+The above currently happens on the image subset.  I need to identify
+the images which are NOT in the subset but for which a mosaic has been
+constructed -- these are partially accepted images.  I then need to be
+able to do something with those images and mosaics: either reject all
+partial mosaics or accept all images from partial mosaics.  The
+advantage of the latter is that the choice of accepted images depends
+on the catalog / regions loaded -- I need to accept images only if all
+overlapping region files are loaded, right?
+
+So, a few things are needed: 
+
+1) identify the images which are NOT selected by have matching start
+times.
+2) exclude them from the subset somehow.
+
+Some questions:
+
+ * the image subset is currently a *copy* of the Image array, not a
+   view.  does it help to change this? (beyond the memory savings?)
+
+ * I'm still a bit unclear on what 'load_images' vs 'reload_images'
+   does.  
+
