Opened 14 years ago

Closed 14 years ago

#116 closed defect (invalid)

gpnorm failing when bandpass tables are present

Reported by: JamieStevens Owned by: MarkCalabretta
Priority: major Milestone:
Component: MIRIAD - main line Version:
Keywords: Cc:
Estimated Number of Hours: 0 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0

Description

For reference please see conversation at http://atcaforum.freeforums.org/gpnorm-gives-fatal-error-when-bandpass-tables-are-present-t39.html

Dominic reports that the gpnorm task does not work on a dataset that has a bandpass table or correction applied. He further states that this is a recent issue and that previous gpnorm versions did not suffer from this.

Change History (1)

comment:1 Changed 14 years ago by MarkCalabretta

Resolution: invalid
Status: newclosed

Bob Sault revised gpnorm on 2009/09/30. The change was simply to check for, and abort with the following message if bandpass tables are present:

"Bandpass tables present

GPNORM does not work correctly in this case"

He sent me an email about it:

"I realized the other day that gpnorm does not correctly handle

bandpass tables being present (a problem unrelated to MarkW's recent work). So for the time being gpnorm aborts if bandpass tables are present. Some time I will get around to handling this correctly."

In the meantime I suggest adopting Jamie's strategy of applying the bandpass cal using uvaver.

Note: See TracTickets for help on using tickets.