Opened 15 years ago

Closed 14 years ago

#80 closed defect (wontfix)

window selection not working as expected

Reported by: JamieStevens Owned by: MarkWieringa
Priority: minor Milestone:
Component: MIRIAD - CABB branch Version:
Keywords: Cc:
Estimated Number of Hours: 0 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0

Description

From the file 2009-04-06_1121.RFI, I ATLOD it

atlod in=2009-04-06_1121.RFI out=set1.uv options=noif,unflag

I then unflag all the visibilities otherwise all data is flagged:

uvflag vis=set1.uv flagval=unflag

Now when I go to uvspec or uvplt and select window 1, I get the first IF as expected. When I don't specify a window in select, I get only the first IF. But when I select window 2 I get the error:

### Fatal Error: Invalid window selection, in UVREAD(select)

uvindex shows that both IF windows are present, and indeed a uvsplit creates all the files that one would expect for both IFs, and when one plots the second IF from the split files it appears as normal.

I am calling this priority minor because I've never experienced a problem with selecting the second IF with window before, so it may just be a fluke set of circumstances leading to this bug.

Change History (3)

comment:1 Changed 15 years ago by VincentMcIntyre

workaround: avoid the NOIF option, or split the IFs into distinct files.

comment:2 Changed 15 years ago by VincentMcIntyre

We will always have full Stokes with CABB so NOIF is not needed for such data?

One test case: spacecraft tracking - C999 Sep 2009

comment:3 Changed 14 years ago by MarkWieringa

Resolution: wontfix
Status: newclosed

Window selection is only meant to work for multiple windows in a spectrum. When NOIF is used, the data is stored with a uv variable in the data separating the frequencies, there will be only one window at a time in that case. The confusion arises because uvindex will show the frequency setups it finds in a similar way.

Note: See TracTickets for help on using tickets.