PGdata.tar.gz contains a directory with the light curves
presented in Figure 3, Table 3 and Table 4 of the paper:
"Reverberation Measurements for 17 Quasars and the Size-Mass-Luminosity Relations in Active Galactic Nuclei"
by Shai Kaspi, Paul S. Smith, Hagai Netzer, Dan Maoz, Buell T. Jannuzi, and Uriel Giveon, 2000, ApJ, 533, 631.
Preprint available at: http://arXiv.org/abs/astro-ph/9911476.
File names start with the PG object number followed by:
Light curves are given in three columns format:
The file PGspectra.tar.gz contains the
spectra for this project in which the above data were derived from. The
file contain 17 directories each named with "pgnnnn" where nnnn is the
PG number. Each of these directories has the spectra in FITS format
with name convention pgnnnnyymmdd.fits where nnnn is the pg number, yy
is the year, mm the month, and dd is the day in the month of the
observation. The data in the FITS files are in units of 1E-16
ergs/s/cm2/A (see figure 1 of the paper above).
Note that the only time tag that is right in the FITS files is the JD
of the observation. The UT date and times and the exposure times are
probably incorrect. This is because each spectrum is a combination
of two (or mode) spectra and so only the JD was updated to be the
average of all combined spectra.
The spectra are binned into 1 A per pixel and are padded from 3000 to
9000 A. Note that in most cases the usable part is from 4500 to 7800 A,
and the rebinning was done to ease the way the calculations were done.
Each of the directories also contain three more files:
lc_phot - that is the photometric light curve that was combined with the 5100 A light curve to produce the lightcurves used in the PG paper.
list_all - a list of all the spectra, but not in chronological order.
jd_all - a list of all JDs that correspond to list_all, again, not in chronological order.
The file PGaverage.tar.gz contains the average spectra in ASCII format (firat column wavelength second column flux in units of 1E-16 ergs/s/cm2/A) for this project as were presented in figure 1 of the paper above.
Comments/problems/questions should be e-mailed to: email@example.com