This loads a font easier to read for people with dyslexia.
This renders the document in high contrast mode.
This renders the document as white on black
This can help those with trouble processing rapid screen movements.

RE: [atnf-data-reduction] Miriad task FITS error: Illegal baseline number

From: <rsault_at_email.protected>
Date: Wed, 13 Jun 2007 13:28:57 +1000

Yosi, Mark,

My reading of Yosi's description is that the antenna
table might be slightly bad. Perhaps Yosi could provide
that somewhere so that an appropriate check for
the particular problem can be added.

Miriad has been used by many people to reduce VLA
data.

Best regards
Bob
--
---------------------------------------------------
Phone:   +61-3-83447074
Email:   rsault_at_physics.<!--nospam-->unimelb.edu.au
Web:     http://astro.ph.unimelb.edu.au/~rsault
> -----Original Message-----
> From: owner-atnf-data-reduction_at_atnf.<!--nospam-->csiro.au [mailto:owner-atnf-data-reduction_at_atnf.<!--nospam-->csiro.au] On
> Behalf Of Mark Calabretta
> Sent: Wednesday, 13 June 2007 12:08 PM
> To: Yosi Gelfand
> Cc: atnf-data-reduction_at_atnf.<!--nospam-->csiro.au
> Subject: Re: [atnf-data-reduction] Miriad task FITS error: Illegal baseline number
> 
> 
> On Thu 2007/06/07 14:06:04 -0400, Yosi Gelfand wrote
> in a message to: atnf-data-reduction_at_atnf.<!--nospam-->csiro.au
> 
> Dear Yosi,
> 
> >	I was wondering if anyone has gotten a similar error message when
> >trying to using the Miriad task FITS to read in UV data taken with the VLA
> >that was written out by AIPS that has multiple AN extensions:
> >	 ### Fatal Error:  Illegal baseline number in antbas
> 
> I'm not aware of anyone at the ATNF who is currently using our local
> variant of Miriad to process VLA data.  In fact, an in-house review
> conducted within the last 12 months decided not to support processing
> of data from non-ATNF instruments, among others specifically mentioning
> the VLA which is well supported by AIPS.
> 
> However, I'm sure that Miriad has been used in the past to process VLA
> data which suggests that this problem may have crept in somehow and so
> should not be difficult to fix.
> 
> >I tracked this error down to FITS assigning Antenna 26 an antenna location
> >of 0, though Antenna 26 was present in all of the AN extensions.  I've
> >managed to edit fits.for to work around this error, but not by fixing
> >antenna 26 getting a non-zero location.
> 
> If you can provide the fix I'll add it to the local code.
> 
> Regards,
> Mark Calabretta
> ATNF
Received on 2007-06-13 13:27:46