1 / 14

CLOSING SUMMARY

CLOSING SUMMARY. Nick Elias 2010 May 14. Highlights I. Jürgen’s talk on science priorities: EVLA and ALMA observation modes  daunting! ALMA depends entirely on CASA Growing CASA user community If CASA or ALMA fails, ramifications for the future! Nick’s talk on the roadmap:

elewa
Download Presentation

CLOSING SUMMARY

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CLOSINGSUMMARY Nick Elias 2010 May 14 CASA Developers' Meeting

  2. Highlights I. • Jürgen’s talk on science priorities: • EVLA and ALMA observation modes  daunting! • ALMA depends entirely on CASA • Growing CASA user community • If CASA or ALMA fails, ramifications for the future! • Nick’s talk on the roadmap: • We’ve made progress on concerns, more to go • Requiring design documents • Formalizing closure process  incorporate comments • It will still be represented by a flowchart (sorry) • Discipline, discipline, discipline! CASA Developers' Meeting

  3. Highlights II. • Sanjay’s algorithm talk: • Several new algorithms under development • Current development driven mostly by EVLA, but much overlap with ALMA • R&D needs isolation from main release branches • Kumar’s imaging talk: • Task by accretion  60 parameters • Described functionality of Imager and related classes • Recent history (no scratch columns, etc.) • Future (parallelization, new algorithms, etc.) CASA Developers' Meeting

  4. Highlights III. • George’s calibration talk: • Supported calibration factors, hierarchy • Classes • Future (eliminate plotcal, ALMA polarization calibration, eliminate scratch columns, etc.) • Visualization talks: • dbus (Darrell): How does it work? Features (Qt). • viewer: (Darrell): Architecture description. • plotms: (George): History. Principles. Future. • 3D: viewer  ESO IFUs. Requirements. Synergy. CASA Developers' Meeting

  5. Highlights IV. • Ger’s talk on casacore: • Recent development • Future plans  mostly bug fixing • pyrap • Jonas’ talk on the new build system: • Requirements • Build tool comparisons  Cmake • Improvements (null build times, integrated unit tests, etc.) CASA Developers' Meeting

  6. Highlights V. • Sandra’s test talk: • List of e2e regressions • Description of unit testing system • How to run and monitor tests • Remy’s simulator talk: • CLI • Corruptions/corrections • Classes • Future plans CASA Developers' Meeting

  7. Highlights VI. • Dirk’s talk on exportasdm: • Design document created • Table formats • Features of each version of code • Binding talks: • ccmtools (Darrell): existing, somewhat complicated • boost (Wes): already used by sd tasks • swig (Michel): simple! • Wes wants to investigate boost and swig • Kumar’s VisibilityIterator talk: • Description, hints, etc. CASA Developers' Meeting

  8. Highlights VII. • Takeshi’s talk on sd: • Architecture (tools and tasks) • Recent developments (e.g., fitting, clipping, plotting) • 3.0.2 plans (msmoments) • Jürgen’s demonstration of Livedata and Gridzilla: • Tools for sd observations • Dominique’s and Jean-Christophe’s talk on TELCAL: • Uses ACS • Must process data within 0.5 sec! • Many engines • Filler and calibration from CASA used • SWIG wrappers CASA Developers' Meeting

  9. Highlights VIII. • John’s talk on the pipeline heuristics: • Python • Recipe driven • HTML Output • Future: Real ALMA data, parallelization • Lindsey’s talk on pipeline infrastructure: • Quicklook and science relay on CASA • Visualization, calibration, flagging, imaging • HPC: • parallel_go (Honglin): python level, how to use? • parallel (Kumar): managing memory, disk access, wrappers around parallel_go (line and continuum) CASA Developers' Meeting

  10. Highlights IX. • Process: • Kumar – Regressions (redundant, check points, documentation), research endeavor, better releases • Remy – Communications issues • Takeshi’s talk on sd data format: • Update scantable or go to ms • We have the info, a bit more discussion, then come up with plan and assign/schedule tickets • Wait for Iono-san? • Honglin’s talk on boxes: • Wow! • Nick’s talk on the release process: • A few OK ideas (e.g., unit tests), needs more work CASA Developers' Meeting

  11. Release Process • “Ready for test”: can go from active to test after passes unit tests and Wes’ regressions • Scratch and R&D branches? • Check breakpoints for regression tests • Must encourage communications among developers, users, testers, etc. • Need to track regression failures • Must make time for long term planning • We have begun with viewer, HPC, and boxes • How can we effectively use Friday afternoon meetings? • E.g., scratch columns, viewer, etc. • Discipline, discipline, discipline! CASA Developers' Meeting

  12. Important Miscellany • Pictures are contained in *.tar.gz files and may be found on the meeting page • If you have additional pictures, please send them to me as well • Comments for communiqué please! • We have a new logo, thanks to Jürgen CASA Developers' Meeting

  13. No Rest for the Weary • The feature freeze starts now • Except for splitting cross hands • Juergen: Coordinate with workshop personnel • Everyone: Regressions started failing • Change of interpolation method? • How to coordinate fixing the regressions? • Discipline, discipline, discipline! • Patch release due o/a June 1 • We may see absolute last minute bugs  be ready! CASA Developers' Meeting

  14. Thanks! CASA Developers' Meeting

More Related