1. December 16, 2002 1 NOAO Mosaic Pipeline CoDR NOAO Mosaic Pipeline Technical Presentation

2. December 16, 2002NOAO Mosaic Pipeline CoDR2 Outline of Technical Presentation Introduction Contexts Capabilities Architecture Implementation

3. December 16, 2002NOAO Mosaic Pipeline CoDR3 Presentation Goals Convince you that: we understand the –problem –requirements –resources –components and that the project –is feasible –has a solution for the primary application –has a flexible design for expansion and wider application

4. December 16, 2002NOAO Mosaic Pipeline CoDR4 Guiding Principles Modest project Part of Data Products Program (NOAO) Mosaic Imaging Data Dedicated pipeline

5. December 16, 2002NOAO Mosaic Pipeline CoDR5 Principles: Modest Project Reuse as much software as possible Keep it simple software

6. December 16, 2002NOAO Mosaic Pipeline CoDR6 Principles: DPP MDHS: Mosaic Data Handling System IRAF: Image Reduction and Analysis Facility NSA: NOAO Science Archive DTS: Data Transport System OPUS: AURA sister institution (STScI) GONG: AURA sister institution (NSO)

7. December 16, 2002NOAO Mosaic Pipeline CoDR7 Principles: (NOAO) Mosaic Data Use experience of Mosaic Survey Teams Need to deal with specific peculiarities –Crosstalk, pupil reflections Allow for high performance per exposure (for real-time telescope context) by capitalizing on the inherent data parallel nature of mosaic imaging data

8. December 16, 2002NOAO Mosaic Pipeline CoDR8 Principles: Dedicated Pipeline Network of similar computers No competition with general users

9. December 16, 2002NOAO Mosaic Pipeline CoDR9 What does this project encompass? Pipeline infrastructure CCD mosaic data reduction Data quality assessment Image differencing Catalog production Database entry and querying Source merging/classification Archive ingest and retrieval Alerts Monitoring Data transport High performance computing Parallel computing More … Algorithms, interfaces, and software for:

10. December 16, 2002 10 NOAO Mosaic Pipeline CoDR Contexts In what contexts will the pipeline run? Can we design a pipeline to satisfy multiple contexts?

11. December 16, 2002NOAO Mosaic Pipeline CoDR11 Contexts NOAO –Telescope/operational context –Archive/NVO context Community –NOAO Mosaic surveys and observers –Other mosaic instruments

12. December 16, 2002NOAO Mosaic Pipeline CoDR12 Priorities 1.NOAO Archive 2.NOAO Mosaic observers −telescope −downtown −home institution 3.NOAO Mosaic observers at home 4.Community

13. December 16, 2002NOAO Mosaic Pipeline CoDR13 NOAO Contexts Downtown center fed from telescope Mountain at telescope Archive on-the-fly reprocessing

14. December 16, 2002NOAO Mosaic Pipeline CoDR14 Pipeline Locations Pipeline Locations La Serena Archive Tucson Archive Kitt Peak Cerro Tololo Pipeline

15. December 16, 2002NOAO Mosaic Pipeline CoDR15 Context: Downtown Pipeline Observer DCA Data Spool and Transport Pipeline DSC User @ telescope, downtown, home Archive DTS

16. December 16, 2002NOAO Mosaic Pipeline CoDR16 Context: Mountain Pipeline DCA Data Spool and Transport Pipeline User @ telescope Archive DTS

17. December 16, 2002NOAO Mosaic Pipeline CoDR17 Context: Archive Pipeline User @ home Pipeline Archive DTS

18. December 16, 2002NOAO Mosaic Pipeline CoDR18 Context: User Pipeline User @ home Pipeline @ home More

19. December 16, 2002NOAO Mosaic Pipeline CoDR19 Proposed Context Downtown pipeline for NOAO archive Observer may subscribe to data products –At telescope, downtown, home –Images, catalogs, alerts, … Observer may connect to DQ monitors Pipeline software available at telescope with minimal support DQ task/monitors may run at telescope

20. December 16, 2002NOAO Mosaic Pipeline CoDR20 Observing Protocols Certain observing protocols may be imposed. Bias sequence Dome flat field sequence Gain sequence –Dome flat fields at different exposures in 1 filter Standard fields for astrometry, photometry, crosstalk

21. December 16, 2002NOAO Mosaic Pipeline CoDR21 Data Requirements The pipeline design is dependent on the information available about the input data. Basically we require data with the current NOAO Mosaic readout format that includes: –identification of exposure type (object, etc) –description of regions (data, overscan) –an approximate world coordinate system

22. December 16, 2002NOAO Mosaic Pipeline CoDR22 Data Requirements There may be additional information that the pipeline will use if present. Associations: type, ID, total and index SEQUENCE = ‘zero2002-12-16T043244.20.3’ SEQUENCE = ‘dither2002-12-16T043244.5.2’ If not present heuristics will be used based on a requirement that data enters in time order

23. December 16, 2002NOAO Mosaic Pipeline CoDR23 Context: Downtown Pipeline Data Transport System: Fitzpatrick and Seaman Spool DCADQA DTS Daemon (n) DTS Daemon (n) DTS Daemon (n) DRA (n) DRA (n) Pipeline DSC DQA User Archive

24. December 16, 2002NOAO Mosaic Pipeline CoDR24 Context: Mountain Pipeline Data Transport System: Fitzpatrick and Seaman Spool DCADQA DTS Daemon (n) DTS Daemon (n) DTS Daemon (n) DRA (n) DRA (n) Pipeline DRA (n) DQA User Archive DTS Daemon (n) DRA (n)

25. December 16, 2002NOAO Mosaic Pipeline CoDR25 Context: Archive Pipeline Data Transport System: Fitzpatrick and Seaman User DTS Daemon (n) DRA (n) DRA (n) Pipeline DQA Archive DTS Daemon (n) DQA

26. December 16, 2002NOAO Mosaic Pipeline CoDR26 Pipeline Data Directory Trigger Directory Module obj123.fitsobj123.trig GO File Triggers May contain information such as output path Data Trigger (DRA, user, or pipeline module) Tape Disk DTS Process

27. December 16, 2002NOAO Mosaic Pipeline CoDR27 Capabilities Capabilities Major Features and Goals Data Products –Basic –Advanced Data Quality Assessment Instrumental Calibration

28. December 16, 2002NOAO Mosaic Pipeline CoDR28 Capabilities Calibrate mosaic exposures Update instrumental calibrations Identify potential bad data (data quality assessment) Monitor trends and maintain database Stack dither sets Catalog and classify objects and artifacts Get and subtract reference image and detect sources Identify interesting sources Automatically provide data products to subscribers Keep up with observing given sufficient CPU resources

29. December 16, 2002NOAO Mosaic Pipeline CoDR29 Major Features and Goals Data products for NOAO archive and NVO node Data products for observers (by subscription) Pipeline for NOAO and mosaic community Basic CCD mosaic calibrations Advanced time-domain data products Real-time data quality assessment and monitoring High performance, data parallel system LSST testbed Fairly generic pipeline infrastructure (NEWFIRM, …) Automated operation Thorough processing history and data documentation

30. December 16, 2002NOAO Mosaic Pipeline CoDR30 Data Products: Basic Instrument calibrated mosaic exposures Rough photometric zero point Astrometric calibrations Data quality evaluations Updated calibrations Bad pixel, saturated, bleed trail masks Object catalogs Object masks Observing logs Processing information –logs –graphs

31. December 16, 2002NOAO Mosaic Pipeline CoDR31 Data Products: Advanced Dither stacks Exposure masks Field Catalogs Difference image detections –Relative to dither stack –Relative to archive or catalog reference Light curves Variable object detections Unusual object alerts Moving object trajectories

32. December 16, 2002NOAO Mosaic Pipeline CoDR32 Data Quality Assessment I nstrument Telemetry Crosstalk Overscan Bias, flat Noise Focus / Distortions Sky Seeing (PSF) Sky brightness Approx. zero point Twilight Moon up / distance Data quality measures are monitored against preset and user limits as well as adaptive time series limits. Some quantities include mean, sigma, and spatial variations.

33. December 16, 2002NOAO Mosaic Pipeline CoDR33 Instrumental Calibrations Crosstalk [1] CCD defects [2,4,5] Saturated pixels [2,4,5] Bleed trails [2,4,5] Cosmic rays [2,4,5] WCS update [3] 1.Requires image data from full mosaic (non-parallel) 2.Each image element independent of others (parallel) 3.Global calculation on measurements images (parallel and non-parallel) 4.Interpolate in data 5.Flag in mask Overscan [2] Bias [2] Flat field [2] Pupil pattern [3] Fringing [3] Approx. zero point [3]

34. December 16, 2002NOAO Mosaic Pipeline CoDR34 Instrumental Calibrations Two-pass calibration for telescope context: 1.Nighttime pass for immediate and nearly complete calibrated exposures 2.Daytime pass for calibration update from the full night’s data set

35. December 16, 2002NOAO Mosaic Pipeline CoDR35 Nighttime Pass Perform standard CCD calibrations: –Use afternoon master bias –Use most recent flat field Apply pupil and fringe correction –Use most recent pupil and fringe templates Apply global coordinate calibration

36. December 16, 2002NOAO Mosaic Pipeline CoDR36 Daytime Pass Determine if night’s data is suitable for deriving updates to library calibrations Derive new pupil, fringe, and sky flat calibrations Evaluate changes and significance of new calibrations Update library calibrations for next night Update night’s exposures with new calibrations Combine afternoon biases into new master bias Combine afternoon dome flats if no library flat

37. December 16, 2002NOAO Mosaic Pipeline CoDR37 Other Contexts For archive data will either already have best calibration from library or will be derived by requesting raw data for night At home or in the community raw data will be queued as at telescope Documentation and support (data ingest applications) will be provided

38. December 16, 2002NOAO Mosaic Pipeline CoDR38 Data Products Subscription Capability of the DPP system –Not necessarily specific to the pipeline but requires interfacing with DTS Allows external software to request notification of new data products Allows flexibility and broader access –Has implications for the pipeline context

39. December 16, 2002NOAO Mosaic Pipeline CoDR39 Architecture What is a pipeline? Mosaic Pipeline Architecture Concept Pipeline Components –Controls and Monitors –Modules –Calibrations and Database (Rafael Hiriart) –Archive (Robyn Allsman)

40. December 16, 2002NOAO Mosaic Pipeline CoDR40 What is a Pipeline? System to transform input data to output data Automated Composed of processing steps (modules) Steps connected by rules (triggers) Provides monitoring and alerts Error tolerant (continue with next input data)

41. December 16, 2002NOAO Mosaic Pipeline CoDR41 Mosaic Pipeline Architecture Concept Multiple CPUs but no dependency on N Multiple types of sub-pipelines by function –One for operations over all mosaic elements –One for operations on individual elements –One for cataloging –One for image differencing All types on all CPUs: no master! Sub-pipelines triggered by files

42. December 16, 2002NOAO Mosaic Pipeline CoDR42 All CPUs with identical pipeline software, possibly on common NFS disk Assign work by minimum data backlog Transfer data to local CPU disk: not NFS! –Optimize by modules writing to next trigger directory Controls connected to operator console Monitors viewed via network by multiple parties Mosaic Pipeline Architecture Concept

43. December 16, 2002NOAO Mosaic Pipeline CoDR43 Network of Sub-pipelines and CPUs Pipeline CPU MEF SIF MEF SIF MEF CPU SIF MEF SIF MEF SIF MEF: pipeline for operations over all mosaic extensions; eg crosstalk, global WCS correction SIF: pipeline for single CCD images; eg ccdproc, masking

44. December 16, 2002NOAO Mosaic Pipeline CoDR44 Data Flow Concept Last module in one pipeline writes output directly to the data directories of the host for next pipeline, with the host selected by having the minimum number of waiting data files.

45. December 16, 2002NOAO Mosaic Pipeline CoDR45 Data Flow Algorithm Search list of potential hosts: –Check if host is up –Check number of trigger files –Assign output filename to data directory of host with least number of data files –Network filenames are used: (eg. host!directory/filename Module runs and writes output files

46. December 16, 2002NOAO Mosaic Pipeline CoDR46 Data Flow Networking Use a daemon automatically spawned the first time data is transferred to a host Daemon provides portability across platforms; eg. Unix and VMS

47. December 16, 2002NOAO Mosaic Pipeline CoDR47 Data Flow Networking: Example Crosstalk input is Obj123.fits with 2 extensions Output names are generated from Host.dat: –Host1 has two waiting files, Host2 has one, Host3 is down, Host4 has none –Host2!Obj123.1, Host4!Obj123.2 Crosstalk module runs and writes output files directly to the hosts There are no extra network copy or splitting steps

48. December 16, 2002NOAO Mosaic Pipeline CoDR48 Data Flow Networking: Example Host0: Crosstalk Host1: Obj456.1 Obj321.2 Host2: Obj567.2 Host3: Obj123 Obj123.2 Obj123.1 Host3!Obj123.1 Host2!Obj123.2 Host4: DOWN

49. December 16, 2002NOAO Mosaic Pipeline CoDR49 Pipeline Components Data Source (DTS, user) Pipeline Controls & Monitors Calibrations & Databases Data Sink (DTS, user) raw data products Module

50. December 16, 2002NOAO Mosaic Pipeline CoDR50 Pipeline Modules Pipeline Modules Pipeline Module CLSHAPICSH

51. December 16, 2002NOAO Mosaic Pipeline CoDR51 Data Parallel Modules Some algorithms may need to be (re-)implemented specifically for a data parallel pipeline. One type is where measurements are made across the mosaic for a global calibration. Rather than requiring all pieces to be in one pipeline arrange for measurements made in parallel to be collected for the global calibration and then apply the global calibration to the pieces in parallel.

52. December 16, 2002NOAO Mosaic Pipeline CoDR52 Data Parallel Modules WCS Example Catalog objects in each CCD in parallel Bring catalogs (not images) together –Only need x/y coordinates of brighter stars Match sources to ref. catalog (eg. USNO) Compute global correction ( shift, scale, etc.) Return correction coefficients to parallel pipelines to be applied to each CCD Cataloging and correction stages can be separated and run asynchronously with other stages

53. December 16, 2002NOAO Mosaic Pipeline CoDR53 Data Parallel Modules Fringe/Pupil Example Determine best global scaling of pupil and fringe templates to each exposure and then subtract scaled template –Compute statistics over each CCD in parallel –Combine statistics to get global scale factor –Subtract template with global scale from each CCD in parallel

54. December 16, 2002NOAO Mosaic Pipeline CoDR54 Pipeline Triggers Files:trigger on appearance of files Flags:trigger on particular set of flags Timers:trigger at times or intervals File contents:trigger on keywords, etc Messages:trigger on messages Resources:trigger on resources May be more but one type can mimic others

55. December 16, 2002NOAO Mosaic Pipeline CoDR55 Pipeline Triggers File triggers useful for initiating a pipeline Flag triggers useful within a pipeline to communicate success of previous steps Flag triggers also useful for waiting for completion of parallel steps Timer triggers useful in telescope pipeline for performing different daytime/nighttime steps

56. December 16, 2002NOAO Mosaic Pipeline CoDR56 Pipeline Data Directory Trigger Directory Module obj123.fitsobj123.trig GO File Triggers May contain information such as output path More

57. December 16, 2002NOAO Mosaic Pipeline CoDR57 Pipeline Trigger Directory Data Directory obj123a.trigobj123b.trigobj123c.trigobj123a.fitsobj123b.fitsobj123c.fits -- -- d -- -- -- d d -- -- d d d -- dddddddd obj123d.fitsobj123d.trig Module GO Flag Triggers and Merging Module GO

58. December 16, 2002NOAO Mosaic Pipeline CoDR58 Timer Triggers and Two-Passes Nighttime pipeline runs and leaves data in starting directory for daytime pipeline Daytime pipeline is triggered at end of night by timer

59. December 16, 2002NOAO Mosaic Pipeline CoDR59 Controls & Monitors Pipeline Process Manager Obs. Manager Status Monitor Keyword Monitor Module To Database

60. December 16, 2002NOAO Mosaic Pipeline CoDR60 Pipeline Data Directory Trigger Directory Module obj123.fitsobj123.trig GO File Triggers May contain information such as output path Data Trigger (DRA, user, or pipeline module) Tape Disk DTS Process

61. December 16, 2002NOAO Mosaic Pipeline CoDR61 Data Manager Interacts with the pipeline, operator, and potentially other parts of the system such as archives or external applications Record –New calibrations from pipeline or operator –New parameters from operator –Processing information from pipeline Responds to queries for –Calibrations –Parameters –Processing history –Documentation and reports for data products

62. December 16, 2002NOAO Mosaic Pipeline CoDR62 Data Manager Architecture

63. December 16, 2002NOAO Mosaic Pipeline CoDR63 What do we want to store in the database?

64. December 16, 2002NOAO Mosaic Pipeline CoDR64 Where is Data Manager?

65. December 16, 2002NOAO Mosaic Pipeline CoDR65 Calibrations The Data Manager responds to requests from pipeline for current calibration for a particular date, filter, etc. Updates calibrations produced by pipeline (or externally) for a particular date, filter, etc. Calibration updates may require operator confirmation. Calibrations include –Biases and flat fields –Pupil and fringe templates –Standard star data –Astrometry coordinates Some queries are satisfied through secondary queries to other databases such as USNO, GSC2, Landolt, etc.

66. December 16, 2002NOAO Mosaic Pipeline CoDR66 Parameters Responds to requests from pipeline for current parameters for –Pipeline module –Observation date, filter, exposure type, etc. –Position on sky Updates parameters supplied by operator

67. December 16, 2002NOAO Mosaic Pipeline CoDR67 Processing Information All information produced by the pipeline is recorded (keyed by a data identifier). This includes all the information provided to the keyword monitor as well as other data processing sources (logs, graphics, etc.) Pipeline requests processing information for a pipeline execution packaged as an associated data product for the archive. The operator can query processing information for diagnostic purposes.

68. December 16, 2002NOAO Mosaic Pipeline CoDR68 Reports Produces reports for a particular data product Documentation is created from processing information according to some template and desired format (eg xml, html)

69. December 16, 2002NOAO Mosaic Pipeline CoDR69 Pipeline/Archive Ingest Interface Desirable traits –Independence of database semantics –Use of self-describing data description standards –Hiding data’s physical location

70. December 16, 2002NOAO Mosaic Pipeline CoDR70 Archive Ingest Who, What, Where Authority Payload Data Receiving Agent Data Store Archive Ingest Manager

71. December 16, 2002 71 NOAO Mosaic Pipeline CoDR Strawman Implementation

72. December 16, 2002NOAO Mosaic Pipeline CoDR72 Things We Looked At / Aware Of Macho pipeline SM/SN pipeline Sloan pipeline Pan-Starrs: IMCAT, Vista IRAF: Core, IMRED pipelines, STSDAS, PYRAF, etc MIDAS: Mosaic Imager Data Archive System Linda and descendants Elixar (CFH), Terapix (CFH), Subaru, ESO WFI, INT WFI Condor / PVM / NOAO message bus Opus pipelines: HST. MSSO, GONG Databases: MySQL, Postgres

73. December 16, 2002NOAO Mosaic Pipeline CoDR73 Software and Systems (Blue Ribbon) OPUS IRAF System –CLSH (enhanced), KI, OBM/GUI IRAF Tasks –MSCRED, ACE SM/SN Alard/Lupton Algorithm POSTGRES DTS NSA

74. December 16, 2002NOAO Mosaic Pipeline CoDR74 Software and Systems (Honorable Mention) PVM Condor Other scripting languages and systems –PYRAF and Python –Perl –MLCL

75. December 16, 2002NOAO Mosaic Pipeline CoDR75 Pipeline Modules Pipeline Module CLSHOAPICSH MSCRED, etc

76. December 16, 2002NOAO Mosaic Pipeline CoDR76 Controls & Monitors Pipeline Process Manager Obs. Manager Status Monitor Keyword Monitor Opus IRAF GUI Opus Module

77. December 16, 2002NOAO Mosaic Pipeline CoDR77 Switchboard Server CPU Pipeline Module Pipeline Module CPU Pipeline Module Pipeline Module Switchboard Server Backup Keyword Monitor Status Monitor Database Manager Other types Or instances Switchboard address set by environment variable

78. December 16, 2002NOAO Mosaic Pipeline CoDR78 Triggers OPUS provides: Files: trigger on appearance of files –Data entry pipeline initiation Flags: trigger on “blackboard” flags –Internal sequencing of modules –Parallel to Global sequencing Timers: trigger at certain times or intervals –Nighttime/Daytime Two-Pass Control

79. December 16, 2002NOAO Mosaic Pipeline CoDR79 Monitoring IRAF Tasks IRAF tasks, including scripts, will open a messaging connection and write status and monitor information Minimal changes will be required to tasks If a server is not running or disappears the tasks will continue to run with output spooled locally

80. December 16, 2002NOAO Mosaic Pipeline CoDR80 Monitoring IRAF Tasks Initially the broadcasting will be a socket connection with a server that multiple clients may connect to for rebroadcast The monitor tasks are IRAF GUI tasks which provide flexibility for changes to the GUI or functionality

81. December 16, 2002NOAO Mosaic Pipeline CoDR81 Monitoring IRAF Tasks The GUI monitors will include: –Adaptive alarms –Adaptive heartbeat monitoring –Advanced graphics

82. December 16, 2002NOAO Mosaic Pipeline CoDR82 IRAF Keyword Monitor Prototype

83. December 16, 2002NOAO Mosaic Pipeline CoDR83 IRAF Keyword Monitor Prototype

84. December 16, 2002NOAO Mosaic Pipeline CoDR84 IRAF Status Monitor Prototype

85. December 16, 2002NOAO Mosaic Pipeline CoDR85 NOAO Mosaic Pipeline Development Plan 1.Basic Calibration Pipeline 2.Advanced Time-Domain Pipeline

86. December 16, 2002NOAO Mosaic Pipeline CoDR86 1. Basic Calibration Pipeline Basic single exposure calibrations Data quality assessment and monitoring High-performance pipeline infrastructure Simple data transport system Connection to the NOAO Science Archive

87. December 16, 2002NOAO Mosaic Pipeline CoDR87 2. Advanced Time-Domain Pipeline Catalogs Image difference detections Multiple detection ident. and merging Time series Alerts Archiving of new data products

88. December 16, 2002NOAO Mosaic Pipeline CoDR88 Timeline Targets Test version of basic calibration pipeline –July 2003 Operational –September 2003 Test version of time-domain pipeline –July 2004 Operational –September 2004

89. December 16, 2002NOAO Mosaic Pipeline CoDR89 Work Breakdown Pipeline Monitors Data Manager Input and Output Data Products Archive

90. December 16, 2002NOAO Mosaic Pipeline CoDR90 Pipeline –Define methods for running IRAF tasks in OPUS Parameters Error handling I/O –Define and verify data flow balancing method –Define, develop, and implement DQ methods –Develop data parallel algorithm steps for WCS Fringe/pupil removal –Develop data parallel OPUS architecture –Setup development system of at least two machines Work Breakdown

91. December 16, 2002NOAO Mosaic Pipeline CoDR91 Monitors –Develop status monitor Experiment with different GUI formats –Develop keyword monitor Experiment with different GUI formats –Develop switchboard server Work Breakdown

92. December 16, 2002NOAO Mosaic Pipeline CoDR92 Work Breakdown Data Manager –Define interfaces Pipeline DBMS NVO/web services External clients –Define database structures –Define archive data products –Design processing reports –Design calibration library storage and methods –Design and implement manager application Include GUI monitor and operator interface –Install and configure DBMS

93. December 16, 2002NOAO Mosaic Pipeline CoDR93 Input and Output Services –Contribute to DTS –Implement interim data transport, staging, and queuing Work Breakdown

94. December 16, 2002NOAO Mosaic Pipeline CoDR94 Archive –Contribute to NSA development of automatic ingest –Adjust data product specification to include NSA requirements Work Breakdown

95. December 16, 2002NOAO Mosaic Pipeline CoDR95 Specify Data Products –File types –Headers –Documentation Work Breakdown

96. December 16, 2002NOAO Mosaic Pipeline CoDR96 Implementation Plan It is important to deliver core functionality quickly Some technologies are new (to the development team) Delivery timeframe is short

97. December 16, 2002NOAO Mosaic Pipeline CoDR97 Management Plan Key elements of the management plan are: Management/staffing Work Breakdown [covered by FV] Schedule Risk Management

98. December 16, 2002NOAO Mosaic Pipeline CoDR98 Personnel Staff Member Role Alloca tion Responsibilities Dick ShawProject Manager5% Schedule development, resource planning Frank ValdesTeam Lead40% Allocation of work, tracking technical progress, lead designer, documentation Chris SmithProject Scientist10% Definition of requirements, use cases, verification & validation, documentation Rafael HiriartS/W Engineer25% Database & infrastructure design & development, use case development Robyn AllsmanS/W Sys. Eng.5% Archive interface definition, archive system updates, data storage planning, consultant F. PierfedericiScientific Progr.30% Implementation, testing TBD (U. MD)S/W Engineer50% Implementation, testing

99. December 16, 2002NOAO Mosaic Pipeline CoDR99 Staffing Profile

100. December 16, 2002NOAO Mosaic Pipeline CoDR100

101. December 16, 2002NOAO Mosaic Pipeline CoDR101 Risk Management Heavily matrixed staff –New staff will also off-load other work from team lead Staff distributed across continents & institutions –Project leadership remains in Tucson –Extended visits by new remote staff –Weekly videoconferences New staff has limited experience in problem domain –Project leader to work closely with new staff Use of new/third-party software –Make effective use of expertise from external partners