[daip] autoboxing

[Eric Greisen]

Lynn D. Matthews wrote:
>> I suspect the failure below is a consequence of problems handling 
>> filtered output and only accidentally related to the auto-boxing.  The 
>> filtered data were so like the non-filtered data that there was 
>> nothing left to Clean. Somehow this did not get passed properly and so 
>> it tried an illegal subtraction and everything fell apart.  I will 
>> have to look at this - it may come from my adding a continue Cleaning 
>> after the "final" filtering in case the filtering mattered.  When it 
>> doesn't - which is what one hopes for a "final" it should then 
>> complete gracefully.
>>
> 
> Yes, I just did a test that confirms that this is unrelated to the 
> auto-box. I have largely stopped using the filtering since it was 
> modified, but I used it in the tests to be consistent with my previously 
> processed data.

By changed do you mean the change I made to do a round of Clean after 
the "final" filter?  If so, why does this stop its use?  Or whcih change 
do you mean?

> 
> One more question; if I look at the history files for IMAGR, some of the 
> images I made today list:
> 
> IMAGRPRM(19) =0.5000 / Dynamic range limit
> 
> as the last line of the history file, while others with the same 
> IMAGRPRM inputs do not. Why so? My impression from the help file is that 
> this parameter is only relevant if OVERLAP>2 (I'm using OVERLAP 0).

The HI writing is object style - if a parameter is not zero/blank it is 
written whether it was relevant or not.  In this case, however, I find 
no limit on IMAGRPRM(19) to any particular value of OVERLAP and I do not 
see from the help why you would expect such.  It may be more useful in 
multi-facet cases, but it has a use everywhere.

I will look at the filtering bug tomorrow - I have been upgrading FILIT 
today.

I will need to write an AIPS Memo on the autoboxing so I am interested 
in what you find.

Thanks,

Eric