Opened 16 years ago

Last modified 15 years ago

#168 assigned defect

scantable.save doesn't honour frequency conversions for non asap output

Reported by: Malte Marquarding Owned by: Malte Marquarding
Priority: normal Milestone: ASAP 2.4
Component: General Version: 2.0
Severity: minor Keywords: coordinates, save, export
Cc:

Description

Frequency conversion is only done on-the-fly for toWorld calls. The underlying coordinate isn't changed from the original though. That means on data export the initial state is saved not taking into account e.g. frame changes.

Th current workaround is to use scantable.freq_align before saving. This will regrid the coordinate. We should probably make this the default. However, this won't work for PKSwriter output as this takes information from the STHeader. This needs to be changed and then we can get rid off this class in favour of table keywords.

This should become a new ticket and breaks the table format -> major version change.

Change History (2)

comment:1 by Malte Marquarding, 15 years ago

Status: newassigned

Had a look at this. The only way to do this is to call freq_align before saving to external formats (except ASCII, which call toWorld). This has been done in changeset:1575. STHeader items get stored/restored into table keywords.

Still to do is the update of the table keywords which get used by PKSwriter

comment:2 by Malte Marquarding, 15 years ago

Severity: criticalminor
Note: See TracTickets for help on using tickets.