... Here is an example of the output header of CATS data. ... SIMPLE=T / BITPIX=8 / character information NAXIS=0 / no image data array present EXTEND=T / may be standard extensions OBJECT= CATS SEARCH / CATS search result ORIGIN=SAO RAS DATE=01/01/1997 / date of file creation END XTENSION=TABLE / F-file table extension BITPIX=8 / 8-bits ... NAXIS1=93 / No. of characters per row NAXIS2=1000 / the number of lines (sources) TFIELDS=10 / there are 16 fields per row EXTNAME= CATS / object name: ...

CATS home ] [ Back to CATS list ] FITS format in CATS . ... SIMPLE=T / BITPIX=8 / character information NAXIS=0 / no image data array present EXTEND=T / there may be standard extensions OBJECT= CATS SEARCH / CATS search result ORIGIN=SAO RAS DATE=char / date of file creation END XTENSION=TABLE / F-file table for spectrum data BITPIX=8 / 8 ... 2-D matrix NAXIS1=93 / No. of characters per row NAXIS2=1000 / number of lines TFIELDS=15 / there are 15 fields per row EXTNAME= CATS / object name: ...

... Input via keyin format is of the form keyword = value . ... The input keywords are not case sensitive. Most of the values required by SCHED, except for file names in case sensitive systems like unix, are also not case sensitive. keywords are, in all cases, limited to 8 characters in length. ... Keyin values can be mathematical statements in parenthesis; for example, dur = 15 rep = (4*5) This example shows the most likely way in which this capability might be used in SCHED input files. ...

... This is done by taking in all input files the extension whose name is specified by the maintable parameter (called 'merged extension' in what follows) and merging the columns into a single output extension of the same name. ... Its contents is taken from the CCDID keyword (and QUADRANT for EPIC PN). ... To propagate other column specific keywords, they must be specified manually via the extensionchecks , mainattributes , maxattributes and minattributes parameters (see above). ...

... In the above example, the second region uses the global coordinate system (PHYSICAL by default). ... Supported systems include: name description ---- ----------- PHYSICAL pixel coords of original file using LTM/LTV IMAGE pixel coords of current file FK4, B1950 sky coordinate systems FK5, J2000 sky coordinate systems GALACTIC sky coordinate systems ECLIPTIC sky coordinate systems ICRS currently same as J2000 LINEAR linear wcs as defined in file In addition, two mosaic coordinate ...

... There are five standard data formats for HSP data. ... The datasets contain a standard header packet , a unique data log , and one to four science data files (and corresponding data quality files). ... HSP Data Files . ... Science data, digital sky .d2h/.d2d . ... Each of the science data files has a corresponding quality file that contains single-precision floating point values. ... The HSP calibration program, calhsp , generates the calibrated file for each corresponding raw science data file. ...

... The catalog contains SAO number; the right ascension and declination with a B1950.0 equinox and epoch; annual proper motion and its standard deviation, photographic and visual magnitudes; spectral type; references to sources; the Durchmusterung (DM) identifier if the star is listed in the Bonner DM (BD), Cordoba DM (CD), or Cape Photographic DM (CP); component identification; The Henry Draper (Extension) (HD or HDE) number; and J2000 positions and proper motions. ...

I/199 Lick Northern Proper Motion Program: NPM1 Catalog (Klemola+ 1987) =============================================================================== = Lick Northern Proper Motion Program: NPM1 Catalog Klemola A.R., Hanson R.B., Jones B.F. <Astron. ... Positions are given for equinox B1950 and computed epoch 1950. ... Other data given for each star are: the original mean epoch, a stellar class code, the number of NPM fields measured, and discrepancy flags for position, proper motion, and photometry. ...