Development Status and Priorities Jeff Kern NRAO.

Slides:



Advertisements
Similar presentations
Extreme Programming Alexander Kanavin Lappeenranta University of Technology.
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Test Automation Success: Choosing the Right People & Process
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
Roadmap to Continuous Integration Testing and Benefits Gowri Selka, Walgreens Natalie Koltun, Walgreens May 20th, 2014 ©2013 Walgreen Co. All rights reserved.
1. Failure is when users do not feel they get what they paid for. 2. Failure is when the overall organization fails to adopt the solution.
Rational Unified Process
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Systems Analysis and Design. Systems Development Life Cycle (SDLC) Systems Analysis Systems Design Programming Testing Conversion On-going maintenance.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Release & Deployment ITIL Version 3
The Integration Story: Rational Quality Manager / Team Foundation Server / Quality Center Introductions This presentation will provide an introduction.
Commissioning the NOAO Data Management System Howard H. Lanning, Rob Seaman, Chris Smith (National Optical Astronomy Observatory, Data Products Program)
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
RUP Fundamentals - Instructor Notes
Model Bank Testing Accelerators “Ready-to-use” test scenarios to reduce effort, time and money.
Agile Web Development C. Daniel Chase University of Colorado at Boulder.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
1 ANASAC Meeting – May 20, 2015 ALMA Pipeline Brian Glendenning (for Jeff Kern)
SPACE TELESCOPE SCIENCE INSTITUTE Operated for NASA by AURA COS Pipeline Language(s) We plan to develop CALCOS using Python and C Another programming language?
McMullinEVLA Advisory Committee Meeting December 14-15, 2004 EVLA Data Post-processing: SSG (AIPS++/CASA) Development J. McMullin.
Usability Issues Documentation J. Apostolakis for Geant4 16 January 2009.
Ocean Observatories Initiative OOI CI Release 3 (Scope To Complete) Kick-Off Tim Ampe: System Development Manager Release 3 Kick-off La Jolla, CA October.
ALMA Integrated Computing Team Coordination & Planning Meeting #2 Santiago, January 2014 Control Group Planning Rafael Hiriart, Control Group Lead.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Atacama Large Millimeter/submillimeter Array Karl G. Jansky Very Large Array Robert C. Byrd Green Bank Telescope Very Long Baseline Array CASA Progress.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
CABB Data Reduction Review Summary of recommendations Dave McConnell June 2011.
Continuous Integration and Code Review: how IT can help Alex Lossent – IT/PES – Version Control Systems 29-Sep st Forum1.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
2007Sep06 EAC Butler - Software Overview 1 Software Overview Bryan Butler.
Observing Modes from a Software viewpoint Robert Lucas and Philippe Salomé (SSR)
1 KFPA Critical Design Review – Fri., Jan. 30, 2009 KFPA Data Pipeline Bob Garwood- NRAO-CV.
Atacama Large Millimeter/submillimeter Array Expanded Very Large Array Robert C. Byrd Green Bank Telescope Very Long Baseline Array Data Processing Progress.
Robustness Initiative Jeff Kern NRAO. CASA Robustness and Reliability Number one priority from the CASA User Survey was reliability. – Survey did not.
CASA Users Survey Response and Progress Jeff Kern NRAO.
CSC 480 Software Engineering Test Planning. Test Cases and Test Plans A test case is an explicit set of instructions designed to detect a particular class.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Thomas Kern | The system documentation as binding agent for and in between internal and external customers April 24th, 2009 | Page 1 The system documentation.
ESO, 17 April 2007ESAC meeting1 ALMA offline User Test 5 Silvia Leurini, ESO.
Managing Challenging Projects Presented to the class of: Dr. Jane Mackay M.J. Neely School of Business.
Atacama Large Millimeter/submillimeter Array Karl G. Jansky Very Large Array Robert C. Byrd Green Bank Telescope Very Long Baseline Array ALMA Pipeline.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Future plans & strategy for CCP4 (for discussion) Tadeusz Skarzynski, 30 March 2006.
T Project Review RoadMappers I2 Iteration
Follow-up to SFT Review (2009/2010) Priorities and Organization for 2011 and 2012.
D. Duellmann, IT-DB POOL Status1 POOL Persistency Framework - Status after a first year of development Dirk Düllmann, IT-DB.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Process changes: Internal processes of CASA, external contributions, release schedule Mark G. Rawlings, CASA Build & Test Lead NRAO, Charlottesville Acknowledgements:
CASA Strategic Plan Subtitle Jeff Kern NRAO. CASA Global Context The CASA strategic plan describes the evolution of CASA over second half of the decade.
Documentation Analysis and Proposal Jeff kern NRAO.
AM10 AUTOMATED TESTING IN DYNAMICS NAV Luc van Vugt, MVP – fluxxus.nl.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
TK2023 Object-Oriented Software Engineering
NRAO-SKA Future Collaboration Meeting
Dinesh Rawat , Software Test Manager
Chapter 18 Maintaining Information Systems
Documentation in Continuous Delivery Model and DevOps
Gustaaf van Moorsel September 9, 2003
Amendment Invoice Task Force Progress Report
Observatory Science Operations
Observatory Science Operations
Amendment Invoice Task Force Progress Report
Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
IT Next – Transformation Program
Presentation transcript:

Development Status and Priorities Jeff Kern NRAO

CASA Interferometry Progress Re-architecting of Clean task implementation to tClean – MT-MFS with mosaics, AW-Projections, parallelization – Available for use, many “nice” features still to be added – Used in ALMA imaging pipeline OTF calibration (cal library) – Supported and well tested in plotMS – Support in tasks implemented, needs to be commissioned – Not yet hooked up to tClean MPI Based parallelization – Fully available and documented for calibration (see talk tomorrow). – Easier integration with most scheduling systems 2015 CASA Users Committee Face to Face2

CASA Interferometry Progress (2) MS Transform – Single location for many similar tasks (deprecating old versions) – Fully MMS aware (parallel where available) Robust statistics algorithms in imstat and ia.statistics – Several algorithms Channel based weights, weight handling defined, and tools for weight manipulation. Linear mosaic (lm) tool to mosaic weighted images – Important for VLASS msuvbin – UV plane accumulation – Designed for CHILES project, allows managing very large data sets 2015 CASA Users Committee Face to Face3

CASA Single Dish Progress MS transition (since 2014 Q4) – All highest priority capabilities, i.e., ones used in standard manual and pipeline data processing of ALMA-TP, have already been implemented. (But the standard data processing of ALMA-TP is still based on ASAP) – 21 out of 58 items are implemented in CASA 4.5 release Support ALMA-TP data processing: manually processed data started to be delivered in Aug Bug fixes and minor enhancements in ASAP to process Cycle 1 and 2 observation data Support of New multi-beam receiver, FOREST, on Nobeyama 45-m – Bug fixes in ASAP to support multi-beam data and enhancements for FOREST – Currently, a dataset should be split by beam for proper imaging CASA Users Committee Face to Face4

CASA Pipeline Progress Successfully supported ALMA Cycle 2 operations. ALMA SD Pipeline acceptance ALMA Imaging Pipeline – Continuum Image – Per SPW continuum subtracted cubes VLA Calibration Pipeline in operations Parallelization – Implemented in pipeline, not yet deployed – See talk tomorrow ALMA-QA0 Flagging Implemented – Additional online flags applied for ALMA 2015 CASA Users Committee Face to Face5 Cycle 2 Pipeline Processing Success w/ Additional Flagging Tweaked SuccessManual

CASA Build and Test Progress Support for OSX 10.9 and Daily automated test versions with automated tests on all four platforms – Stables (those that pass tests) are made available to the community. 89 stable versions available during 4.5 development cycle Integration with github::CASACore project – Unified casacore with rest of community Normalization and standardization of build process across OSX and Linux libsakura integration – High performance vector processor library developed at NAOJ C++11 Support in compilers – Allows removal of custom solutions: container classes, smartpointers MPI Integration 2015 CASA Users Committee Face to Face6

CASA Misses (Things we didn’t do). Updates to FFTW (Done, but to late for 4.5 release) Complete switch of calibration to new IO infrastructure layer – Full scratchless operation in calibration (done, but needs validation) Rewrite of visstat – Scope increase (support Single Dish) and new developer. 4.6 tClean: – Transition to new IO infrastructure (scratchless operation) – Improved image weighting (fixes interpolation issues) – Interactive interface improvements (descoped early) – automasking – Parallelization (Done, but needs validation) 2015 CASA Users Committee Face to Face7

CASA Misses (Things we didn’t do). SetJy – Full reuse of imaging infrasturucture StatWt improvements Enhanced RFI mitigation in RFLAG (requirement mismatch) 2015 CASA Users Committee Face to Face8

CASA Interferometric Priorities Reliability and Stability Initiatives – Testing Enabling and requiring tests at the C++ module level – Technical Debt Continued migration to standard IO routines Namespace cleanup, removal of bespoke code – Obsolete Code Removal of unused or unsupported options Consolidation of routines to use a single pattern for accomplishing the same thing CASA Users Committee Face to Face9

CASA Interferometric Priorities Close out of ongoing initiatives – tClean – Scratchless operation in Calibration, testing and perfecting Some “behind the scenes” changes for maintainability – VisStat Speed, parallelization, and support for large data Robust estimation – Scratchless operation extended to tClean No more applycal? New initiatives: – Performance effort: Particularly looking at low level IO access patterns 2015 CASA Users Committee Face to Face10

CASA Pipeline Priorities ALMA: – Implement antenna outlier amplitude vs time flagging heuristic – ALMA imaging acceptance (and improvement) – HPC in production – Sessions (?) Multiple contiguous executions of the same SB Sharing calibration across exectuions VLA – VLASS specializations (OTF Mosaic support) – Spectral calibration support Both – Low signal to noise ratio heuristics – Polarization calibration – Science Ready Data Products 2015 CASA Users Committee Face to Face11

CASA Single Dish Priorities Complete the MS transition project Aim finishing migration of most of the items by the end of 2016 Support ALMA to start using the new single dish module based on MSes The new single dish module is ready for use for ALMA-TP. Need to update manual reduction scripts and pipeline Support ALMA Cycle 4 TP observations Major new capabilities are fast-scanning observations of the Sun and observations of multiple science targets by an SB Support Nobeyama start using CASA as the primary data reduction software Nobeyama decided to adopt CASA for new backends Preliminary schedule: 2016 Q4 - the observatory test use of CASA, 2017 Q4 - observatory start supporting reduction by CASA 2015 CASA Users Committee Face to Face12

CASA Build and Test Priorities Add support for more Oss – OSX (10.9 going away!) – RHEL 7 – Ubuntu support (MeerKAT?) Resources permitting Transition to Git as version control system for all of CASA – Investigating more integrated tool chain Automation of new tests under development by development team – Introduce and track test coverage metrics Addition of tools to enforce Software Quality initiatives Implementation of framework to support user documentation effort 2015 CASA Users Committee Face to Face13

CASA 2014 CUC Report Recommendations Since speed and ease-of-use are the main laments of CASA users, we recommend to emphasize improvements in performance and parallelization, and to improve the overall robustness of basic operation. The CASA HPC framework is now in place and available for general use. Parallel imaging is implemented and tested in pipeline context but not yet undergone full validation. Scratchless operation is available in calibration, plotMS, and MSTransform, but not yet in imaging. Additional attention to setting user expectations may also help ameliorate these issues, such as (crude) time estimators for critical tasks. This has not yet been addressed, it is on the list of remaining imaging re-architecting tasks CASA Users Committee Face to Face14

CASA 2014 CUC Report Recommendations Complete the CLEAN refactor with high priority, as this will bring important capabilities as well as retire some speed and usability issues. The first version of this is now available in CASA 4.5 Improve and curate better CASA documentation; a small number of well- maintained documents is preferable to many that are not maintained and become out of date. See discussion in talk on documentation Provide updates to CASA users about ongoing and planned developments, as well as prioritized fixes, in a regular and easily digestible form. The first CASA newsletter was published in April, the second is in prepartion and will be out this week or next. Improve feedback to users on helpdesk/ticket disposition, especially where challenging problems may take a long time to address, or will not be addressed. User surveys can uncover problematic issues and help to guide future development; we would like to work with the CASA team to develop and deploy more user surveys. As there always will be a longer wish list of CASA improvements than available re- sources can support, we recommend to engage the external community by stabilizing and documenting interfaces and import/export formats to better enable users to con- tribute and to maintain CASA tasks and scripts. Continue to promote CASA for telescopes other than ALMA and the VLA on a best effort basis; major initiatives formulated by external groups should be undertaken only if the additional resources required are provided CASA Users Committee Face to Face15

CASA 2014 CUC Report Recommendations Improve feedback to users on helpdesk/ticket disposition, especially where challenging problems may take a long time to address, or will not be addressed. We have created a web page to address this, some of the CASA management consultant recommendations are focused on improving determinism for development. User surveys can uncover problematic issues and help to guide future development; we would like to work with the CASA team to develop and deploy more user surveys. First user survey was conducted and a response has been prepared (see upcoming newsletter). Further details in discussion on user survey CASA Users Committee Face to Face16

CASA 2014 CUC Report Recommendations As there always will be a longer wish list of CASA improvements than available resources can support, we recommend to engage the external community by stabilizing and documenting interfaces and import/export formats to better enable users to contribute and to maintain CASA tasks and scripts. We have addressed a number of known issues with the uvfits import/export tasks. Documentation was discussed earlier. The transition to an enterprise Git implementation will allow more dynamic interaction with external developers. Continue to promote CASA for telescopes other than ALMA and the VLA on a best effort basis; major initiatives formulated by external groups should be undertaken only if the additional resources required are provided. Under these auspices we have entered into a collaboration to support the ACA reduction with CASA. We are working to incorporate resources from other observatories in the NRAO helpdesk to assist in the support of CASA CASA Users Committee Face to Face17