Changes between Version 2 and Version 3 of DVO_format
- Timestamp:
- Jul 13, 2010, 6:37:37 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DVO_format
v2 v3 33 33 34 34 == Top Level Files == 35 The top level of the DVO database has 3 data files; Images.dat, Photcodes.dat, and SkyTable.fits35 The top level of the DVO database has 3 data files; Images.dat, Photcodes.dat, and !SkyTable.fits 36 36 37 37 === Images.dat === … … 90 90 There are a number of bit masks for each photcode. During reduction, the IPP sets a number of quality flags, which get copied into the PHOT_FLAGS data field in the .cpm files. The photcode fields ASTROM_BAD_MASK, ASTROM_POOR_MASK, PHOTOM_BAD_MASK encode which of those bits indicate failures in an object's astrometry or photometry. See examples at the end for working with these values in IDL. 91 91 92 === SkyTable.fits ===93 As mentioned above, the objects in the DVO database get grouped into regions based on their position in the sky, and placed in one of the DVO subdirectories like n0000. The SkyTable.fits file gives the sky boundaries of each of these subdirectories, and can be used to locate which directory a particular region of interest is in:92 === !SkyTable.fits === 93 As mentioned above, the objects in the DVO database get grouped into regions based on their position in the sky, and placed in one of the DVO subdirectories like n0000. The !SkyTable.fits file gives the sky boundaries of each of these subdirectories, and can be used to locate which directory a particular region of interest is in: 94 94 95 95 {{{
