[daip] RMCUB errors

[Eric Greisen]

Data Analysts writes:

 > >  >go
 > > AIPS 1: Found in Version=RM
 > > ZSSSX2: write data packet 2: Bad file descriptor
 > >  ZTTYIO: LUN =  6 NOT OPEN IN FTAB
 > >  ZMSGCL: LUN =  6 ALREADY CLOSED IN FTAB ON SEARCH
 > >  ZTTYIO: LUN =  6 NOT OPEN IN FTAB
 > >  ZMSGCL: LUN =  6 ALREADY CLOSED IN FTAB ON SEARCH
 > >  ZTTYIO: LUN =  6 NOT OPEN IN FTAB
 > >
 > >
 > > The inputs for the task are
 > >
 > > >inp
 > > AIPS 1: Found in Version=RM
 > > AIPS 1: RMCUB : Task to plot pol angle vs lambda**2 on grid of y, and z
 > > AIPS 1: Adverbs     Values                 Comments
 > > AIPS 1: ----------------------------------------------------------------
 > > AIPS 1: USERID        0                    User ID.  0=>current user
 > > AIPS 1:                                      32000=>all users
 > > AIPS 1: INNAME     '2200_8-43GHz'          Image name (name)
 > > AIPS 1: INCLASS    'TRANS'                 Image name (class)
 > > AIPS 1: INSEQ         1                    Image name (seq. #)
 > > AIPS 1: INDISK       15                    Disk drive #
 > > AIPS 1: BLC         288         384        Bottom left corner of image
 > > AIPS 1:            *rest 0                   0=>entire image
 > > AIPS 1: TRC         292         388        Top right corner of image
 > > AIPS 1:            *rest 0                   0=>entire image
 > > AIPS 1: YINC          1                    Increment on 2nd axis to plot
 > > AIPS 1: ZINC          0                    Increment on 3rd axis to plot
 > > AIPS 1: PIXRANGE   -180         180        Range of degrees on y-axis
 > > AIPS 1: LTYPE         4                    Type of labeling: 1 border,
 > > AIPS 1:                                    2 no ticks, 3 standard, 4 rel
 > > AIPS 1:                                    to center, 5 rel to subim cen
 > > AIPS 1:                                    6 pixels, 7 standard w/o any
 > > AIPS 1:                                    headers
 > > AIPS 1: APARM         4           3        1: Number of freq. in cube
 > > AIPS 1:               0           0        2: Number of freq. to use
 > > AIPS 1:               0           0         in the fit. The first
 > > AIPS 1:               0           1         APARM(2) freq. will be used.
 > > AIPS 1:               0           0        3: panels/page in x-direction
 > > AIPS 1:                                      0=> MIN (TRC(2)-BLC(2+1,5)
 > > AIPS 1:                                    4: panels/page in y-direction
 > > AIPS 1:                                      0=> final value of APARM(1)
 > > AIPS 1:                                    5: LTYPE for panels 0=>LTYPE
 > > AIPS 1:                                    6: maximum rotation measure
 > > AIPS 1:                                    7: initial guess for the RM
 > > AIPS 1:                                    8: Solution type >0 weighted
 > > AIPS 1:                                       fit, assumes last half of
 > > AIPS 1:                                       cube are error maps
 > > AIPS 1:                                    9: y-value x-axis: leave 0
 > > AIPS 1:                                   10: x-value y-axis: leave 0
 > > AIPS 1: BPARM      8421.459    15365.459  1-7: First 7 freq in cube(MHz)
 > > AIPS 1:            22233.459   43217.461    8: constant position angle
 > > AIPS 1:            *rest 0                     err to add in quadrature
 > > AIPS 1:                                     9: 1 => include zero wavelen
 > > AIPS 1:                                        0 => self-scale x axis
 > > AIPS 1: INFILE     ' '
 > > AIPS 1:                                   Optional input disk file name
 > > AIPS 1:                                   containing freq in cube (MHz)
 > > AIPS 1: DOTV          1                   > 0 => TV, else plot file
 > > AIPS 1: GRCHAN        1                   graphics channel to use
 > > >
 > >
 > > What's wrong? Please help.
 > >

I have no idea.  This task is not present in the AIPS we distribute.
(The version=rm is a clue to that.)

Making wild guesses - the TV is perhaps not properly opened and I
would expect that some array has overflowed making a mess of the
message handling.

Eric Greisen