| | 20 | |
| | 21 | (tentative) |
| | 22 | |
| | 23 | * Day 1: Overview |
| | 24 | planning sessions for the rest of the meeting to set goals |
| | 25 | |
| | 26 | * Day 2 - ?: ASAP merge (alma branch -> trunk of ATNF ASAP svn) "working session(s)" |
| | 27 | - Starting point would be alma branch updated recently by Kana |
| | 28 | - include few more updates from CASA |
| | 29 | - Resolve any conflicts, duplicated features, etc |
| | 30 | - (move ASAP logger to CASA C++ logger?) |
| | 31 | - Documentation (including scantable format description) |
| | 32 | |
| | 33 | |
| | 34 | [Following sessions will be scheduled on ~last half of the second week] |
| | 35 | |
| | 36 | * Discussions(1): near term (~1yr?) ASAP coordination |
| | 37 | - Future merge (alma branch->trunk) planning - how often? procedures |
| | 38 | - consideration: release schedules of each packages |
| | 39 | - Development plans (for CASA, CASS?) |
| | 40 | - fillers? |
| | 41 | - plotter |
| | 42 | - flagging |
| | 43 | - baseline fit improvement |
| | 44 | |
| | 45 | * Discussions(2): long term plan |
| | 46 | - Possibility to unify ASAP - CASA as a single package to use for CASS/ALMA/.. |
| | 47 | - Build issues? |
| | 48 | - (supporting OSes) |
| | 49 | - Scantable vs Measurement Set ("kick-off" discussion) |
| | 50 | - Current usages of scantable |
| | 51 | - Requirements for CASS/CASA |
| | 52 | - Measurement Set def. 2.0 |
| | 53 | - Is it sufficient to store single dish data from relevant telescopes (AT's, ALMA), do we need to modify? |
| | 54 | - What modifications are needed for scantable to MS migration? |
| | 55 | - Others |
| | 56 | |
