[daip] imagr problem
Eric Greisen
egreisen at cv3.cv.nrao.edu
Tue Jul 2 10:32:29 EDT 2002
Sara Tinti writes:
>
> Hello,
> I have the 31DEC02 aips version installed on a LINUX machine
> (RedHat 6.2) with f77 compiler. I can open the tv screen server and the
> message server and I can use some tasks but when I try to use imagr, mx
> or uvmap tasks I have error messages and the tasks die of UNNATURAL
> causes.
>
> The exact error message I get when I run imagr is:
>
> SEXTAN> IMAGR1: Task IMAGR (release of 31DEC02) begins
> SEXTAN> IMAGR1: Create 1335+5844X .IMAGR . 1 (UV) on disk 4 cno 1
> SEXTAN> IMAGR1: Beginning channel 1 through 1 with 1 IFs
> SEXTAN> IMAGR1: IMACPY: append zero spacing 1.0000 weight 1.0 Stokes
> I
> SEXTAN> IMAGR1: IMACPY: Copied 1933 visibilities to be imaged
> SEXTAN> IMAGR1: Create PIPPO .IBM001. 4 (MA) on disk 1 cno 12
> SEXTAN> IMAGR1: Create PIPPO .ICL001. 4 (MA) on disk 1 cno 13
> SEXTAN> IMAGR1: GRDFLT: X and Y convolution type = SPHEROIDAL
> SEXTAN> IMAGR1: GRDFLT: X and Y parms = 3.0000 1.0000
> SEXTAN> IMAGR1: GRDFLT: convolution function sampled every 1/100 of a cell
> SEXTAN> IMAGR1: FOR GRIDDING NEED 10772 HAVE ONLY 0 WORDS IN
> 'AP'
> SEXTAN> IMAGR1: PROBLEM AS POSED WILL NOT FIT EVEN IF DATA ARE SORTED
> SEXTAN> IMAGR1: OUVIMG: MAKING BEAM BEAM image for CLEAN
> SEXTAN> IMAGR1: OUVIMG: FROM UVdata work object
> SEXTAN> IMAGR1: CLNINI: ERROR OPENING CLEAN process object
> SEXTAN> IMAGR1: CLNUV : ERROR CLEANING CLEAN process object
> SEXTAN> IMAGR1: Deleting UV work file:
> SEXTAN> IMAGR1: Destroyed 1 extension files of type AN
> SEXTAN> IMAGR1: Destroyed 1 extension files of type FQ
> SEXTAN> IMAGR1: Destroyed UV image file: catno= 1 disk= 4
> SEXTAN> IMAGR1: Purports to die of UNNATURAL causes
> SEXTAN> IMAGR1: sextans 31DEC02 TST: Cpu= 0.3 Real= 1
>
It would appear that your installation thinks there are no words in
the "pseudo array processor" used by many of the most important tasks.
Exit aips and do the following:
RUN SETPAR
2
look at the values for parameter 11 - which should be 64 and parameter
29. I do not know what that value should be so try
29
99999
This will give you an error message such as
*** Pseudo-AP 2nd memory limited to 5056 not 999999
so enter whatever the first number is (5056 in my case). Then
-1
AMANAGER (the usual password)
4 (to exit)
Then try things again.
If the 5056 says 0 then you have a much larger problem. In that case
the file $INC/NOTST/$ARCH/PAPC.INC has an error in it. If this is the
case, send me the text of that file and I wil send you the lengthy
instructions for fixing your installation.
Eric Greisen
More information about the Daip
mailing list