[daip] Re: CONFI

[Leonia Kogan]

Mark,

Yes, last year I enhanced the concept of the mask file adding the option 
of the file in fits format. But the option of the ASCII format is there 
as well. The help file say:
"If the IN2FILE includes character sequence 'FITS' then
                the IN2FILE is interpreted as FITS format file
             else the file is interpreted as ASCII format file:"

But I changed the concept of restricted (masked) points:

"3. IND, restricted (IND=1) or not restricted (IND=0)"

You consider  "unmasked pixels  (ie, mask value == 1)  "
The last version of CONFI  uses the opposite concept. See help:
"3. IND, restricted (IND=1) or not restricted (IND=0)"

Leonia






Mark Holdaway wrote:

>
> Leonia,
>
> I'm having trouble with the topography file in CONFI.
>
> two years ago, I used an ASCII mask -- this year, I notice that
> CONFI can read FITS files.   Well, I have generated an initial
> configuration file which has all stations sitting in unmasked pixels
> (ie, mask value == 1)   --  however, CONFI is complaining that
>
> air   > CONFI1: Reading from disk file: FITS:FULL.MASK.14.3.FITS
> air   > CONFI1: NBAD =   744605
> air   > CONFI1: Some antennas are outside the topography mask
> air   > CONFI1: Purports to die of UNNATURAL causes
>
> Presumably there is a problem with the way the antenna coordinates
> are converted to image pixel values, which you need BLC, TRC, and
> CELL for.   (I might add that this seems a bit backwards to me --
> I would have used the REF_PIX, REF_VAL, and CELLSIZE from
> the FITS header.)   Can you please shed some light on the details
> of what is going on?   Presumably I am off by 1 pixel or 0.5 pixel in the
> way I am defining things, though I have tried shifting the BLC and TRC
> by 5m and 10m, but nothing is fixed.
>
>
> Thank you,
>
>     -Mark