Mid-Infrared
Sky Background and Absolute Photometric Calibration of the Spitzer Space Telescope Infrared Array Camera
B. Bhattacharya1, W. Glaccum1,
P.J. Lowrance1, W.P. Lee1, W.T. Reach1, J.
Surace1, S. Carey1, M. Lacy1, B. Nelson1,
G. G. Fazio2 and othersÉ
1Spitzer Science Center, Infrared Processing and Analysis
Center, MS 220-6, California Institute of Technology, Pasadena, CA 91125
2Harvard-Smithsonian Center for
Astrophysics, 60 Garden Street, Cambridge, MA 02138
;
Abstract
Since
its launch in late 2003, the Spitzer
Space Telescope Infrared Array Camera (IRAC) has routinely measured
mid-infrared sky brightness from 3.6 - 8.0 mm as part of the nominal operations calibration program. We present a summary of these
observations, including background measurements at the north ecliptic pole as
well as in the ecliptic plane.
Temporal and spatial variations are noted and compared with a
pre-launch, DIRBE-based background model.
We find that offsets between observations and predicted sky brightness
can be attributed both to instrument bias as well as inaccuracies in the
zodiacal background model. The
data are used to derive band-specific scale and offset factors that can be used
to convert measured photometric values to an absolute scale.
1. Introduction
The
mid-infrared background provides a measure of thermal emission within and
outside of the solar system. At
IRAC wavelengths, 3.6, 4.5, 5.8, and 8.0 mm,
(Fazio, et al., 2004), the primary contributor to background emission is
interplanetary dust ???emanating from comets (wtr, if so, need ref) as well
as ?? from asteroid collisions. In addition to targeted studies of this
dust (e.g., Grogan, 2005), calibration observations can be mined to determine
overall morphology and temporal variation of this background emission.
An
empirical zodiacal (zody) background model (Kelsall, 1998), based on
observations by the Diffuse Infrared Background Experiment (DIRBE) on the
Cosmic Background Explorer (COBE) spacecraft (Bennett, et al. 1993; Boggess, et
al., 1992), has been used as the basis for modeling sky background in Spitzer data.
The Spitzer model (Reach,
2000; Bhattacharya and Reach, 2004) is routinely used in the data reduction
pipeline to predict sky background at a given location; the astronomical
community also makes uses of this model through the Spitzer Observer Planning
Tool (SPOT).
In
this study, we consider observations at various ecliptic latitudes in
comparison to the zody model; offsets between observed and predicted sky
background are used to determine revised photometric calibration factors. Reach, et al, 2005, provided an
assessment of in-flight calibration accuracy using 3.6 – 8.0 mm measurements of standard calibration
stars. We supplement their results
by examining additional IRAC calibration datasets, including sky background and
flat field observations taken as part of the Spitzer nominal operation calibration plan from December
2003 through February 2006. In
Section 2, the calibration observations and data analysis techniques are
described. Section 3 discusses the Spitzer zody model. In Section 4,
observed temporal and spatial variations in the 8mm sky background are discussed in the context of the zody
model. The difference between
observed and modeled sky background is used as the basis for conversion of IRAC
photometric measurements to an absolute scale, as presented in Section 5. Finally, in Section 6 these conversion
factors are applied to a representative IRAC dataset from the Spitzer Legacy GOODS program.
2. Observations and Data Analysis
In
order to characterize the sky background level and pixel-to-pixel variability
of the four IRAC detectors, deep observations near the North Ecliptic Pole
(NEP), as well as in the ecliptic plane, are taken systematically as part of the
nominal operations calibration program.
The current cadence of these measurements places them at the beginning
and end of each instrument campaign, leading to a pair of observations taken a
week to 10 days apart each time IRAC is turned on. During the first year and a half of operations, sky darks
and flats were taken more frequently, every two to three days per
campaign. To mitigate thermal
load, the observatory is sequentially dedicated to operate of one of its three
instruments, cycling through IRAC, the Multiband Imaging Photometer for Spitzer (MIPS) (Rieke, et al., 2004) (Houck, et al., 2004)
and then the Infrared Spectrograph (IRS) (Houck, et al., 2004).
Spitzer nominal operations (NomOps) started approximately 90
days after launch its launch on August 25, 2003. The first 90 days (In-Orbit
Checkout or IOC) were spent characterizing the space-based performance of
detectors and observatory, and data from IOC are not included in this
study. The IRAC detectors have
demonstrated a high level of stability throughout NomOps, as shown in the
long-term datasets presented below.
All calibration data publicly available through the Spitzer archive tool, Leopard (http://ssc.spitzer.caltech.edu). Data are taken at all frametimes for
the sky background and dark monitor programs, and taken with 100 second
frametimes only for the flat field and zodiacal background monitoring programs,
all of which are described below. Ensemble
images of 256 x 256 pixels, with a scale factor of 1.22Ó/pixel, are used for
the sky background and flat field analysis, and individual, pipeline processed
frames of the same size and resolution are used here in the dark and zody
monitoring data. These four sets
of calibration data, over 30,000 ???Wen, what is total number of dceÕs??? frames in all, provides a valuable, fiducial
reference set for determining variations in the mid-IR background and
determining instrument characteristics.
2.1.
Sky Background
Background
removal is performed in the standard Spitzer pipeline for IRAC data to subtract thermal emission
from foreground sources such as interplanetary dust as well as to subtract
instrumental dark current.
Background observations are made in a region of the NEP that is relatively
free of mid-IR sources. To obtain
a more accurate measure of the sky background, instrumental bias is removed
using pre-launch, laboratory-based dark frame measurements.
The
standard sequence for obtaining background observations is to observe nine
positions in a 3x3 grid surrounding the observing location with 100 pixel step
sizes, as illustrated in Figure 1.
Table 1 summarizes the NEP observations available at the time of this
paper, including data from December 2003 through 2005 November at the coordinates
(l,b)
~ (125o,87o) J2000 ecliptic or (a, d) ~ (265o,+69o)
J2000 equatorial. Small positional
offsets are required from time to time to avoid bright sources because of the
relative rotation of the Pole as Spitzer
travels around the Sun. For mid-IR
background determination, we use the the 100s high dynamic range skydark data,
in which observations at 0.6 s and 12s are taken prior to the 100s frame. The first two frames are not included
as they are susceptible to the so-called First Frame Effect (FFE), a bias level
variation that is dependent on the time elapsed since the previous
readout. Figure 2a provides the averaged
(not medianed, as per wplee, 4/06)
value for observations at 3.6, 4.5, 5.8, and 8.0 mm of the NEP as part of the Spitzer sky dark calibration
program on days 98-800 of the mission, 2003-Dec-02 through 2005-Nov-02. The average value in DN for each AOR
(Astronomical Observation Request), pipeline calibrated to correct for
instrument bias and the FFE, is plotted here against heliocentric ecliptic
longitude of the spacecraft. The
top set of curves in each panel shows measured sky brightness, and the bottom
set provides a measure of the offset from our zodiacal background (zody) model,
which is described in detail in Section 4. The periodic variability in sky brightness as the spacecraft
samples different lines of sight while traveling around the Sun is clearly
apparent. To examine the role of
frametime on measured background, in Figure 2b, we also present 30-second HDR
sky dark observations at 3.6 and 8.0 mm. These shorter exposure datasets were
taken concurrently and at the same location as the 100sHDR darks listed in
Table 1.
change daynum and dates
with W-PL delivery of more sodb results, BB, 4/20
2.2. Sky
Flats
Need to verify inclusion
of skydark in header keyword FLATNORM Verify inclusion of
skydark in header keyword FLATNORM for both flats and skydarks
Flat
field calibration is performed to remove pixel-to-pixel variations in detector
response. A 256x256 array of
wavelength-dependent scale factors is applied to IRAC data to account for
individual pixel response. Because
the IRAC shutter is set to the open position for the duration of the mission,
flat field calibration files are derived from a deep set of observations taken
near the Ecliptic Plane, which is a region of high zodiacal background, at
locations that are relatively free of stars. A mean solar elongation of 100o is observed in each campaign within a
few degrees of the Plane. As shown
in table 2, the coordinates observed vary as a function of spacecraft
position. SpitzerÕs earth-trailing
orbit around the sun lags the earth by approximately 6o/year. The sequence of observations for flat
data acquisition include the default 0.6 and 12s frames taken to ameliorate the
FFE and 126 additional frames
obtained using a 14-point dither of a 3x3 map, with 120 pixel step sizes and
100s frametime, as shown in Figure 1b.
Since flat field data are obtained at solar elongation of 100o,
the observed
position varies over the course of a year, as shown in Table
2. Figure 4 shows observations at
3.6, 4.5, 5.8, and 8.0 mm in the Plane
as part of the Spitzer sky flat calibration program on days 98-903 of the
mission, 2003-Dec-01 through 2006-Feb-13. As in Figures 2 and 3, median value in DN for the data, as
well as zody model, is plotted against heliocentric ecliptic longitude of the
spacecraft. The skyflat ensemble
plotted here, have been pipeline calibrated to correct for instrument bias and
the FFE.
The pipeline also
subtracts the median value for nearest-in-time 100s skydark observation, but in
Figure 4, this value has been added back in, to provide a more accurate measure
of the sky background at the viewing position.
2.3.
Dark Monitoring
Within
an IRAC campaign, it is important to separate instrumental bias variations from
actual changes in the mi-IR background.
Sky background observations provide calibration datasets for background
removal in the data pipeline, but they are not taken with sufficient frequency
to provide data on bias variation.
During the first ten IRAC campaigns, through July 2004, a calibration
program was implemented to observe the NEP every 12 hours; typically these observations
were executed 14-18 times per campaign. The dark monitor program was
implemented to detect variations in dark current for all frametimes. ???IER
description & obs strategy here???
We present an analysis of the longer
100s observations are considered in the present work. These 100s dark monitor observations, which complement the
sky dark calibration program, observed the NEP position 162 times over the
course of 8 months, as outlined in Table 3.
If
instrumental bias remains constant over an IRAC campaign, observations should
reveal out only the changes in zodiacal background itself. Figure 4 illustrates
the variation in zody over the first 6 campaigns for all four IRAC bands. These observations are consisted with
the skydark data presented in Figure 2a. In addition, the color of the sky measurements should
remain constant over time. Figure 8b indicates the 3.6/8.0, 4.5/8.0, and
5.8/8.0 mm colors are consistent over
time in the dark monitor program.
This is discussed in further detail in Section 4.1, with an examination
of the zody color at both the NEP and in the Ecliptic Plane data, illustrated
in Figures 8 and 9. From these
data, bias levels have been determined to be constant throughout a campaign.
2.4.
Routine Background Monitoring
Initial
analysis of the dark monitoring calibration program, described in Section 2.3,
indicated the presence of temporal variations that were not predicted by the
zody model (Bhattacharya and Reach, 2004). In order to further verify that these variations were due to
secular drift in instrumental bias or a real deviation from the model, the dark
monitoring program was replaced by a routine background monitoring test that
took background measurements at various locations in the sky. Positions observed in addition to the
NEP included the South Ecliptic Pole (SEP) and latitudes of b =
+15o both earthward and anti-earthward, relative to the
spacecraft at solar elongations of 95o (verify). This test was implemented in campaigns
12-17 in August-December 2004.
Table 4 summarizes the viewing geometry and observing times.
2.5. Pipeline and off-pipeline analysis
The
datasets used in this study include sky background and sky flat observations
taken each campaign for use in calibrating concurrent science data as well as
observations designed to monitor long-term variability in the background level. Spitzer IRAC data are processed through
a datatype-specific software pipeline that calibrates observations for
instrumental response and variability as well as observational effects, as
discussed by Lowrance, et al., (2006, in preparation). A detailed description
of the reduction procedures used to convert from data from raw counts to
physical units (MJy/sr) is also available through the Spitzer website. The science products pipeline removes
electronic bias, corrects for wraparound, non-linear detector response and the
FFE. It also uses NEP sky
background levels from the relevant campaign for background subtraction,
applies a flat field scale factor to account for pixel-to-pixel variability,
and conversion from DN to physical units based on the latest calibration
factors (Reach et al., 2005), and finally performs pointing refinement. This level of processing results in a
set of basic calibrated data (BCD), with one .fits file generated per
spacecraft pointing and exposure time.
These files are of size 256 x 256 pixels (one IRAC field of view) with
data in units of MJy/sr. An AOR is
provided as a series of BCDÕs, usually at varying dither positions, that are
mosaiced together in the post-BCD pipeline (Lowrance, et al., 2006).
How large a border (2
pixels) around each flat field bcd is omitted when computing the
median? Is a border ignored
for the skydark medians, too?
Is this to avoid gradients induced by telescope optics/ scattered
light?
Two
of the datasets presented in this study, the dark and routine background
monitoring programs, do not provide routine calibration files for use in the
pipeline. These are available as
BCDÕs, and for these observations we have added back in the sky background
value (header keyword SDRKEPID provides the relevant skydark ensemble product
ID number), and returned to data number values by multiplying by the exposure
time and dividing by the absolute calibration factors presented by Reach, et
al., 2005. In addition, for
channels 3 and 4, an extended source photometric scale factor (dividing by 0.63
and 0.69, respectively) has been applied.
Flatfield ÒuncorrectingÓ is unnecessary as pixel-to-pixel variations are
not significant when working with aor medians.
Routine
calibration products are processed into a final ÒensembleÓ of size 2562
pixels, are available for the skydark and flat field observations. The skydark ensembles are already
provided in DN. Skyflat ensembles
are normalized to the median value in DN.
This value is listed in the header keyword FLATNORM and is applied as a
multiplicative scale factor to obtain measurements in data number.
3. The Spitzer
Zodiacal Background Model
The
mid-IR sky background is a superposition of thermal emission from the cosmic
infrared background (CIB), the interstellar medium (ISM), and the
interplanetary dust (IPD) (Kelsall, 1998). At temperatures of ~3K (Bennett, et al., 1993), the CIB
typically emits most strongly wavelengths near 100 mm. This background,
a remnant of the Big Bang and a signature of the early universe, contributes
negligibly to background in the IRAC wavebands. The interstellar medium is
warmer, at temperatures of ???, and most easily detected in the 12-25 mm range (Bennett, et al. 1993). A local contributor to the mid-IR
background, the zody emits at temperatures near 300K and dominates the IRAC
background at 3.6 – 8.0 mm.
The
zodiacal background is comprised of three major components, each of which
clearly exhibits large-scale structure.
As verified by DIRBE (Kelsall, et al., 1998) the zody is a superposition
of a smooth cloud, a circumsolar dust ring at ~1 AU, and dust bands associated
with certain asteroid families.
Resonant leading and trailing dust clumps have been identified in the
circumsolar dust ring by Dermott, et al., 1994, using the Infrared Astronomical
Satellite (IRAS) and recently by Grogan, et al, 2005, using Spitzer data.
Structures within the smooth cloud and asteroidal dust bands have also
been identified using the DIRBE experiment (Jayaraman, et al., 1999).
The
Spitzer model builds upon Kelsall, et
al., 1998 by modifying several parameters (specify) and introducing a
non-geocentric line of sight.
Using the spacecraftÕs position on a given day as defined by the
ephemeris file, offsets from the Earth are computed to define the current
location of the observatory as the point of origination for viewing a specified
location on the sky. Contributions
to infrared emissiosn along the line of sight, which is extended to 5AU from
the Sun, are computed from modeled spatial distributions of the dust components
contributing to the zodiacal background.
Thermal contribution from the ISM, which is significantly lower at IRAC
wavebands, is calculated using SchlagelÕs dust maps (need ref, further
details). The 3.6 - 8.0 mm signature of the CIB, though poorly
defined at this time, is expected to be below that of the ISM (need ref---wtr,
K-band recent results??).
Consequently, thermal emission from this component is not included in
our model. The CIB is an isotropic
background source, superimposed on the IPD and ISM contributions to the zody,
whose effects can be removed by subtracting the NEP sky from that at the
ecliptic plane, as shown in Figure 11 and discussed further in Section
4.2.
For
the observations presented in Figures 2, 3, 4, and 5, we have computed the
zodiacal background model, as seen in Figures 6a, 6c, and 7a (also need
darkmon, zodymon model bkds). The
biannual spike in the ISM in Figure 7a is due to the spacecraft crossing the
galactic plane. The Spitzer zody model can be accessed through the SPOT
interface, available at http://ssc.spitzer.caltech.edu.
4. Variations in the zodiacal background
4.1
Skydarks and dark monitor
In
order to determine whether variation from the zodiacal background model is
affected by exposure time, we present additional skydark observations taken
with a 30s frametime at the NEP in Figure 2b. Dark monitor observations, as described in Section 2.3, have
been taken to check for change within an individual campaign of background
levels; these files are not used by the IRAC pipeline for data calibration. The
analysis performed on dark monitor data for the results presented here has
involved restoring data to DN values, removing the flat field correction, and
adding back in the sky background. These data are similar in nature to the sky
background measurements but taken with greater frequency. The sky dark should provide a combined measurement of
instrumental noise and offsets as well as the background sky.
Discuss
residuals. Discuss extended source photometric correction (0.63, 0.69) in
channels 3, 4. Discuss
color correctionÉ.
4.2 CIB
Discuss
4.2 Flat Field
As
these data are taken near the ecliptic plane, their trending over time is an
indication of change of sky background value near the ecliptic. Figure 3 shows variability in the flat
field over the first 903 days of the nominal mission, through 2006-Feb-13. Discuss residuals
The
routine background monitoring program, as described in Section 2.4, was
designed as a followup to the dark monitoring program discussed above. These data have been processed through
the science pipeline to generate BCDÕs as with the dark monitoring datasets and
are also not used by the IRAC pipeline for data calibration. Processing of BCDÕs from this program
has involved the same steps used for handling the dark monitoring data. From days ___ through ___ of the
mission, the background was observed at twelve (verify) different
locations. The positions observed
in this program are listed in Table 1d, and the time variability in the sky
background at these positions is plotted in Figure 5. Discuss residuals.
4.4.
Instrument bias removal
If labdark removes bias, zody color vs. time should be constant
provide each bandÕs labdark value, explain how derived, include text to support:
Fig. 6: ground-based lab darks
Fig. 7: zody color vs. time
zody color varies some (quantify)—attribute to Òspace darkÓ needed (using labdark now) and to differences in IPD from predicted
IRACÕs
bias level may be affected by stochastic temperature fluctuations due to
4.4.
Instrument bias levels and temperature
IRACÕs
bias level may be affected by stochastic temperature fluctuations due to ___
(CFT, WTA-why do temps change?), time since last readout, as well as by
anneals. The effects annealing on dark current have become an important issue
in NomOps because of the presence of latent images left by bright sources. Since campaign 3 in early 2004, all
four detectors have been systematically annealed at the beginning of each
campaign, and channels 1 and 4 are also annealed after each downlink.
In
this section, we consider the roles of variations in IRAC cold footpad assembly
and the warm temperature electronics on the dark monitor data, which were taken
frequently in early NomOps; considered time since previous readout, and time
since last anneal on bias level.
4.4.a.
Thermal fluctuations
Thermal
fluctuations in the detector or telescope assembly can potentially introduce
changes in dark current. In order
to examine the effects of temperature effects, we have plotted warm temperature
assembly and the cold footpad temperature (details-describe where these are and
why these are best places to examine -- Glaccum) and fluctuations over several
campaigns to look for correlations with dark monitor measurements at the
NEP. As shown in Figure 12a,
temperature fluctuations after IRAC turns on and stabilizes are small, on the
order of one degree for the warm temperature assembly and a few hundredths of a
degree for the cold footpad. The
top panel in Figure 12a shows that variations in measured background are
unaffected by these small excursions in temperature, even in the 3.6 mm detector where zody signal is lowest and
thermal noise should consequently play a more significant role.
4.4.b.
Time since last readout
IsnÕt
this just the FFE?
4.4.c.
Time since last anneal
Campaign
8 time change w/ anneal
5) Deriving absolute
photometric measurements using IRAC
If labdark removes bias, zody color vs. time should be constant
5.1) correction_factor =
darkmon_dn_with_ffcorr – zody_model
First frame correct the raw dn and subtract the zody model from this. The residual is a measure of the actual difference of observed zody from model as well as a measure of the change in bias from that predicted by ffcorr.
Absolute photometric value = (your bcd) – correction_factor
(in MJy/sr)
5.2.1) Look at change in correction factor vs. time—should be roughly constant
Fig. 8: correction factor vs. time, NEP; show each band
Fig. 9: correction factor vs. time, ecliptic plane; show
each band
Table 5: band, correction factor, to use for abs photometry
6) Application: Analysis of sky bkd variations in pipeline processed
COSMOS/GOODS data
6.1) Look at variation of skydark mosaics over time
<skydarks mosaics> have skybkd subtracted; therefore bkd in mosaics should be close to zero
Fig 10: <skydark mosaics>
vs. time
Consider COSMOS/GOODS bkd plots, where variation is substantial (plot from HaoJing)
Fig 11: <COSMOS/GOODS skydark
mosaics> vs. time
6.2) How does applying correction factor affect this variation?
Wtr usually quotes nominal values of a factor of two over two months in ecliptic and a factor of 10-20% over a year at the pole
7) Conclusions
8. References
Bennett, C.L., et al., Scientific results from COBE, Adv. Sp. Res., vol.13, no. 12, 409-423, 1993.
Bhattacharya, B., and Reach, W.T., Zodiacal Background: Spitzer Observations vs. DIRBE-Based Model, BAAS 205, #56.06.
Boggess, N., et al., The COBE Mission – Its Design and Performance Two Years after Launch, ApJ, 397, 420-429, 1992.
Dermott, S.F., et al., A Circumsolar Ring of Astgeroidal Dust in Resonant Lock with the Earth, Nature, 369, 719-723, 1994.
Fazio G.G. , et al., The Infrared Array Camera (IRAC) for the Spitzer Space Telescope, ApJS, 154,10-17, 2004.
Grogan, K., et al., First Spitzer Observations of EarthÕs Resonant Rings,
Protostars and Planets V, 1286., p. 8462, 2005.
Houck, J.R., et al., The Infrared Spectrograph (IRS) on the Spitzer
Space Telescope, ApJS, 154, 18-24, 2004.
Jayaraman, S., Studying the Fine Structure and Temporal Variations of
the Zodiacal Clooud and Asteroidal Dust Bands Using the 3-Year Near-IR COBE-DIRBE
Data, NASA Technical Report, NASA/CR-1999-209246,
1999.
Kelsall, T., et al., The COBE Diffuse Infrared Background Experiment
Search for the cosmic Infrared Background. II Model of the Interplanetary Dust Cloud,Ó AJ, 508, 44073,
1994.
Lowrance, P.J., et al., IRAC Pipeline Description Paper, title/journal
TBD, 2006.
Reach, W.T., SIRTF Background Estimation Methods and Implementation, http://ssc.Spitzer.caltech.edu/documents/background/, 2000.
Reach, W.T., et al., Absolute Calibration fo the Infrared Array Camera
on the Spitzer Space Telescope, PASP,
117, 978-990, 2005.
Rieke, G.H., et al., The Multiband Imaging Photometer for Spitzer
(MIPS), ApJS, 154, 25-29, 2004.
SchlagelÉISM maps
Silverberg, R.F., et al., Proc. SPIE, 2019, 180, 1993—not in
ADS—replace w/ correct DIRBE instrument description paper.
Fig. 1a. Skydark Fig 1b. Skyflat aors

Fig. 2a—100s NEP sky darks – observations

Fig. 2b—30s NEP sky darks – observations and zody model






Fig. 3—100s ecliptic plane sky flats – observations and zody model

Fig. 4—dark monitor NEP observations
***make sure skydark has been added back in correctly in sodb retrievalÉthese plots should match skydarks in fig 2!!

Fig. 5—Zody monitoring observations
POLES:


Leading Blob, PLANE:


Trailing Blob, PLANE:


Leading Blob, +- 15degs from ecliptic plane


Trailing Blob, +- 15degs from ecliptic plane


Fig. 6a—100s NEP sky darks –zody model


Fig. 6b—100s NEP skydark residuals





Fig. 6c —30s NEP skydark models


Fig. 6d—30s NEP skydark residuals




Fig. 7a—100s ecliptic plane sky flats models


Fig. 7b—100s ecliptic plane sky flats – residuals




Fig 8 – 100s NEP sky dark colors


Fig 8b – 100s zody monitor NEP sky dark colors—if these plots match skydark colors, which they should, donÕt include
Fig 8c – 30s NEP sky dark colors

Fig 10 – 100s ecliptic plane sky flat colors



Fig 11. Ecliptic minus NEP



Fig 12a – instrument temperature and zody—ch4 only

Fig 12b – variation with time since last anneal- ch1 is easiest to see (low dn)

Fig 13 – ch4 variation w/ readout


Fig. 8:
correction factor vs. time, NEP; show each band
Fig. 9:
correction factor vs. time, ecliptic plane; show each band
Fig 10:
<skydark mosaics> vs. time
Fig 11:
<COSMOS/GOODS skydark mosaics> vs. time
Tables
Table 1: IRAC skydark observing times and positions
|
DATE |
RA |
DEC |
|
2003-12-02 |
265.1190 |
69.0225 |
|
2003-12-05 |
265.1160 |
69.0243 |
|
2003-12-07 |
265.1140 |
69.0259 |
|
2003-12-18 |
265.1010 |
69.0322 |
|
2003-12-24 |
265.0920 |
69.0352 |
|
2003-12-28 |
265.0860 |
69.0370 |
|
2003-12-21 |
265.0970 |
69.0337 |
|
2004-01-09 |
265.0660 |
69.0416 |
|
2004-01-12 |
265.0600 |
69.0425 |
|
2004-01-15 |
265.0550 |
69.0433 |
|
2004-01-18 |
265.0490 |
69.0440 |
|
2004-01-20 |
265.0450 |
69.0443 |
|
2004-02-09 |
265.0230 |
69.0346 |
|
2004-02-12 |
265.0180 |
69.0347 |
|
2004-02-15 |
265.0140 |
69.0347 |
|
2004-02-19 |
265.0070 |
69.0346 |
|
2004-03-06 |
264.9840 |
68.9797 |
|
2004-03-09 |
264.9800 |
68.9791 |
|
2004-03-13 |
264.9750 |
68.9782 |
|
2004-03-28 |
264.9570 |
68.9736 |
|
2004-03-31 |
264.9540 |
68.9727 |
|
2004-04-04 |
264.9510 |
68.9711 |
|
2004-04-05 |
264.9490 |
68.9705 |
|
2004-04-20 |
264.9380 |
68.9623 |
|
2004-04-23 |
264.9360 |
68.9610 |
|
2004-04-25 |
264.9350 |
68.9598 |
|
2004-04-30 |
264.9330 |
68.9573 |
|
2004-04-28 |
264.9340 |
68.9583 |
|
2004-05-16 |
264.9300 |
69.0034 |
|
2004-05-22 |
264.9310 |
69.0003 |
|
2004-05-25 |
264.9320 |
68.9988 |
|
2004-05-19 |
264.9300 |
69.0019 |
|
2004-06-09 |
264.9380 |
68.9917 |
|
2004-06-29 |
264.9470 |
68.9984 |
|
2004-07-02 |
264.9500 |
68.9972 |
|
DATE |
RA |
DEC |
|
2004-07-07 |
264.9550 |
68.9957 |
|
2004-07-19 |
264.9760 |
68.9773 |
|
2004-07-22 |
264.9800 |
68.9766 |
|
2004-07-25 |
264.9840 |
68.9760 |
|
2004-07-28 |
264.9880 |
68.9755 |
|
2004-08-12 |
265.1500 |
68.9462 |
|
2004-08-17 |
265.1600 |
68.9483 |
|
2004-09-02 |
265.0380 |
68.9751 |
|
2004-09-13 |
265.0520 |
68.9769 |
|
2004-10-05 |
265.0770 |
68.9707 |
|
2004-10-12 |
265.0830 |
68.9734 |
|
2004-10-27 |
265.1270 |
68.9176 |
|
2004-11-01 |
265.1300 |
68.9200 |
|
2004-11-18 |
265.1340 |
68.9285 |
|
2004-11-28 |
265.1330 |
68.9336 |
|
2004-12-15 |
265.0920 |
69.0170 |
|
2004-12-21 |
265.0880 |
69.0198 |
|
2005-01-16 |
265.0620 |
69.0295 |
|
2005-01-22 |
265.0550 |
69.0311 |
|
2005-02-19 |
265.2120 |
69.0347 |
|
2005-02-25 |
265.2030 |
69.0346 |
|
2005-03-25 |
264.9680 |
69.0297 |
|
2005-03-30 |
264.9620 |
69.0280 |
|
2005-05-06 |
264.8580 |
69.0124 |
|
2005-05-10 |
264.8570 |
69.0104 |
|
2005-06-14 |
264.9370 |
68.9925 |
|
2005-06-09 |
264.9340 |
68.9953 |
|
2005-07-15 |
265.0040 |
68.9804 |
|
2005-07-26 |
265.0170 |
68.9774 |
|
2005-08-24 |
265.0990 |
68.9739 |
|
2005-08-17 |
265.0890 |
68.9741 |
|
2005-09-14 |
265.0440 |
68.9674 |
|
2005-09-23 |
265.0550 |
68.9691 |
|
2005-10-21 |
265.0840 |
68.9615 |
|
2005-11-02 |
265.0920 |
68.9668 |
Table 2: IRAC skyflat observing times and positions
|
DATE |
RA |
DEC |
Ec Lon |
EC Lat |
|
2003-12-01 |
344.2980 |
-1.3013 |
345.0340 |
4.9789 |
|
2003-12-04 |
344.2980 |
-1.3011 |
345.0341 |
4.9790 |
|
2003-12-07 |
344.2980 |
-1.3010 |
345.0341 |
4.9792 |
|
2003-12-18 |
2.0325 |
-4.5915 |
0.0341 |
-5.0203 |
|
2003-12-21 |
2.0324 |
-4.5917 |
0.0340 |
-5.0204 |
|
2003-12-24 |
2.0324 |
-4.5919 |
0.0339 |
-5.0206 |
|
2003-12-28 |
2.0324 |
-4.5922 |
0.0337 |
-5.0209 |
|
2004-01-09 |
29.8038 |
6.8643 |
30.1442 |
-4.9700 |
|
2004-01-12 |
29.8037 |
6.8641 |
30.1441 |
-4.9702 |
|
2004-01-15 |
29.8037 |
6.8639 |
30.1440 |
-4.9704 |
|
2004-01-18 |
29.8036 |
6.8637 |
30.1438 |
-4.9706 |
|
2004-01-20 |
29.8036 |
6.8635 |
30.1438 |
-4.9707 |
|
2004-02-09 |
58.9988 |
15.2363 |
60.0740 |
-5.0403 |
|
2004-02-12 |
58.9987 |
15.2361 |
60.0739 |
-5.0405 |
|
2004-02-15 |
58.9986 |
15.2359 |
60.0737 |
-5.0407 |
|
2004-02-19 |
58.9985 |
15.2356 |
60.0736 |
-5.0410 |
|
2004-03-06 |
73.1313 |
27.5455 |
75.0331 |
4.9784 |
|
2004-03-09 |
73.1314 |
27.5456 |
75.0332 |
4.9785 |
|
2004-03-13 |
73.1315 |
27.5458 |
75.0334 |
4.9787 |
|
2004-03-28 |
106.9420 |
27.5372 |
105.0326 |
4.9778 |
|
2004-03-31 |
106.9420 |
27.5373 |
105.0326 |
4.9779 |
|
2004-04-04 |
106.9420 |
27.5375 |
105.0326 |
4.9780 |
|
2004-04-05 |
106.9420 |
27.5376 |
105.0326 |
4.9781 |
|
2004-04-21 |
136.0210 |
11.4619 |
135.0736 |
-5.0708 |
|
2004-04-23 |
136.0210 |
11.4618 |
135.0736 |
-5.0709 |
|
2004-04-26 |
136.0210 |
11.4617 |
135.0737 |
-5.0710 |
|
2004-04-29 |
136.0210 |
11.4615 |
135.0737 |
-5.0712 |
|
2004-05-01 |
136.0210 |
11.4615 |
135.0737 |
-5.0712 |
|
2004-05-17 |
150.5830 |
7.6803 |
149.9328 |
-4.0716 |
|
2004-05-20 |
150.5830 |
7.6802 |
149.9328 |
-4.0717 |
|
2004-05-23 |
150.5830 |
7.6801 |
149.9328 |
-4.0718 |
|
2004-05-26 |
150.5830 |
7.6800 |
149.9329 |
-4.0719 |
|
2004-06-09 |
182.1060 |
4.5529 |
180.1170 |
5.0141 |
|
2004-06-18 |
195.9540 |
-0.8667 |
195.0319 |
5.4769 |
|
2004-06-29 |
195.9550 |
-0.8662 |
195.0326 |
5.4777 |
|
2004-07-03 |
195.9550 |
-0.8661 |
195.0325 |
5.4779 |
|
2004-07-07 |
195.9560 |
-0.8659 |
195.0334 |
5.4784 |
|
2004-07-19 |
220.8980 |
-21.4258 |
225.0343 |
-5.3201 |
|
2004-07-22 |
220.8980 |
-21.4259 |
225.0344 |
-5.3202 |
|
2004-07-25 |
220.8970 |
-21.4260 |
225.0335 |
-5.3206 |
|
2004-07-28 |
220.8970 |
-21.4261 |
225.0335 |
-5.3207 |
|
2004-08-12 |
239.1220 |
-15.2942 |
240.2027 |
5.0081 |
|
2004-08-18 |
239.1230 |
-15.2940 |
240.2036 |
5.0085 |
|
2004-09-03 |
253.2260 |
-27.7859 |
255.1447 |
-5.2076 |
|
2004-09-13 |
253.2250 |
-27.7863 |
255.1438 |
-5.2080 |
|
2004-10-05 |
285.7330 |
-17.6430 |
285.0332 |
4.9790 |
|
2004-10-12 |
285.7340 |
-17.6426 |
285.0342 |
4.9793 |
|
2004-10-27 |
315.9970 |
-11.6069 |
315.0092 |
4.9387 |
|
2004-11-01 |
315.9970 |
-11.6066 |
315.0093 |
4.9390 |
|
2004-11-18 |
330.6010 |
-7.4508 |
330.0295 |
4.2806 |
|
2004-11-28 |
330.6010 |
-7.4504 |
330.0297 |
4.2810 |
|
2004-12-15 |
2.1241 |
-4.5512 |
0.1343 |
-5.0197 |
|
2004-12-21 |
2.1241 |
-4.5516 |
0.1341 |
-5.0201 |
|
2005-01-16 |
29.8037 |
6.8642 |
30.1441 |
-4.9701 |
|
2005-01-22 |
29.8036 |
6.8638 |
30.1439 |
-4.9705 |
|
2005-02-19 |
59.3027 |
15.1249 |
60.3393 |
-5.2095 |
|
2005-02-25 |
59.3026 |
15.1245 |
60.3391 |
-5.2099 |
|
2005-03-25 |
106.5750 |
27.5869 |
104.7025 |
4.9896 |
|
2005-03-31 |
106.5750 |
27.5871 |
104.7024 |
4.9899 |
|
2005-05-06 |
135.9960 |
11.5209 |
135.0330 |
-5.0214 |
|
2005-05-10 |
135.9960 |
11.5207 |
135.0331 |
-5.0215 |
|
2005-06-09 |
164.2810 |
1.2789 |
165.0269 |
-5.0060 |
|
2005-06-15 |
164.2810 |
1.2788 |
165.0269 |
-5.0062 |
|
2005-07-15 |
210.3970 |
-5.0409 |
210.0664 |
6.8850 |
|
2005-07-26 |
210.3980 |
-5.0402 |
210.0672 |
6.8859 |
|
2005-08-18 |
238.8720 |
-15.3765 |
239.9829 |
4.8780 |
|
2005-08-24 |
238.8720 |
-15.3761 |
239.9828 |
4.8784 |
|
2005-09-14 |
253.2670 |
-27.7777 |
255.1799 |
-5.1953 |
|
2005-09-23 |
253.2670 |
-27.7780 |
255.1800 |
-5.1956 |
|
2005-10-21 |
303.8840 |
-26.8279 |
300.0721 |
-6.8570 |
Table 1c: IRAC dark monitor observing times and positions
|
DATE |
RA |
DEC |
|
2004-06-30T21:18:04 |
264.9910 |
69.0070 |
|
2004-07-05T09:48:10 |
264.9910 |
69.0064 |
|
2004-07-05T21:48:14 |
264.9910 |
69.0063 |
|
2004-07-06T09:48:21 |
264.9910 |
69.0062 |
|
2004-07-06T21:47:58 |
264.9910 |
69.0062 |
|
2004-07-07T12:18:24 |
264.9910 |
69.0061 |
|
2004-07-01T09:18:07 |
264.9910 |
69.0070 |
|
2004-07-01T21:18:12 |
264.9910 |
69.0069 |
|
2004-07-02T08:50:18 |
264.9910 |
69.0068 |
|
2004-07-02T23:47:34 |
264.9910 |
69.0067 |
|
2004-07-03T09:48:37 |
264.9910 |
69.0067 |
|
2004-07-03T22:03:06 |
264.9910 |
69.0066 |
|
2004-07-04T10:03:10 |
264.9910 |
69.0065 |
|
2004-07-04T21:48:10 |
264.9910 |
69.0064 |
|
2004-06-29T12:48:01 |
264.9910 |
69.0072 |
|
2004-06-29T21:15:16 |
264.9910 |
69.0072 |
|
2004-06-30T09:18:22 |
264.9910 |
69.0071 |
|
2003-12-18T23:51:40 |
265.0370 |
68.9999 |
|
2003-12-19T13:06:39 |
265.0370 |
68.9999 |
|
2003-12-24T00:51:49 |
265.0380 |
69.0006 |
|
2003-12-24T13:09:36 |
265.0380 |
69.0006 |
|
2003-12-20T00:36:40 |
265.0370 |
69.0000 |
|
2003-12-20T12:13:22 |
265.0370 |
69.0001 |
|
2003-12-21T00:21:44 |
265.0370 |
69.0001 |
|
2003-12-21T16:32:35 |
265.0370 |
69.0002 |
|
2003-12-21T23:51:45 |
265.0370 |
69.0003 |
|
2003-12-22T13:09:43 |
265.0370 |
69.0004 |
|
2003-12-23T00:51:47 |
265.0370 |
69.0004 |
|
2003-12-23T13:09:46 |
265.0380 |
69.0005 |
|
2003-12-25T00:21:51 |
265.0380 |
69.0007 |
|
2003-12-25T12:51:52 |
265.0380 |
69.0008 |
|
2003-12-27T00:21:57 |
265.0380 |
69.0010 |
|
2003-12-27T12:51:57 |
265.0380 |
69.0011 |
|
2003-12-26T00:06:53 |
265.0380 |
69.0008 |
|
2003-12-26T12:51:55 |
265.0380 |
69.0009 |
|
2003-12-28T00:06:58 |
265.0380 |
69.0011 |
|
2003-12-28T12:51:59 |
265.0380 |
69.0012 |
|
2004-01-10T00:21:55 |
265.0400 |
69.0031 |
|
2004-01-10T12:14:51 |
265.0400 |
69.0031 |
|
2004-01-15T00:20:23 |
265.0400 |
69.0038 |
|
2004-01-16T00:20:17 |
265.0400 |
69.0040 |
|
2004-01-16T23:20:10 |
265.0400 |
69.0041 |
|
2004-01-17T11:20:06 |
265.0400 |
69.0042 |
|
2004-01-17T23:20:02 |
265.0400 |
69.0043 |
|
2004-01-18T23:39:56 |
265.0400 |
69.0044 |
|
2004-01-11T00:21:49 |
265.0400 |
69.0032 |
|
2004-01-19T12:19:52 |
265.0400 |
69.0045 |
|
2004-01-20T00:19:49 |
265.0400 |
69.0046 |
|
2004-01-21T00:14:42 |
265.0400 |
69.0048 |
|
2004-01-11T12:21:46 |
265.0400 |
69.0033 |
|
2004-01-13T00:21:37 |
265.0400 |
69.0035 |
|
2004-01-13T11:51:33 |
265.0400 |
69.0036 |
|
2004-01-14T00:40:29 |
265.0400 |
69.0037 |
|
2004-01-14T11:50:26 |
265.0400 |
69.0038 |
|
2004-01-16T10:20:13 |
265.0400 |
69.0041 |
|
2004-01-12T00:21:42 |
265.0400 |
69.0034 |
|
2004-02-10T11:27:48 |
265.0380 |
69.0078 |
|
2004-02-09T11:22:47 |
265.0380 |
69.0077 |
|
2004-02-14T11:17:52 |
265.0370 |
69.0084 |
|
2004-02-15T03:22:16 |
265.0370 |
69.0085 |
|
2004-02-15T12:17:54 |
265.0370 |
69.0086 |
|
2004-02-15T23:10:53 |
265.0370 |
69.0086 |
|
2004-02-16T11:07:55 |
265.0370 |
69.0087 |
|
2004-02-16T23:17:55 |
265.0370 |
69.0088 |
|
2004-02-17T11:17:56 |
265.0360 |
69.0088 |
|
2004-02-17T23:17:56 |
265.0360 |
69.0089 |
|
2004-02-18T11:18:32 |
265.0360 |
69.0089 |
|
2004-02-18T23:17:52 |
265.0360 |
69.0090 |
|
2004-02-09T23:17:48 |
265.0380 |
69.0078 |
|
2004-02-19T15:12:25 |
265.0360 |
69.0091 |
|
2004-02-10T23:37:50 |
265.0380 |
69.0079 |
|
2004-02-11T11:37:49 |
265.0380 |
69.0080 |
|
2004-02-12T02:52:07 |
265.0380 |
69.0081 |
|
2004-02-12T11:27:51 |
265.0380 |
69.0081 |
|
2004-02-12T23:17:52 |
265.0370 |
69.0082 |
|
2004-02-13T10:57:52 |
265.0370 |
69.0083 |
|
2004-02-13T23:17:51 |
265.0370 |
69.0083 |
|
2004-03-06T01:49:32 |
265.0320 |
69.0109 |
|
2004-03-10T12:14:07 |
265.0300 |
69.0114 |
|
2004-03-10T23:47:42 |
265.0300 |
69.0114 |
|
2004-03-11T12:17:42 |
265.0300 |
69.0115 |
|
2004-03-12T00:17:38 |
265.0300 |
69.0115 |
|
2004-03-12T12:17:37 |
265.0300 |
69.0116 |
|
2004-03-13T00:17:36 |
265.0290 |
69.0116 |
|
2004-03-13T15:13:25 |
265.0290 |
69.0117 |
|
2004-03-06T15:22:29 |
265.0320 |
69.0110 |
|
2004-03-06T23:48:04 |
265.0310 |
69.0110 |
|
2004-03-07T11:48:05 |
265.0310 |
69.0111 |
|
2004-03-07T23:48:05 |
265.0310 |
69.0111 |
|
2004-03-08T11:18:05 |
265.0310 |
69.0112 |
|
2004-03-08T23:13:09 |
265.0310 |
69.0112 |
|
2004-03-09T15:23:08 |
265.0310 |
69.0113 |
|
2004-03-09T23:46:08 |
265.0300 |
69.0113 |
|
2004-03-28T23:18:05 |
265.0230 |
69.0127 |
|
2004-04-01T23:01:37 |
265.0220 |
69.0129 |
|
2004-04-02T12:07:55 |
265.0210 |
69.0129 |
|
2004-04-02T23:05:39 |
265.0210 |
69.0129 |
|
2004-04-03T11:07:01 |
265.0210 |
69.0130 |
|
2004-04-04T10:04:56 |
265.0210 |
69.0130 |
|
2004-04-04T22:18:09 |
265.0200 |
69.0130 |
|
2004-04-05T14:08:37 |
265.0200 |
69.0130 |
|
2004-03-29T11:14:51 |
265.0230 |
69.0127 |
|
2004-03-29T23:04:50 |
265.0230 |
69.0128 |
|
2004-03-30T11:06:53 |
265.0230 |
69.0128 |
|
2004-03-31T02:13:41 |
265.0220 |
69.0128 |
|
2004-03-31T11:08:03 |
265.0220 |
69.0128 |
|
2004-04-04T02:08:53 |
265.0210 |
69.0130 |
|
2004-03-31T23:02:51 |
265.0220 |
69.0129 |
|
2004-04-01T11:15:05 |
265.0220 |
69.0129 |
|
2004-04-21T09:31:27 |
265.0130 |
69.0132 |
|
2004-04-26T00:15:38 |
265.0110 |
69.0131 |
|
2004-04-26T09:08:40 |
265.0110 |
69.0131 |
|
2004-04-26T21:48:23 |
265.0110 |
69.0131 |
|
2004-04-27T10:15:11 |
265.0110 |
69.0131 |
|
2004-04-27T22:03:06 |
265.0110 |
69.0131 |
|
2004-04-28T10:03:31 |
265.0100 |
69.0131 |
|
2004-04-29T00:45:24 |
265.0100 |
69.0130 |
|
2004-04-21T21:33:30 |
265.0130 |
69.0132 |
|
2004-04-29T11:28:17 |
265.0100 |
69.0130 |
|
2004-04-29T23:18:20 |
265.0100 |
69.0130 |
|
2004-04-30T11:13:28 |
265.0100 |
69.0130 |
|
2004-05-01T00:45:54 |
265.0090 |
69.0130 |
|
2004-05-01T10:18:13 |
265.0090 |
69.0130 |
|
2004-04-22T09:22:41 |
265.0130 |
69.0132 |
|
2004-04-22T22:01:21 |
265.0130 |
69.0132 |
|
2004-04-23T13:24:12 |
265.0120 |
69.0132 |
|
2004-04-23T22:18:11 |
265.0120 |
69.0132 |
|
2004-04-24T09:49:15 |
265.0120 |
69.0132 |
|
2004-04-24T21:44:28 |
265.0120 |
69.0132 |
|
2004-04-25T09:35:51 |
265.0120 |
69.0132 |
|
2004-05-16T10:47:22 |
265.0030 |
69.0122 |
|
2004-05-20T00:57:47 |
265.0020 |
69.0119 |
|
2004-05-20T10:40:34 |
265.0020 |
69.0119 |
|
2004-05-20T22:15:10 |
265.0020 |
69.0118 |
|
2004-05-21T21:48:22 |
265.0010 |
69.0117 |
|
2004-05-22T09:48:28 |
265.0010 |
69.0117 |
|
2004-05-23T00:35:59 |
265.0010 |
69.0116 |
|
2004-05-24T10:12:24 |
265.0000 |
69.0115 |
|
2004-05-23T22:38:18 |
265.0000 |
69.0116 |
|
2004-05-23T10:48:47 |
265.0010 |
69.0116 |
|
2004-05-24T22:43:31 |
265.0000 |
69.0115 |
|
2004-05-25T10:48:39 |
265.0000 |
69.0114 |
|
2004-05-16T16:08:50 |
265.0030 |
69.0122 |
|
2004-05-26T01:03:33 |
265.0000 |
69.0114 |
|
2004-05-26T10:24:46 |
265.0000 |
69.0113 |
|
2004-05-21T10:28:18 |
265.0010 |
69.0118 |
|
2004-05-26T22:03:16 |
264.9990 |
69.0113 |
|
2004-05-27T10:48:22 |
264.9990 |
69.0112 |
|
2004-05-16T12:11:12 |
265.0030 |
69.0122 |
|
2004-05-16T16:33:07 |
265.0030 |
69.0122 |
|
2004-05-16T20:09:45 |
265.0030 |
69.0121 |
|
2004-05-17T10:33:24 |
265.0030 |
69.0121 |
|
2004-05-17T22:13:32 |
265.0030 |
69.0120 |
|
2004-05-18T11:08:11 |
265.0020 |
69.0120 |
|
2004-05-18T21:58:14 |
265.0020 |
69.0120 |
|
2004-05-19T10:47:20 |
265.0020 |
69.0119 |
|
2004-06-08T22:34:09 |
264.9960 |
69.0099 |
|
2004-06-08T23:11:58 |
264.9960 |
69.0099 |
|
2004-06-09T21:48:38 |
264.9950 |
69.0098 |
|
2004-06-10T10:33:12 |
264.9950 |
69.0097 |
|
2004-06-10T22:18:09 |
264.9950 |
69.0097 |
|
2004-06-28T21:37:15 |
264.9920 |
69.0073 |
Table 1d: IRAC zodiacal background monitor observing times and positions (include solar elongation)
|
DATE |
Position |
RA |
DEC |
EcLon |
EcLat |
SolElong |
|
2004-07-22T18:17:58 |
LB_above |
15.2828 |
22.8254 |
22.9893 |
15.0272 |
-95 |
|
2004-07-22T18:48:41 |
LB_plane |
21.2587 |
8.963 |
22.99 |
0.0273 |
-95 |
|
2004-07-22T19:17:38 |
LB_below |
26.7856 |
-4.9883 |
22.9902 |
-14.9726 |
-95 |
|
2004-07-22T18:33:42 |
LB_plane_east |
2.7328 |
1.214 |
2.99 |
0.0273 |
-115 |
|
2004-07-22T19:02:30 |
LB_plane_west |
30.7682 |
12.5343 |
32.99 |
0.0273 |
-85 |
|
2004-07-22T12:03:25 |
NEP |
264.963 |
68.982 |
125.89 |
86.9208 |
-
- |
|
2004-07-22T16:35:44 |
SEP |
93.8898 |
-64.0421 |
124.6153 |
-87.0037 |
-
- |
|
2004-07-22T15:00:45 |
TB_above |
215.863 |
1.587 |
213.0096 |
14.9726 |
+95 |
|
2004-07-22T15:30:02 |
TB_plane |
210.787 |
-12.5409 |
213.0096 |
-0.0273 |
+95 |
|
2004-07-22T16:00:50 |
TB_below |
205.114 |
-26.5627 |
213.0111 |
-15.0268 |
+95 |
|
2004-07-22T15:15:54 |
TB_plane_east |
201.277 |
-8.9703 |
203.0095 |
-0.0274 |
+115 |
|
2004-07-22T15:45:01 |
TB_plane_west |
230.543 |
-18.5017 |
232.9399 |
0.0059 |
+85 |
|
2004-08-12T21:47:23 |
NEP |
264.988 |
68.9768 |
125.826 |
86.9306 |
-
- |
|
2004-08-12T23:22:31 |
SEP |
93.8945 |
-64.0322 |
124.551 |
-86.9941 |
-
- |
|
2004-08-12T23:42:49 |
LB_above |
34.0897 |
29.5968 |
41.7891 |
15.0272 |
-95 |
|
2004-08-13T00:12:25 |
LB_plane |
39.3444 |
15.3978 |
41.7902 |
0.0274 |
-95 |
|
2004-08-13T00:26:25 |
LB_below |
43.9121 |
1.0914 |
41.7905 |
-14.9725 |
-95 |
|
2004-08-12T23:58:04 |
LB_plane_east |
20.132 |
8.5168 |
21.7903 |
0.0274 |
-115 |
|
2004-08-12T22:05:49 |
TB_above |
233.234 |
-3.7261 |
231.8098 |
14.9725 |
+95 |
|
2004-08-12T22:35:43 |
TB_plane |
229.383 |
-18.2447 |
231.8099 |
-0.0273 |
+95 |
|
2004-08-12T23:04:06 |
TB_below |
224.817 |
-32.6721 |
231.8105 |
-15.0271 |
+95 |
|
2004-08-12 |