Progress Report Ian Evans (CXCDS) and Jonathan McDowell (SDS) Chandra Users ’ Committee Meeting September 19, 2007.

Slides:



Advertisements
Similar presentations
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Advertisements

The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
Progress Report Ian Evans (CXCDS) On behalf of the Chandra Source Catalog Project Team Chandra Users’ Committee Meeting April 9, 2008.
Chandra Calibration Status ACIS 1.Gain corrections for epochs 28 and 29 (Nov – April 2007) were released in CALDB 3.4 on May 16, Gain corrections.
Chandra Calibration Status Summary 1.The gratings and mirrors are very well calibrated at this time and there are no time-dependent effects as far as we.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
CXC Manager’s Status Report Chandra User Committee Meeting Roger J. Brissenden 25 June 2002.
RIT Software Engineering
SE 450 Software Processes & Product Metrics 1 Defect Removal.
Iterative development and The Unified process
CXC CUC September SDS Page 1 CUC Sep 2007 Science Data Systems – Jonathan McDowell.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Implementation/Acceptance Testing / 1 Implementation and Acceptance Testing Physical Implementation Criteria: 1. Data availability 2. Data reliability.
Testing - an Overview September 10, What is it, Why do it? Testing is a set of activities aimed at validating that an attribute or capability.
Commissioning the NOAO Data Management System Howard H. Lanning, Rob Seaman, Chris Smith (National Optical Astronomy Observatory, Data Products Program)
Annie Griffith Infrastructure Programme Manager July 2007 UK Link Technology Refresh.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
RUP Fundamentals - Instructor Notes
Chapter 2 The process Process, Methods, and Tools
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
N By: Md Rezaul Huda Reza n
Progress Report Ian Evans On behalf of the Chandra Source Catalog Project Team Chandra Users’ Committee Meeting October 23, 2014.
© Grant Thornton | | | | | Guidance on Monitoring Internal Control Systems COSO Monitoring Project Update FEI - CFIT Meeting September 25, 2008.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
MULTIMEDIA DEVELOPMENT
Chapter 6 : Software Metrics
CXC CUC April SDS Page 1 Science Data Systems – Jonathan McDowell CUC April 2007 SCIENCE DATA SYSTEMS.
1 ANASAC Meeting – May 20, 2015 ALMA Pipeline Brian Glendenning (for Jeff Kern)
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Introduction to Interactive Media The Interactive Media Development Process.
Installation and Maintenance of Health IT Systems
Service Transition & Planning Service Validation & Testing
EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,
1 Project Risk Management Project Risk Management Dr. Said Abu Jalala.
RMS Update to TAC May 8, RMS Update to TAC ► At April 9 RMS Meeting:  Antitrust Training  RMS Voting Items: ► NPRR097Changes to Section 8 to Incorporate.
TSS Project Update WRAP Technical Analysis Forum San Francisco, CA October 11, 2007.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CesrTA Experimental Plan M. Palmer for the CesrTA Collaboration November 17, 2008.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Project Management Methodology
Request for Service (RFS) Process and Metrics Update June 24, 2008.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Implementation Review1 Archive Ingest Redesign March 14, 2003.
Information Technology Service Availability Metrics March 2008.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
PDS4 Project Report PDS MC F2F University of Maryland Dan Crichton March 27,
MyFloridaMarketPlace Quality Improvement Plan. Page 2 MFMP Quality Improvement Plan  The MFMP team has developed a quality improvement plan that addresses.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
1 CMBG 2009 Planning for Obsolescence June 27, 2009 John Parler South Carolina Electric & Gas.
Advanced Software Engineering Dr. Cheng
Software Project Configuration Management
Managing the Project Lifecycle
IEEE Std 1074: Standard for Software Lifecycle
Proposal for LAT Year 1 Data Release Plan
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
CS/EE/ME 75(a) Nov. 19, 2018 Today: Prelimnary Design Review Homework.
Amendment Invoice Task Force Progress Report
M. Kezunovic (P.I.) S. S. Luo D. Ristanovic Texas A&M University
A handbook on validation methodology. Metrics.
Presentation transcript:

Progress Report Ian Evans (CXCDS) and Jonathan McDowell (SDS) Chandra Users ’ Committee Meeting September 19, 2007

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 2 Outline Acknowledgements The Chandra Source Catalog is a collaborative effort between the scientists and software developers of CXCDS and the scientists of SDS This presentation includes contributions from both groups –Other CXC scientists have provided contributions in some areas Presentation Outline This presentation is divided into two parts –Outline of overall progress since the last CUC meeting and schedule update Presented by Ian on behalf of the Chandra Source Catalog team (CXCDS and SDS) –Detailed discussion of science progress, issues, and investigations, with examples Presented by Jonathan on behalf of the Chandra Source Catalog team (SDS and CXCDS)

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 3 Summary Significant progress has been made since the last CUC meeting –About a dozen requirements and specs have been delivered by the science team –A similar number are currently in-work, including several that have science studies in progress or completed –The software team has completed the CAT 2.5 (Operational Testbed 1) release, which is now operational and providing feedback to the science and software teams –Development work for the CAT 2.6 (Operational Testbed 2) release is well underway The science and software teams are fully engaged and understand the priorities and schedule –Priorities are clearly established by the CXC management Currently estimating start of production in May 2008, with first public data access in June, and formal release 1 in October –First public access includes ~1/3 of public imaging observations processed and available, and preliminary statistical characterization of catalog properties –Catalog release includes public mission-to-date imaging observations and complete statistical characterization of catalog properties available –This schedule reflects an approximately 2 month slip since March Due to a mix of internal (catalog) and external (non-catalog) factors We used the risk mitigation process defined earlier this year to limit the impacts of the slip and ensure that the teams are focused on the project goals

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 4 Progress: Science Highlights Science Highlights Since Last CUC Meeting Details will be discussed by Jonathan later in this presentation Algorithms, requirements, and specifications (with targeted software releases) –Aperture photometry Developed algorithms to compute aperture photometry rates, fluxes, and errors, and limiting sensitivity maps (CAT 2.5, 2.6) –Background Maps and Source Detection Refined algorithms to compute ACIS streak map and low freq. background (CAT 2.5) Developed algorithm to compute HRC-I low frequency background (CAT 2.6) Developed specification for estimating source position uncertainties (CAT 2.5) –Spatial Properties Developed an algorithm for identifying observations with large extended sources [to be excluded from processing] (CAT 3.0) –Spectral Properties Developed specifications for computing spectral fits & energy flux in bands (CAT 2.5, 2.6) Developed specification for computing hardness ratios (CAT 2.6) –Temporal Properties Developed specifications for evaluating time variability of sources (CAT 2.5, 2.6) Developed an algorithm for identifying and removing background flares (CAT 2.7) –Master Source Properties Developed algorithm for combining error ellipses from multiple observations that include the same source (CAT 2.6)

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 5 Progress: Science Highlights (cont.) Science Highlights Since Last CUC Meeting (continued) Science Studies –Background Maps and Source Detection Evaluated impacts of HRC-S detector structure on background map computations Evaluated performance of wavdetect on extended sources and systematic errors in source region parameters computed by wavdetect –Spatial Properties Evaluating a scale-less algorithm for estimating source extent –Temporal Properties Evaluating approaches for removing effects of dither from time variability measures –Master Source Properties Developed estimator of pile-up fraction as a function of count rate

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 6 Documents Documents Delivered Since Last CUC Meeting Requirements and specifications –“Combining Error Ellipses”, J. Davis, SDS/MIT –“Chandra Source Catalog Quality Assurance Specifications”, I. Evans, CXCDS –“Chandra Source Catalog Requirements, Version 0.6”, I. Evans, CXCDS –“Computation of Hardness Ratios Using BEHR”, I. Evans, CXCDS –“Chandra Source Catalog Background Map Flux, Edge, and Exposure Map Modifications”, M. McCollough & A. Rots, CXCDS –“HRC-I Background Map Requirements”, M. McCollough & A. Rots, CXCDS –“Avoiding Numerical Instabilities in Computing Aperture Fluxes”, F. Primini, SDS –“Computing L3 Limiting Sensitivity Maps”, F. Primini, SDS –“Recommendations for Estimating L3 Source Position Uncertainties”, F. Primini, SDS –“Revised Specifications for Computing Aperture Photometry Quantities”, F. Primini, SDS –“Detection of Background Flares and Similar Phenomena”, A. Rots, CXCDS –“Identification of Observations Containing Large Extended Sources”, A. Rots, CXCDS –“L3 Temporal Variability Measures”, A. Rots, CXCDS Science study reports –“Pile-up Fractions and Count Rates”, J. Davis, SDS/MIT –“Measuring Detected Source Extent Using Mexican-Hat Optimization”, J. Houck, SDS/MIT –“HRC-S Background Map Issues”, M. McCollough & A. Rots, CXCDS –“Preliminary Assessment of Dither Corrections for L3 Lightcurves”, M. Nowak, SDS/MIT –“Thoughts on Filtering Flares in L3 Background Files”, M. Nowak, SDS/MIT –“Evaluation on wavdetect Performance on Extended Sources”, F. Primini, SDS

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 7 Progress: Software Highlights Software Highlights Since Last CUC Meeting Requirements and specifications –Revised Chandra Source Catalog Requirements document to version 0.6 Major change is the addition of two-sided confidence intervals for photometric and spectrometric quantities Aperture fluxes and associated values, spectral fit parameters, hardness ratios Replaces symmetric Gaussian errors in previous version Updates to definition of temporal variability properties Now record several quantities that are already calculated in algorithm Improved definitions of the contents of some data products Removed TBDs, added clarifications based on science use cases and requirements for calculating limiting sensitivity A number of minor changes/clarifications, and resolution of several TBDs –Quality assurance requirements updated Incorporates more robust false source rejection tests Details requirements for manual quality assurance steps and GUI Feedback from CAT 2.5 testing valuable for assessing quality assurance efficacy –Catalog infrastructure reviews Extensive reviews of quality assurance, catalog inclusion criteria, master pipeline transactions, and database interfaces established detailed system-wide infrastructure

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 8 Progress: Software Highlights (cont.) Software Highlights Since Last CUC Meeting (continued) CAT 2.5 (Operational Testbed 1) build released –First release with archive and database integration with processing pipelines –Pipelines match Requirements Document version 0.5, with waivers for incomplete items, and some updated data products (per draft version 0.6) Calibrate, Detect, and Source pipelines Source detection with combined streak map and low freq. backgrounds for ACIS Aperture photometry rates, fluxes, and errors Sensitivity map and spectral fits (initial implementations) Gregory-Loredo, KS, and Kuiper variability and light-curve (source region only) PSF generation running directly on Beowulf using SAOTrace No source extent estimation Initial version of Master pipeline Matches sources across multiple observations to create a single “top-level” catalog entry for each source Creates database transaction files Does not include merge properties computations No quality assurance –Automated Processing (AP) infrastructure to run system in “catch-up” mode –Archive Observation and master source databases Database quantity and archive data product ingestion AP/archive interfaces

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 9 Results from CAT 2.5 Evaluation Progress CAT 2.5 running and providing feedback to science and software teams –Approximately 50 observations processed to develop a baseline Chosen to exercise various aspects of the algorithms, for comparison with existing studies, and to include a range of sources, source distributions, and densities –Additional observations will be run for performance evaluation and to expand the source sample for statistical analysis Science results will be reported by Jonathan later in this presentation Issues Science algorithms –Main issue to be addressed is the high false source rate for some observations Limitations of ACIS readout streak computation for subarrays with few (< 256 ?) rows Reduced statistics results in improper estimate of streak background Investigating use of background variance in wavdetect step, as well as quality assurance flagging to eliminate false sources HRC low frequency background improperly determined Background estimate does not exclude the “bad” outer regions of the detector Expect to resolve on production timescale (not necessarily start of production) HRC-S LESF results in false source detections Need additional mechanism to consider spatial scale for background variability at edge of LESF Do not expect to resolve for release 1; current baseline is to exclude HRC-S

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 10 Results from CAT 2.5 Evaluation (cont.) Issues (continued) Software –Initial integration of pipelines with archive and database took longer than expected Several bugs and performance issues were addressed –Needed several iterations to get source detection working correctly with computed backgrounds Pipeline parameters updated based on analysis of a sample of observations Lack of quality assurance steps required workarounds to eliminate propagation of false source detections (source regions with low net counts and significance) Hardware performance and reliability –Archive test hardware performance issues Will be addressed as part of archive hardware upgrades currently in work (to be installed prior to start of production) –Beowulf cluster hardware reliability The first time all cluster processors were run at a sustained ~100% utilization during CAT 2.5 testing, one node (out of 14) suffered an unrecoverable electrical failure Other nodes occasionally crash unexpectedly, leaving pipelines hanging Performance about a factor ~2 slower than expected Plan to replace existing cluster nodes with new quad-core nodes prior to start of production

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 11 Schedule: Planned Software Releases Planned Software Releases CAT 2.6 (Operational Testbed 2; November 2007) –Pipelines Match Requirements Document version 0.6, with waivers for incomplete items –Calibrate, Detect, and Source pipelines essentially complete Exceptions are some source extent properties and lack of background flare filtering Includes automated pipeline quality assurance Validate processing, detected sources (false source rejection), source properties –Master pipeline mostly complete Most merged source properties Inter-observation variability No quality assurance –Automated Processing infrastructure Support for automated quality assurance Support for “bulk” reprocessing (observation at a time) –Archive Versioning evaluation with reprocessing integration Includes quality assurance/catalog inclusion transactions

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 12 Schedule: Planned Software Releases (cont.) Planned Software Releases (continued) CAT 2.7 (Production Prototype; January 2008) –All pipelines in production configuration Completion of any remaining production liens –Automated Processing infrastructure Mechanism for selective reprocessing (e.g., failed pipelines) Support manual quality assurance –Manual quality assurance GUI Evaluate failed pipelines Evaluate and correct questionable source detections and source matches –Archive Initial user interface GUI Catalog release support (freeze catalog and evaluate catalog inclusion criteria) –Run pre-production test CAT 3.0 (Production Release; May 2008) –Pipelines Fine tune pipelines based on pre-production test –Automated Processing infrastructure Operations interfaces complete; support for daily operations –Archive User interface GUI Hardware configurations complete –Catalog production

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 13 Schedule: Tasks Leading to Catalog Production Tracked Task Summary High level science and software tasks leading to production start –Does not include science characterization tasks which occur in parallel, since they are not a lien against production start ReleaseCompletedWorking Waiting*OpenHold* CAT 2.5 Science 21 CAT 2.5 Software Aug 0736 CAT 2.6 Science 7341 CAT 2.6 Software Nov CAT 2.7 Science 657 CAT 2.7 Software Jan CAT 3.0 Science 635 CAT 3.0 Software May * “Waiting” tasks are in-work but require feedback from CAT 2.5 evaluation to complete “Hold” tasks are suspended (identified as not required for production start)

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 14 Schedule: Risks Schedule Risk Changes Since Last CUC Meeting Processing and/or archive hardware performance is inadequate (Risk  ) –CAT 2.5 testing indicates upgrades required to for aging Beowulf hardware to achieve performance goals Current pipelines include all “compute-intensive” steps, so no further significant performance changes are anticipated Hardware plan being formulated to recover performance, and will be ordered shortly –Database and archive performance evaluation has established requirements for archive hardware upgrades These upgrades have been folded into the overall archive hardware migration plan, and new hardware has been ordered Science algorithm development takes longer than planned (Risk  ) –Development of key algorithms is now completed or well in hand Most are already implemented in CAT 2.5, and will be fine-tuned in future releases –Certain science capabilities will be deferred to avoid impacting release 1 schedule Science algorithms or software are inadequate (Risk  ) –Each software release is followed by a test and evaluation period to identify issues early CAT 2.5 testing indicates that there are some issues to be resolved but no major problems Science characterization of results builds confidence –Pre-production test will evaluate scientific correctness on ~1/3 of the mission data prior to production start

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 15 Schedule: Risks (cont.) Schedule Risks (continued) Software implementation takes longer than planned (Risk  ) –Specifications or partial specifications exists for most tasks, and schedule estimates are fairly reliable for these –Remaining tasks have incorporated best estimates based on available information Establishing catalog operations takes longer than planned (Risk  ) –Plan to provide system documentation and training for the operations group well in advance of pre-production test, and use pre-production test to refine procedures Software and science teams will support operations during transition phase Other tasks compete for resources (Risk  ) –Same science and software resources support live Chandra mission –Some unexpected CXC software development requirements for Cycle 10 have been identified, but we expect these to have limited schedule impact –New archive hardware is not supported under Solaris 8, forcing us to migrate the data system to Solaris 10 by the end of the year –Sybase has announced it will discontinue support for the version of the SQL database server that we are running in December 2007, forcing us to upgrade to a new version Our plan is to combine the migration to Solaris 10 and the Sybase 15 upgrade in order to minimize the resulting schedule impact

CXC Chandra Source Catalog Chandra Users’ Committee Meeting September 19, 2007 Page 16 Schedule: Summary Schedule Continuing to maintain a detailed task list and schedule leading to catalog release 1 –All of the tasks (science and software) that must be done for each software release are expected to be completed in time to avoid delaying that release This is true even for some tasks that are presently lagging –Some tasks have been completed ahead of schedule Several of the schedule risks have decreased since the last CUC meeting, as more of the higher-risk, critical tasks are completed Most concerned about schedule risk associated with competition for available resources –Some unanticipated external factors do require action by the end of this year –Will work to mitigate by reassigning resources and internally shuffling schedule Continue to estimate that all catalog schedule components will complete at about the same time THERE ARE STILL NO LONG POLES Bottom line best estimate is start of production in May 2008, with first public data access in June, and formal release 1 in October