Browse
this table...

SWIFTUVLOG - Swift UVOT Instrument Log

HEASARC
Archive

Overview

The UVOT runs only one type of configuration filter/mode/window in a given time interval. This database table, therefore, contains for a given time interval a single record that describes one configuration.

Bulletin

The SWIFTUVLOG database table was last updated on 22 October 2014.

Provenance

This database table is generated by the Swift Data Center. During operation, it is updated on daily basis.

Parameters

Name
The designation of the pointed source.

Orig_Target_ID
This is a numerical value assigned automatically to each target and corresponds to the trigger number. The numerical value follows the convention adopted for Swift to assign the target identification. The numerical values can include up to 8 digits.

Target_ID
This is a unique numerical value assigned to each target and corresponds to the unique trigger number. To remove the degeneracy in the assignment of Target_ID for the safe pointing position and/or to correct any wrong assignment of the Target_ID, the unique (or the correct) number is re-assigned on ground and stored in the True_Target_ID parameter. In these cases Orig_Target_ID and Target_ID do not contain the same values otherwise they are identical. The numerical value follows the convention adopted for Swift to assign the target identification. The numerical values can include up to 8 digits.

RA
Right Ascension of the pointing position or position of the mask tag rate source.

Dec
Declination of the pointing position or position of the mask tag rate source.

Roll_Angle
Roll angle of the observation given in degrees.

Start_Time
Start time for this UVOT instrument configuration.

Stop_Time
Stop time for this UVOT instrument configuration.

Orig_Obs_Segment
The Swift observation strategy is similar to a monitoring campaign, where a target is observed several times. The observation segment, stored in this parameters, corresponds to the number of times a specific target has been observed. The numerical value follows the convention adopted for Swift to assign the observation segments and can include up to 3 digits.

Obs_Segment
This parameter contains the correct observation segment. The Swift observation strategy is similar to a monitoring campaign, where a target is observed several times. The observation segment, stored in this parameters, corresponds to the number of times a specific target has been observed. The numerical value follows the convention adopted for Swift to assign the observation segments and can include up to 3 digits. However the observation segment value can be wrongly assigned. This parameter contains the correct value reassigned on ground.

Orig_ObsID
This parameter contains a numeric value that should uniquely identify an observation. This value is the combination of the numerical value assigned to a target and the observation segment and is derived from the parameters Orig_Target_ID and Orig_Obs_Segment. Since the latter can be wrong or not unique the Orig_Obs_Number can also be wrong or not unique. The numerical value is a fixed 11-digit number, where the first 8 are for the target and last 3 are for the observation segment. Note that the Target_ID used in the observation number is the value associated to the current pointing position and not to the pre-assigned mask task rate listed in the Target_ID parameter in this table.

ObsID
This parameter contains a numeric value that uniquely identifies an observation. This value is the combination of the numerical value assigned to a target and the observation segment and is derived from the parameters Target_ID and Obs_Segment. The numerical value is a fixed 11-digit number, where the first 8 are for the target and last 3 are for the observation segment. Note that the Target_ID used in the observation number is the value associated to the current pointing position and not to the pre-assigned mask task rate listed in the Target_ID parameter in this table. The data directory is named after the ObsID.

Exposure
Total exposure time in seconds for the data included in the current record.

Counts
Total raw counts collected in this time interval.

Image_Loss
Records the total counts as reported by the instrument telemetry. The ratio between this value and the content of the parameter 'counts' give an estimate of the correction to apply to the data. This paramter is only valid when the instrument in working in Image mode and is set to null in all other cases.

Window_Size
Indicates the window size used during this time interval.

Binning
Indicates image binning applied on-board.

Filter
Records the filter value used during this time interval.

Operation_Mode
This parameter contains the operation mode running within the start and stop listed for the current record.

Pointing_Mode
This parameter contains the spacecraft observing mode. Possible values are "pointing" or "settling".

Filename
Name or root for the file containing the data for this interval.

Extname
Name of the extension in the FITS file containing the data for this time interval.

Asp_Corr
This parameter contains a flag which indicates whether or not the additional aspect correction has been applied to the UVOT processed data.

Submode
This parameter contains the array of bits which indicate whether various UVOT sub-mode activities were performed. The given activity should have been performed if the indicated bit is set. The following is a list of the possible bit values and their meanings:

       0x01 - Generate Finding Chart following exposure
       0x02 - Save ACS messages during exposure
       0x10 - Perform tracking
       0x20 - Generate Tracking Frame Switch data product
  

LED_Bias
This parameter records the setting for the LED.

LII
The Galactic Longitude of the pointing position. Note that the pointing position can be different from the GRB (or other target) position.

BII
The Galactic Latitude of the pointing position. Note that the pointing position can be different from the GRB (or other target) position.


Contact Person

Questions regarding the SWIFTUVLOG database table can be addressed to the HEASARC User Hotline.

Page Author: Browse Software Development Team
Last Modified: 12-Sep-2008