Swift Archive: Getting started
General
The Swift science data are organized in two main data sets: by observations, where an observation contains
data from all three instruments, and by TDRSS messages, which can contain data from both valid and false
triggers. These two data sets are stored in separate directories named /obs
(containing the observations) and /tdrss (containing the TDRSS messages). Data in each of the
two main directories are further subdivided into one month interval and, within each interval, by
observation id or sequence number. The month interval directories are named YYYY_NN, where YYYY is the year
and NN is the numeric value for the month.
The observation id or sequence number is an 11-digit number made up of the target id or trigger number
(first 8-digits) and the observation segment (last 3-digits).
The archive structure for the science data is therefore:
A Swift observation is defined as a collection of snapshots, where a snapshot is defined as the time interval spent continuously observing the same sky position. Because of observing constraints, the length of a snapshot can be shorter than a single orbit and it can be interrupted because the satellite points to a different direction in the sky or because the time allocated to that observation ends.
Archive access : Web, FTP and wget
At the HEASARC the Swift archive can be accessed using the web interfaces (see Special Swift archive page or Browse ) or via anonymous FTP.
- Access via Web : The archive access via the Web makes use of database tables to search for the science data. The currently available tables are :
- swiftmastr records high-level information for each Swift observation.
- swifttdrss records information contained in the TDRSS messages associated with each trigger.
- swiftbalog dedicated to the BAT instrument
- swiftbalog dedicated to the XRT instrument
- swiftbalog dedicated to the UVOT instrument
- Anonymous FTP : If the observation id and the time of the observation are already known, the data can be retrieved via anonymous FTP. For example, if the user wants to retrieve the sequence '00101993000' observed in January 2005, she/he can either download the files individually (see Example 1) or create and download a tar file containing the entire observation (see Example 2).
By following the TDRSS hyperlink under the related link column for the observation id '101065000', the user can check what is available in the swifttdrss database for that observation.
Example 1 mycom> ftp heasarc.gsfc.nasa.gov (username: anonymous, password: your_e-mail_address) %cd swift/data/obs/2005_01/00101993000 %binary %[prompt] %[m]get file_name[s] %quit Example 2 mycom> ftp heasarc.gsfc.nasa.gov (username: anonymous, password: your_e-mail_address) %cd swift/data/obs/2005_01/ % prompt % get 00101993000.tar.gz %quit
Example 1 mycom> wget -q -nH --cut-dirs=5 -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks http://heasarc.gsfc.nasa.gov/FTP/swift/data/obs/2004_12/00100585001/ Example 2 mycom> wget -q -nH --cut-dirs=5 -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks http://heasarc.gsfc.nasa.gov/FTP/swift/data/obs/2004_12/00100585001/xrt
If you have a question about Swift, please contact us via the Feedback form.