| | 1 | = Scantable Redesign Proposal = |
| | 2 | |
| | 3 | == Summary == |
| | 4 | |
| | 5 | The current Scantable schema is biased towards rpfits style data (or the structure of {{{atnf/PKSIO/PKSrecord.h}}}). Using the PKSreader and the current Scantable format a lot of metadata from the !MeasurementSets get lost. This proposal tries to rectify this without as major impact on the current use of the Scantable. |
| | 6 | |
| | 7 | The proposal in summary: |
| | 8 | |
| | 9 | * Keep Scantable as the asap internal format |
| | 10 | * extend the schema to include all relevant (meta)data in the !MeasurementSet (MS) |
| | 11 | * implement a direct MS->Scantable Filler avoiding (meta)data loss by going through the PKSreader |
| | 12 | * use MS as the persistent asap storage container |
| | 13 | * implement a direct Scantable->MS Writer avoiding (meta)data loss by going through the PKSwriter |
| | 14 | |
| | 15 | optional performance/usability changes: |
| | 16 | |
| | 17 | * implement a direct ASDM->Scantable Filler (performance) |
| | 18 | * implement an upgrade task for the old Scantable to the new Scantable schema ( not required for standard as Scantable is not assumed to be persistent) |
| | 19 | |
| | 20 | |
| | 21 | = Relevant Documentation = |
| | 22 | |
| | 23 | * ''attach spreadsheet for impact on all asap functions/methods/tasks'' |
| | 24 | * ''attach image of Scantable schema'' |
| | 25 | |
| | 26 | |
