Monday Morning Meeting 10/1/18

  • DIAL-IN NUMBERS & PASSCODES:
  • IP: 192.33.117.12##8110
  • Phone: (434) 817-6524

Attendance

  • Socorro:
  • CV:
  • Garching:
  • SCO:

News / Meetings / Visitors

  • CASA Architect offer declined
  • CASA SW Engineer interviews continuing
  • Upcoming CUC meeting in SO 10/25 - 10/26
  • Upcoming Pipeline developers meeting in SO 10/29 - 11/2
  • Upcoming ICT leads meeting in SO 11/6 - 11/8

Development

  • CASA 5.5 Confluence page
    • Organizing tclean development plan now
    • Need plan for VI/VB2 and MSTransform
    • TBD: add other miscellaneous items

  • CASA tasks always do a fullgarbage collection "gc.collect()" at the end. This is inserted by the casa2pycli.xsl casa2pypg.xsl etc. stylesheets/templates.
    • Does anyone know the history of this? It was introduced Jan 2012: https://svn.cv.nrao.edu/view/casa/trunk/gcwrap/install/casa2pycli.xsl?r1=6662&r2=6947
    • It runs a full collection, including gen2 (long-lived objects), which can be very expensive. It interferes with the Python GC heuristics.
    • Was this introduced to address old issues like old leaky behavior of CASA and/or ancient Python versions?
    • For the pipeline it can cause delays of 10s of seconds or minutes for every task call: CAS-11578, CAS-11690 - serious performance degradation when a CASA-based application does many quick task executions, with lots of blobs of Python objects around (Pipeline context, results, etc.).
    • Unless there is a good reason to keep this:
      • I think it should not be carried over to CASA 6.
        • This is not a feature of CASA 6
      • I'd experiment with removing it now (CASA 5.5).

Pipeline

Users

  • CASA Newsletter: deadline for contributions today (+- 2 days). If you have items for the CASA calendar (workshops, meetings, etc), please send them to me by Wednesday.
  • CASA Docs development server will be for CASA 5.5, not CASA 5.4.1. For documentation that needs to go in CASA 5.4.1: please put info in CASA Docs devel, then email me what should be copied into 5.4.1.
  • CASA User Survey: 100 completed replies. Interesting detail: majority of users that completed the survey use Ubuntu (see attachment). Article on survey results + helpdesk ticket statistics in CASA Newsletter, full memo is in prep.

Build, Release

Verification Testing

Validation Testing

CASA 6

  • added configure check to abort if C++ compiler does not support C++11 STL features
  • added configure check for GSL version, along with search of complete $PATH
  • worked on creating a python package closure for publishing binary packages to local PyPi repository

CARTA

Developer Reports

Monday Meeting
  • Sandra Castro
  • Kana Sugimoto
  • Bjorn Emonts
  • Pam Ford
  • Enrique Garcia
  • Bob Garwood
  • Kumar Golap
  • David Mehringer
  • George Moellenbrock
  • Dirk Petry
  • Federico M Pouzols
  • Darrell Schiebel
  • Ville Suoranta
  • Neal Schweighart
  • Takahiro Tsutsumi
Friday NAOJ Meeting (9/27/18)
  • Wataru Kawasaki
  • Takeshi Nakazato
    • additional validation on CAS-11501 and gave a feedback to the ticket
    • preliminary workload estimate and ticket assignment for 5.5
  • Renaud Miel
    • NTR, Off last week
  • Suminori Nishie
    • CAS-11427 Unit Test (UT) for PointingDirectionCalculator
      • Source review: significant promlem were fixed, Introdced smart_pointer for no memory-leak.
      • Source code refactoering: removing redundnt statement / rename variables / comments update / edited spacing etc.
    • Started reading documents for 5.5.
      • Reviewing mathematical interporation (esp. spline)
    • Near future
      • Started reviewing (Intel) Asembler. (VAX->8086->IA-32(486)->x64) and the latest technology (i.e SIMD).

-- TakeshiNakazato - 2018-09-25

Topic attachments
I Attachment Action Size Date Who Comment
Survey_OS.pngpng Survey_OS.png manage 21 K 2018-10-01 - 07:53 BjornEmonts  
This topic: Software/CASA > Software > WebHome > CASAMeetingPage > Oct0118
Topic revision: 2018-10-01, DarrellSchiebel
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback