\documentclass[11pt,twoside]{article}  % Leave intact
\usepackage{adassconf}

\begin{document}   % Leave intact

\paperID{P4-15}
%%%% ID=P4-15

%-----------------------------------------------------------------------
%		            Paper Title 
%-----------------------------------------------------------------------

\title{Chandra Level 3 Processing: Creating an Automated Source Catalog for Chandra Data}
\titlemark{Chandra Level 3 Processing}

%-----------------------------------------------------------------------
%		          Authors of Paper
%-----------------------------------------------------------------------

\author{Roger Hain, Adam Dobrzycki, Ian Evans, Janet DePonte Evans, Peter Freeman, Kenny Glotfelty, Margarita Karovska, Michael McCollough, Francis Primini, Arnold Rots}

\affil{Harvard-Smithsonian Center for Astrophysics, 60 Garden St., Cambridge, MA 02138}

%-----------------------------------------------------------------------
%			 Contact Information
%-----------------------------------------------------------------------

\contact{Roger Hain}
\email{rhain@head-cfa.harvard.edu}

%-----------------------------------------------------------------------
%		      Author Index Specification
%-----------------------------------------------------------------------
% Specify how each author name should appear in the author index.  The 
% \paindex{ } should be used to indicate the primary author, and the
% \aindex for all other co-authors.  You MUST use the following
% syntax: 
%
% SYNTAX:  \aindex{LASTNAME, F. M.}
% 
% where F is the first initial and M is the second initial (if
% used).  This guarantees that authors that appear in multiple papers
% will appear only once in the author index.  
%
% EXAMPLE: \paindex{Crabtree, D.}
%          \aindex{Manset, N.}
%          \aindex{Veillet, C.}
%
% NOTE: this information is also used to build the author list that
% appears in the table of contents.  Authors will be listed in the order
% of the \paindex and \aindex commmands.
%

\paindex{Hain, R.}
\aindex{Dobrzycki, A.}
\aindex{Evans, I.}
\aindex{Evans, J. DePonte}
\aindex{Freeman, P.}
\aindex{Glotfelty, K.}
\aindex{Karovska, M.}
\aindex{McCollough, M.}
\aindex{Primini, F.}
\aindex{Rots, A.}


%-----------------------------------------------------------------------
%                     Author list for page header
%-----------------------------------------------------------------------
% Please supply a list of author last names for the page header. in
% one of these formats:
%
% EXAMPLES:
% \authormark{LASTNAME}
% \authormark{LASTNAME1 \& LASTNAME2}
% \authormark{LASTNAME1, LASTNAME2, ... \& LASTNAMEn}
% \authormark{LASTNAME et al.}
%
% Use the "et al." form in the case of seven or more authors, or if
% the preferred form is too long to fit in the header.

\authormark{Hain et al.}

%-----------------------------------------------------------------------
%			Subject Index keywords
%-----------------------------------------------------------------------
% Enter up to 6 keywords describing your paper.  These will NOT be
% printed as part of your paper; however, they will be used to
% generate the subject index for the proceedings.  There is no
% standard list; however, you can consult the indices for past ADASS
% proceedings (http://adass.org/adass/proceedings/).

\keywords{AXAF, Chandra, pipelines, catalogs, source detection, source properties}

%-----------------------------------------------------------------------
%			       Abstract
%-----------------------------------------------------------------------
% Type abstract in the space below.  Consult the User Guide and Latex
% Information file for a list of supported macros (e.g. for typesetting 
% special symbols). Do not leave a blank line between \begin{abstract} 
% and the start of your text.

\begin{abstract}          % Leave intact
Efforts are underway at the Chandra X-ray Center to develop a new level of data processing capability which will result in the creation of a source catalog spanning the full set of Chandra observations.  Level 3 processing will include detailed source properties derived from all available Chandra data.  The resulting catalog will provide easy access to Chandra data for an expanded number of astronomers, particularly those less familiar with analysis in the X-ray regime.  It will allow easy searching of the archive for specific sources or for statistical properties of different classes of targets.  In addition, consistent sets of data products along with all relevant calibrations will be available for detailed analyses.

Work has begun on developing a preliminary data processing pipeline, combining existing processing tools and identifying functionality which needs to be developed.  Some effort has been made to identify a quick source detection algorithm which can work in the presence of the low-count background and source photons typical of Chandra X-ray data, and also be robust enough to find multiple or extended sources.  Eventual goals of Level 3 processing include refining source detection and properties by simultaneously fitting multiple observations, and cross-matching identified sources with other catalogs.  In this paper we present the current design, challenges, and discuss the various analysis trade-offs.
\end{abstract}

%-----------------------------------------------------------------------
%			      Main Body
%-----------------------------------------------------------------------
% Place the text for the main body of the paper here.  You should use
% the \section command to label the various sections; use of
% \subsection is optional.  Significant words in section titles should
% be capitalized.  Sections and subsections will be numbered
% automatically. 

\section{Goals}

There are three main goals that drive the development of the Chandra Level 3 pipeline project.  The first is the desire to create a catalog of all detected sources from all Chandra observations.  This will be done by automating source detection to extract all sources in the field of view.  It specifically envisions making use of all available data from combined observations to maximize the ability to detect and quantify all possible sources.

In addition to identifying sources and their locations, the second goal is to provide detailed source properties for all detected sources.  This will mean archiving a uniform set of properties for all catalog objects.  All relevant calibration data will also be made available in the catalog.

Having detected sources and cataloged detailed information, the third goal is to provide easy access to all Chandra data for a broad based group of astronomers.  The catalog and interface will enable easy searches for sources and properties, and also enable easy searches for statistical properties over a class of sources.  In addition to providing information for pure scientific research, the data should also aid in preparing future proposals or observations.


\section{Prototype Pipeline}

The prototype Level 3 pipeline is currently being developed.  In its initial steps, it processes individual observation IDs (obsids) to automatically extract source data and populate the archive. Event data from an obsid is preprocessed by removing bad pixels and creating a simplified exposure map.  This information is used by the source extraction software to identify source regions (Figure~\ref{P4-15:SourceReg}).  Source detection is performed on the broadband image, and also on the hard, medium, and soft energy ranges independently. Successively larger regions centered at the mirror focal point are examined at higher blocking factors.  These larger blocking factors are matched to the increase in size of Chandra's point spread function (PSF).

% L3 pipe step 1: source regions
\begin{figure}
\epsscale{0.35}
\plotone{P4-15_1.ps}
\caption{Sample source regions identified by the Level 3 pipeline}
\label{P4-15:SourceReg}
\end{figure}

Sources from the event list examined at different blocking factors and energy levels are then merged to create a complete source list.  Each source region is identified, along with an appropriate background region.  Further analysis is performed on a per source basis, with parallel paths for each source through the pipeline.  To assist in the forward fitting step, in which sources are identified as either a single point source, two point sources, or a more complex source, the Chandra PSF is calculated at multiple energy levels (Figure~\ref{P4-15:psfs}).  Exposure maps of both the broadband background region and of the individual energy regions are also calculated.

% L3 pipe step 2: PSFs
\begin{figure}
\plottwo{P4-15_2.ps} {P4-15_3.ps}
\caption{Sample source PSFs for 2 energy bands: soft (left) and hard}
\label{P4-15:psfs}
\end{figure}

The forward fitting step identifies the type of source (single, double, complex) and provides source property information.  Flux, hardness ratio, and other quantities are calculated.  Additional information, such as lightcurves and spectral information, are extracted.  Data are then fed into the archive.  The archive is examined for existing data on the source, and if found, portions of the Level 3 pipeline will be run again with merged data from multiple obsids.  The archive will maintain the most complete information from all obsids that have been incorporated into the Level 3 pipeline.  It will include not just source property information, but also ancillary data, such as the regions from which source and background information was extracted, exposure map data, etc.


\section{Challenges}

This section highlights four of the most significant challenges that will need to be met in order to create the Level 3 pipeline.

\emph{Low Count Data.}  Chandra X-ray data typically consist of low-count source data when compared to background data, often making it difficult for source detection algorithms to distinguish sources, reject false sources, and separate two nearby sources.  Since the Chandra PSF grows significantly away from the focal point of the mirrors, resolution between multiple sources far from the focal point becomes increasingly difficult.  Shown on the left in Figure~\ref{P4-15:challenges} are some test studies performed to determine the ability of one candidate source extraction routine, SExtractor (Bertin), to resolve sources in the presence of varying backgrounds and distances from the focal point.  The graphs show that increasing distance from the focal point and decreasing source events increases resolving difficulty for a pair of sources 4 arcseconds apart.

% L3 challenges
\begin{figure}
\epsscale{0.4}
\plottwo{P4-15_4.ps}{P4-15_5.ps}
\caption{Challenges: Source detection results (left), overlapping ROIs}
\label{P4-15:challenges}
\end{figure}

\emph{Regions of Interest.}
Determining the source and background regions for cleanly separated sources is not difficult.  But when multiple sources are near each other and source and background photons overlap, identifying regions of interest (ROIs) becomes harder. For example, at the right in Figure~\ref{P4-15:challenges} two sources are near enough that the source and background photons (nested circular regions) overlap in a small area. Should the overlapping photons be assigned to both sources, divided equally, or ignored?  Various characterizations of the source and background region are currently being evaluated in a forward fitting algorithm.

\emph{Processing Complexity.}
Efficiently handling the large number of per source files and supporting data created by the Level 3 pipeline is necessary to minimize processing times.  The current pipeline produces a very large number of files.  Focal plane images at several blocking factors and energies are produced. Per source exposure maps and PSF files are created at each energy band. Spectral and temporal information, per source viewable image files and additional smoothed images are created.  Then, if prior Level 3 processing has already created archive entries for a source, all processing is repeated combining data from current and prior observations of this source for a new archive entry.

\emph{Archive.}
Challenges for the Level 3 archive come from the need to provide uniform data for all sources, despite the different character of the sources and the different needs of potential users.  Issues also arise from combining multiple observations of the same source.  Some archived quantities are not easy to merge into a combined catalog entry.  Spectral information, for example, may vary among different observations of the same source.  Which method is best to represent these types of data?  How should factors such as exposure length vs.\ off-axis angle be weighed against each other?

\section{Conclusion}

Work is underway on the Chandra Level 3 pipeline to produce a source catalog with detailed information for all Chandra sources.  An initial prototype pipeline is being developed, highlighting numerous challenges that need to be addressed.  Refinements will be made to the pipeline as research into these issues matures.

\acknowledgments

This project is supported by the Chandra X-ray Center under NASA contract NAS8-39073.

%-----------------------------------------------------------------------
%			      References
%-----------------------------------------------------------------------
% List your references below within the reference environment
% (i.e. between the \begin{references} and \end{references} tags).
% Each new reference should begin with a \reference command which sets
% up the proper indentation.  Observe the following order when listing
% bibliographical information for each reference:  author name(s),
% publication year, journal name, volume, and page number for
% articles.  Note that many journal names are available as macros; see
% the User Guide for a listing "macro-ized" journals.   
%
% Note the following are some of the tricks that can be used:
%
%   o  \& is used to format an ampersand symbol (&).
%   o  \'e puts an accent grave over the letter e.  See the User Guide
%      for details on formatting special characters.  
%   o  "\ " after a period prevents LaTeX from interpreting the period 
%      as an end of a sentence.
%   o  \aj is a macro that expands to "Astron. J."  See the User Guide
%      for a full list of journal macros
%   o  \adassvii is a macro that expands to the full title, editor,
%      and publishing information for the ADASS VII conference
%      proceedings.  Such macros are defined for ADASS conferences I
%      through IX.
%   o  When referencing a paper in the current volume, use the
%      \adassix and \paperref macros.  The argument to \paperref is
%      the paper ID code for the paper you are referencing.  See the 
%      note in the "Paper ID Code" section above for details on how to 
%      determine the paper ID code for the paper you reference.  
%
\begin{references}
\reference Bertin, E.\ SExtractor User's Guide, \\
\url{http://terapix.iap.fr/cplt/oldSite/soft/sextractor}
\end{references}

% Do not place any material after the references section

\end{document}  % Leave intact
