Full implications of ALMA delays unclear, as yet; will proceed as planned for now
CASA release schedule proceeding as normal; ALMA expecting CASA 6.1 for resumed cycle 7
Unclear if ALMA Cycle 8 ambitions increasing from nominal; may be difficult to accommodate given uncertainty in restarting upstream operations (online testing, data gathering, etc.), and subsequent need to inform downstream development.
Connection for this meeting: JIVE Zoom
(Mark) Requirements collation status?
Almost done, Mark will distribute soon
Includes new appendices for completed and low-priority items
(George/Ryan) CASA VLBI Readiness
VLBA and JIVE prioritization of Mark's requirement doc?
Brian Glendenning would like a "credible effort estimate" for UC meeting at end of May(!)
In coming weeks, George will:
Poll VLBA and JIVE for prioritization
Attempt first stab at FTE estimates for BG
Understanding the anticipated JIVE contribution will be very useful!
(Ryan) CNGI Status
CNGI/ngCASA Conceptual Design Review: 2020 Jun 9-10 (Documentation by May 20)
Discussions with ASTRON re casacore, MSv3, etc.? (Ryan: Discussions effectively suspended, for now, but ASTRON aware as of (at least) ADASS19; no changes beyond details.)
George: Role of MSv3 as science data (content) model? (Ryan: CNGI effectively based on MSv2 science content; MSv3 translation possible from ASTRON?)
Pending admin issues
casa6 build issues: formal instructions for plotms, CASAshell, casa5/6 co-exist, c++ unit tests in casa6
New VLBI integration branch?
Bamboo automated builds only for casa6. casa5 available on-demand (George will clarify and report)
Stakeholders exercise is for planning CASA staff work distribution, according to a broad spectrum of requests; does not control JIVE development effort, though JIVE welcome to contribute as a stakeholder
Des: How should EHT contribute as stakeholder?
Tools/processes evolving on confluence/JIRA as CASA 5.8/6.2 planning is settled.
All VLBI-specific efforts to be documented with CASA effort; isolated via "VLBI" and "VLBI@JIVE" JIRA labels. May leverage confluence a bit more in future.