[daip] Using source models in FRING
Leonia Kogan
lkogan at aoc.nrao.edu
Tue May 23 15:49:37 EDT 2000
Hello,
I have finished the check of FRING and comparison it with CALIB.
1.
>FRING1: FREQUENCIES DO NOT LIE ON A UNIFORM GRID.
>FRING1: THIS MAY DEGRADE DETERMINATION OF DELAYS.
>P.P.S. Note that the complaint about a nonuniform grid may occur because
>the UV file has multiple FREQIDs. However, within each FREQID, the
>spacing is uniform. You may find that the trigger for this message needs
>updating - or perhaps I am missing something.
No the complain can not occur because of multiple FREQIDs. You actually selected
one FREQID=2.
Subroutine GRDFRQ estimates nonuniformity of the frequencies using operator MOD:
FERROR = MOD (ABS (FREQS(I) - FREQS(1)), DF)
Then FERROR is compared with FTOL. If (FERROR .GE. FTOL) then the frequencies
are considered ununiform and the message appears.
The tollerance TOL=1.E-7 may be too small in comparison with possible mistake
of FERROR's calculation by MOD.
This is my explanation of this message. If I am right then the message is not
dangerous. Having discussed this issue here I'll try to modify the trigger of
this message.
2.
>We do not receive a message from FRING that it is using a particular
>number of CCs to construct the model.
>Were we running CALIB, we would receive such a message.
FRING carries out identical (with CALIB) calculation of the used CC components
but does not print them.
I can add the prints to make FRING print the used CC components.
Leonia
----- Begin Included Message -----
>From owner-daip at kochab.cv.nrao.edu Tue May 23 09:33 MDT 2000
Date: Tue, 23 May 2000 11:28:56 -0400 (EDT)
From: Lincoln Greenhill <lincoln at play.harvard.edu>
To: daip at cv3.cv.nrao.edu
cc: jmonnier at cfa.harvard.edu
Subject: [daip] Using source models in FRING
MIME-Version: 1.0
Sender: owner-daip at kochab.cv.nrao.edu
Precedence: bulk
X-Lines: 170
Status: RO
Dear Leonia,
We are running FRING on a multi-source file that contains VLBA data.
We are supplying FRING with a source model though IN2NA, etc.
The source model has two fields, each with on the order of 100 CCs.
We do not receive a message from FRING that it is using a particular
number of CCs to construct the model.
Were we running CALIB, we would receive such a message.
I would like to make absolutely certain that FRING is in fact using the
source model information we give it, in the form of CCs.
Can you please interpret the following output messages from FRING and/or
double-check the code of FRING itself?
The inputs follow the list of messages.
Thank you very much for your help.
Regards,
Lincoln
P.S. Please direct replies to jmonnier at cfa, with a cc: to me.
P.P.S. Note that the complaint about a nonuniform grid may occur because
the UV file has multiple FREQIDs. However, within each FREQID, the
spacing is uniform. You may find that the trigger for this message needs
updating - or perhaps I am missing something.
-----
FRING1: Task FRING (release of 15OCT99) begins
FRING1: You are using a non-standard program
FRING1: Selecting, editing and calibrating the data
FRING1: SETGDS: imaging done with one tangent plane
FRING1: VISDFT: Begin DFT component division
FRING1: VISDFT: Model components of type Point
FRING1: I Polarization model processed
FRING1: Model computation is 10 percent complete
FRING1: Model computation is 20 percent complete
FRING1: Model computation is 30 percent complete
FRING1: Model computation is 40 percent complete
FRING1: Model computation is 50 percent complete
FRING1: Model computation is 60 percent complete
FRING1: Model computation is 70 percent complete
FRING1: Model computation is 80 percent complete
FRING1: Model computation is 90 percent complete
FRING1: Model computation is 100 percent complete
FRING1: Determining solutions
FRING1: Doing Least Squares fits for multi and single band delays
FRING1: Writing SN table 16
FRING1: FREQUENCIES DO NOT LIE ON A UNIFORM GRID.
FRING1: THIS MAY DEGRADE DETERMINATION OF DELAYS.
FRING1: Found 1348 good solutions
FRING1: Appears to have ended successfully
FRING1: rgalp6 15OCT99 NEW: Cpu= 449.2 Real= 474 IO= 27114
AIPS 1: FRING: Task to fringe fit data
AIPS 1: Adverbs Values Comments
AIPS 1: ----------------------------------------------------------------
AIPS 1: Input uv data.
AIPS 1: INNAME 'MULTI ' UV file name (name)
AIPS 1: INCLASS 'UVDATA' UV file name (class)
AIPS 1: INSEQ 1 UV file name (seq. #)
AIPS 1: INDISK 4 UV file disk drive #
AIPS 1: Data selection (multisource):
AIPS 1: CALSOUR 'J1833-2103 ' Calibrator sources
AIPS 1: *rest ' '
AIPS 1: QUAL -1 Calibrator qualifier -1=>all
AIPS 1: CALCODE ' ' Calibrator code ' '=>all
AIPS 1: SELBAND -1 Bandwidth to select (kHz)
AIPS 1: SELFREQ -1 Frequency to select (MHz)
AIPS 1: FREQID 2 Freq. ID to select.
AIPS 1: TIMERANG *all 0 Time range to use.
AIPS 1: BCHAN 1 Lowest channel number 0=>all
AIPS 1: ECHAN 0 Highest channel number
AIPS 1: ANTENNAS *all 0 Antennas to select. 0=all
AIPS 1: DOFIT *all 0 Subset of ANTENNAS list
AIPS 1: for which solns are desired.
AIPS 1: 0 => solve for all antennas
AIPS 1: implied by ANTENNAS list
AIPS 1: SUBARRAY 0 Subarray, 0=>all
AIPS 1: UVRANGE 0 0 Range of uv distance for full
AIPS 1: weight
AIPS 1: WTUV 0 Weight outside UVRANGE 0=0.
AIPS 1:
AIPS 1: Cal. info for input:
AIPS 1: DOCALIB 1 If >0 calibrate data
AIPS 1: GAINUSE 4 CL table to apply.
AIPS 1: FLAGVER 2 Flag table version
AIPS 1: DOBAND 1 If >0 apply bandpass cal.
AIPS 1: Method used depends on value
AIPS 1: of DOBAND (see HELP file).
AIPS 1: BPVER 4 Bandpass table version
AIPS 1: SMOOTH *all 0 Smoothing function. See
AIPS 1: HELP SMOOTH for details.
AIPS 1:
AIPS 1: CLEAN map (optional)
AIPS 1: IN2NAME 'LENS.X ' Cleaned map name (name)
AIPS 1: IN2CLASS 'ICLN ' Cleaned map name (class)
AIPS 1: IN2SEQ 14 Cleaned map name (seq. #)
AIPS 1: IN2DISK 4 Cleaned map disk unit #
AIPS 1: INVERS 1 CC file version #.
AIPS 1: NCOMP *all 0 # comps to use for model.
AIPS 1: 1 value per field
AIPS 1: FLUX 0 Lowest CC component used.
AIPS 1: NMAPS 2 No. Clean map files
AIPS 1: SMODEL *all 0 Source model, 1=flux,2=x,3=y
AIPS 1: See HELP SMODEL for models.
AIPS 1:
AIPS 1: Output uv data file.
AIPS 1: OUTNAME 'LENS.X ' UV file name (name)
AIPS 1: OUTCLASS 'ICLN ' UV file name (class)
AIPS 1: OUTSEQ 14 UV file name (seq. #)
AIPS 1: OUTDISK 4 UV file disk drive #
AIPS 1:
AIPS 1: Solution control adverbs:
AIPS 1: REFANT 4 Reference antenna
AIPS 1: SEARCH *all 0 Prioritized reference antenna
AIPS 1: list - supplements REFANT
AIPS 1: ** press RETURN for more, enter Q or next line to quit print **
#
AIPS 1: - but only if APARM(9)>0
AIPS 1: SOLINT 2 Solution interval (min)
AIPS 1: 0 => 10 min
AIPS 1:
AIPS 1: APARM 3 0 General parameters
AIPS 1: 0 0 1=min. no. antennas
AIPS 1: 2 *rest 0 2 > 0 => data divided
AIPS 1: 3 > 0 => avg. RR,LL
AIPS 1: 4 > 0 => avg. freq. in IFs
AIPS 1: 5 > 0 => combine IFs.
AIPS 1: 6=print level, 1=some
AIPS 1: 7=SNR cutoff (0=>5)
AIPS 1: 8=max. ant. # (no AN)
AIPS 1: 9 > 0 => do exhaustive
AIPS 1: baseline search
AIPS 1: DPARM 3 *rest 0 Delay-rate parameters
AIPS 1: 1=no. bl combo. (def=3)
AIPS 1: 2=delay win (nsec), if <0
AIPS 1: no delay search done
AIPS 1: 3=rate win (mHz)
AIPS 1: 4=int. time (sec)
AIPS 1: ** press RETURN for more, enter Q or next line to quit print **
#
AIPS 1: 0 => min. found in data
AIPS 1: 5 >0 => don't do ls. soln
AIPS 1: 6 >0 => don't avg. in freq
AIPS 1: 7 >0 => don't rereference
AIPS 1: phase
AIPS 1: 8 > 0 => activate zero'ing
AIPS 1: options
AIPS 1: SNVER 0 Output SN table, 0=>new table
AIPS 1: ANTWT *all 0 Ant. weights (0=>1.0)
AIPS 1: BADDISK *all 0 Disk no. not to use for
AIPS 1: scratch files.
>
----- End Included Message -----
More information about the Daip
mailing list