Support for casacore as its own namespace is in the home stretch. About 90 files require a final merging with current source files which changed during the modification work. CasaCore mod to allow cmake enable/disable of the feature is in a pull-request. In a day or two it ought to go into the trunk.
(CAS-8837) implement multithreading in ClassicalStatistics::_createDataArrays(). UT. Responded to query that this and other related tickets could be tested together as long as quantile-like values are part of the test plan.
Completed migration to OSX 10.11 on my laptop, then wrestled with the CASA build. Only a few quirks to contend with relative to the wiki instructions, mostly related to the fact that I was updating an existing installation of 3rd party stuff rather than installing them from scratch. Provided some feedback to Ville.
Advised on CAS-8895 (chan-ave'd weights don't look right), which was mostly pilot error in selecting axis options in plotms. Pam added a warning that 'wt' refers explicitly to the unchan'd WEIGHT column, and will plot it (even vs. freq-dep axes) even if there is a non-trivial WEIGHT_SPECTRUM. Next cycle we will move toward serving the weight info with the same shape as data and flags always, to simplify this interface, and deeper application interfaces as well (JIRA ticket pending).
CAS-8893 ('nearest' freq interp wrong) RTT: This turned out to be a re-do of a fix CAS-6995) I did in May 2015 on the v4.4 release branch that never made it back to casacore trunk on the git repo (we were in the midst of migrating to the git repo, and this revision was lost in the shuffle). Asked Jim to expedite a pull request for this, so it can be fixed in v4.7.
CAS-8904 (single-precision time in interpolation defeats ~msec sampling observations). Turns out time (minus a large offset) has been explicitly cast to Float in calibration interpolation because the Interpolate1D class can't handle a Double abscissa when interpolating an Array<Float> ordinate. I think this is mainly because mixed-type operator* (and similar) is not supported in the public interface (or at least the well-used interface) of ArrayMath. I wonder if it is a good idea to support mixed types there or not. For v4.7, we'll finesse the time offset to minimize the problem, and address the deeper ArrayMath fix for v5.0.
Several non-CASA meetings (local sci staff, OSTC), misc. correspondence.
CASA IO testing
visstat2 unit tests on time averaging
Carta OSX packaged from development branch
Still working on Carta build issues on Ubuntu
Plan creation from Jira works, but the plan creation won't cascade. Hence the build plan needs to create a new testing plan at the final stage (no point in creating/running test plan before the initial build is done). The initial test of this seemed to work alright.
Started consolidating Bamboo plans, but based on current workflow and the trigger limitations in Bamboo, those will probably need to be split up again.
Checked in new asteroid models and updated code for setjy
Automask doc - responding some of Amanda's questions
Investigating CAS-8900 the pipeline shows the difference in the flux scaling in setjy (evla) running multiple spws all at once versus running individually.
Friday NAOJ Meeting
discussion on how to test CAS-8419 with Kana and Patricio
bug report on CTTimeInterp1 (conversion time value to single precision)
CAS-7339: double-checked Eiji's verification result. Quasar not visible on imaging result