Changes between Version 16 and Version 17 of DVO_TopLevel

Timestamp:

Jun 13, 2012, 3:21:01 PM (14 years ago)

Author:

eugene

Comment:

--

DVO_TopLevel

@@ -12 +12 @@
 DVO uses the following database tables:
 
-[source:trunk/Ohana/src/libautocode/def/images.d Images.dat], [source:trunk/Ohana/src/libautocode/def/photcode.d Photcodes.dat], and [source:trunk/Ohana/src/libautocode/def/SkyRegion.d SkyTable.fits]
 
  * [source:trunk/Ohana/src/libautocode/def/SkyRegion.d Sky Layout] : defines the organization of the object / measurement tables on the sky
@@ -21 +20 @@
  * [source:trunk/Ohana/src/libautocode/def/measure.d Measure] : all detections of the astronomical objects
  * [source:trunk/Ohana/src/libautocode/def/missing.d Missing] : non-detections of known astronomical objects nominally touched by an image (note : this table is not populated by default)
+
+'''NOTE''': the links for each table listed above point to the autocode description of the maximal schema table, a particular instance of a DVO database may use a reduced schema without all fields defined.
 
 The standard implementation of DVO uses a stores the database information as a collection FITS tables.  For a subset of the tables (Average, SecFilt, Measure, Missing), the data is partitioned into multiple files representing different regions on the sky.  The partitioning scheme allows for a wide range of scale on which the sky is divided.  At one extreme, the entire sky is represented by a single file.  At the next level, this is split into Declination bands of width 7.5 degrees.  Next, these bands are split into RA ranges.  The next levels subdivide the RA / DEC ranges into smaller and smaller patches.  From the third level on down, the size of the sky regions varies with Galactic latitude to better sample regions of high and low stellar density.