Changes between Version 9 and Version 10 of ScantableRedesignProposal
- Timestamp:
- 08/16/10 11:23:46 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ScantableRedesignProposal
v9 v10 47 47 == Structure == 48 48 49 * add columns in '''MS::WEATHER''' table to '''Scantable::WEATHER, including '''Time'''50 * '''MS''' is time based, so MS->Scantable Filler needs to generate '''WEATHER_ID''' in main table49 * add columns in '''MS::WEATHER''' table to '''Scantable::WEATHER, including '''Time''' 50 * '''MS''' is time based, so MS->Scantable Filler needs to generate '''WEATHER_ID''' in main table 51 51 52 * Add '''ANTENNA''' sub-table to Scantable, referencing in main table keyword.53 * Copy from '''MS'''.54 * MS for single-dish should always be one row only.52 * Add '''ANTENNA''' sub-table to Scantable, referencing in main table keyword. 53 * Copy from '''MS'''. 54 * MS for single-dish should always be one row only. 55 55 56 * add columns from '''MS::SYSCAL''' to '''Scantable::TCAL'''56 * add columns from '''MS::SYSCAL''' to '''Scantable::TCAL''' 57 57 58 * add '''FIELD''' sub-table to '''Scantable''' and move existing '''FIELD''' related columns from main table into it.58 * add '''FIELD''' sub-table to '''Scantable''' and move existing '''FIELD''' related columns from main table into it. 59 59 60 * Add '''OBSERVATION''' sub-table to Scantable, referencing in main table keyword61 * Copy from '''MS'''.62 * should always be one row only.60 * Add '''OBSERVATION''' sub-table to Scantable, referencing in main table keyword 61 * Copy from '''MS'''. 62 * should always be one row only. 63 63 64 * Use '''MS::HISTORY''' in '''Scantable::HISTORY''' (message column)64 * Use '''MS::HISTORY''' in '''Scantable::HISTORY''' (message column) 65 65 66 * Copy '''MS::STATE''' to new sub-table and add '''STATE_ID''' in main Scantable66 * Copy '''MS::STATE''' to new sub-table and add '''STATE_ID''' in main Scantable 67 67 68 * Copy '''MS::POINTING''' table. No referencing in main table. Plain copy68 * Copy '''MS::POINTING''' table. No referencing in main table. Plain copy 69 69 70 * Copy '''MS::POLARIZATION''' table71 * add '''POL_ID'''72 * add {{{getPolType}}} method70 * Copy '''MS::POLARIZATION''' table 71 * add '''POL_ID''' 72 * add {{{getPolType}}} method 73 73 74 * move '''SRCxyz''' columns into new '''SOURCE''' sub-table.75 * add '''SOURCE_ID''' to main table76 * copy '''MS::SOURCE''' columns77 * note that '''RESTFREQUENCY''' etc. are in different sub-tables.78 * not a direct copy from '''MS'''74 * move '''SRCxyz''' columns into new '''SOURCE''' sub-table. 75 * add '''SOURCE_ID''' to main table 76 * copy '''MS::SOURCE''' columns 77 * note that '''RESTFREQUENCY''' etc. are in different sub-tables. 78 * not a direct copy from '''MS''' 79 79 80 * add extra columns from '''MS::SPECTRAL_WINDOW''' to '''Scantable::FREQUENCIES'''81 * note: use '''IF_CONV_CHAIN''' or '''FREQ_GROUP''' as '''IFNO''' equivalent in export to '''MS'''80 * add extra columns from '''MS::SPECTRAL_WINDOW''' to '''Scantable::FREQUENCIES''' 81 * note: use '''IF_CONV_CHAIN''' or '''FREQ_GROUP''' as '''IFNO''' equivalent in export to '''MS''' 82 82 83 83 == API == 84 84 85 * make polarisation handling row-based ('''POL_ID''') and remove hard-coding of feed type etc.85 * make polarisation handling row-based ('''POL_ID''') and remove hard-coding of feed type etc. 86 86 87 * make sure all methods accessing moved/new columns get updated87 * make sure all methods accessing moved/new columns get updated 88 88 89 89