Changes between Version 5 and Version 6 of Fossils

Timestamp:

Jun 13, 2008, 2:48:06 PM (16 years ago)

Author:

davea

Comment:

--

Fossils

@@ -1 @@
-Fossils
-
 = Hominids@home =
 
@@ -9 +7 @@
 
 A given rig session will yield
- * A number of cameras with ~1000 images.  Each image will have a timestamp.  File names may not be unique across cameras.
+ * A number of cameras with ~1000 images.  Image are hi-res (~2Kx3K pixels).  Each image has a timestamp.  File names may not be unique across cameras.
  * A GPS log file with a sequence of timestamped waypoints.
 
@@ -16 +14 @@
 Then you'll connect the various cameras, one at a time, to USB,
 and it will download their images.
-The outputs:
+This will produce a "batch" of images, consisting of:
 
- * A directory of all the images, with unique filenames.
- * An 'image index' file, one line per image.  For each image:
-  * time
-  * lat/long
-  * filename
-  * estimated size factor (meters/pixel)
-
-== Loading images on the server ==
+ * A directory of the images, with filenames that are unique within the batch.
+ * A 'batch description' file, JSON format. Includes
+  * Batch name (descriptive)
+  * And for each image:
+   * time
+   * lat/long of center of image (estimated from image timestamp and GPS log)
+   * filename
+   * x/y size, pixels
+   * estimated size factor (meters/pixel)
 
 We'll develop a script '''load_images''' that takes the above info
-and loads it into the Bossa database.
-Each run of this script produces a "batch" of jobs
+and does the following:
+ * Create a Bossa "batch" record
+ * Copy the images to a directory whose name is the batch ID
+ * Create medium-res (~1024x768) versions of images.
+ * Creates a Bossa job record for each image.
+Each run of this script produces a batch of jobs
 that can be managed as a unit (see below).
 Initially the state of the batch is "pending",