[daip] help with AIPS
Amy Mioduszewski
amiodusz at nrao.edu
Tue Nov 11 18:11:34 EST 2008
Hi Melanie,
Well, quick look at your file shows me that it is in the wrong format. You need
to remove the source name (see the end of EXPLAIN SETFC). Try it with the
corrected file, but I also suspect you might have to set some BPARM.
Also, I noticed in the last set of inputs you sent me that you set cellsize to
3.5 when the recommended cellsize was 3.3025, if you round your cellsize you
should go smaller not bigger, so 3 rather than 3.5.
Amy
Melanie Gendre wrote:
> I do. I attach it here (columns: name, ra, dec, flux in mJy). Here are my
> inputs and message for SETFC:
>
> AIPS 1: SETFC: Task to make a BOXFILE for input to IMAGR
> AIPS 1: Adverbs Values Comments
> AIPS 1: ----------------------------------------------------------------
> AIPS 1: INNAME 'EISD_P1' UV dataset name (name)
> AIPS 1: INCLASS 'SPLIT' UV dataset name (class)
> AIPS 1: INSEQ 1 UV dataset name (seq. #)
> AIPS 1: INDISK 1 Disk drive #
> AIPS 1: SOURCES *all ' ' Source selected
> AIPS 1: BCOUNT 1 First field number to use
> AIPS 1: BOXFILE 'MYDATA:BOXFILE_1'
> AIPS 1: disk file to write to (the
> AIPS 1: input BOXFILE for IMAGR)
> AIPS 1: CELLSIZE 3.3025 3.3025 (X,Y) size of grid in asec
> AIPS 1: IMSIZE 512 512 field size
> AIPS 1: SHIFT 0 0 Position shift (RA,Dec) asec
> AIPS 1: for all fields
> AIPS 1: FLUX 0 Minimum component flux =
> AIPS 1: (source * beam)
> AIPS 1: BPARM *all 0 (1) Inner region radius (deg)
> AIPS 1: (2) Field overlap (pixels)
> AIPS 1: (3) Factor to scale NVSS
> AIPS 1: fluxes, 0 -> 1
> AIPS 1: (4) Radius NVSS search (deg)
> AIPS 1: (5) Flux limit in NVSS (Jy)
> AIPS 1: (6) IMSIZE for NVSS fields
> AIPS 1: (7) IMSIZE for Sun fields
> AIPS 1: (8) Write Clean boxes for
> AIPS 1: NVSS fields
> AIPS 1: (9) Maximum allowed phase
> AIPS 1: error in imaging
> AIPS 1: (10) Points per beaam
> AIPS 1: PBPARM *all 0 Beam parameters:
> AIPS 1: (1) Cutoff; (2) Use (3)-(7)
> AIPS 1: (3)-(7) Beam shape parms
> AIPS 1: INFILE 'CENSORS_SOURCELIST.ASCII'
> AIPS 1: NVSS input file name
> AIPS 1: ' ' => AIPS provided.
>
>
>
>
> localh> SETFC1: Task SETFC (release of 31DEC07) begins
> localh> SETFC1: Found EISD_P1 SPLIT Seq 1 Disk: 1 in slot 5
> localh> SETFC1: SETCEL: max baseline, W = 2.1979E+04 2.1487E+04 wavelengths
> localh> SETFC1: SETCEL: max field radius 8.1240E+02 arc seconds
> localh> SETFC1: SETCEL: recommends IMSIZE 519 CELLSIZE 3.12818
> localh> SETFC1: SETCEL: returns IMSIZE 512 CELLSIZE 3.30245
> localh> SETFC1: ZTXOP2: using translated file name =
> localh> SETFC1: ZTXOP2: /home/mgendre/Research/CENSORS/327MHz_Data/BOXFILE_1
> localh> SETFC1: First field number written was 1
> localh> SETFC1: Highest field number written was 0
> localh> SETFC1: returns adverbs to AIPS
> localh> SETFC1: Appears to have ended successfully
> localh> SETFC1: localhost 31DEC07 TST: Cpu= 0.9 Real= 1
>
>
> Melanie
>
>
>
>> I thought you had an input file.
>>
>> Amy
>>
>> Melanie Gendre wrote:
>>> Hi again,
>>>
>>> I have for input in SETFC:
>>> AIPS 1: SETFC: Task to make a BOXFILE for input to IMAGR
>>> AIPS 1: Adverbs Values Comments
>>> AIPS 1: ----------------------------------------------------------------
>>> AIPS 1: INNAME 'EISD_P1' UV dataset name (name)
>>> AIPS 1: INCLASS 'SPLIT' UV dataset name (class)
>>> AIPS 1: INSEQ 1 UV dataset name (seq. #)
>>> AIPS 1: INDISK 1 Disk drive #
>>> AIPS 1: SOURCES *all ' ' Source selected
>>> AIPS 1: BCOUNT 1 First field number to use
>>> AIPS 1: BOXFILE 'MYDATA:BOXFILE_1'
>>> AIPS 1: disk file to write to (the
>>> AIPS 1: input BOXFILE for IMAGR)
>>> AIPS 1: CELLSIZE 3.5 3.5 (X,Y) size of grid in asec
>>> AIPS 1: IMSIZE 512 512 field size
>>> AIPS 1: SHIFT 0 0 Position shift (RA,Dec) asec
>>> AIPS 1: for all fields
>>> AIPS 1: FLUX 0 Minimum component flux =
>>> AIPS 1: (source * beam)
>>> AIPS 1: BPARM *all 0 (1) Inner region radius (deg)
>>> AIPS 1: (2) Field overlap (pixels)
>>> AIPS 1: (3) Factor to scale NVSS
>>> AIPS 1: fluxes, 0 -> 1
>>> AIPS 1: (4) Radius NVSS search (deg)
>>> AIPS 1: (5) Flux limit in NVSS (Jy)
>>> AIPS 1: (6) IMSIZE for NVSS fields
>>> AIPS 1: (7) IMSIZE for Sun fields
>>> AIPS 1: (8) Write Clean boxes for
>>> AIPS 1: NVSS fields
>>> AIPS 1: (9) Maximum allowed phase
>>> AIPS 1: error in imaging
>>> AIPS 1: (10) Points per beaam
>>> AIPS 1: PBPARM *all 0 Beam parameters:
>>> AIPS 1: (1) Cutoff; (2) Use (3)-(7)
>>> AIPS 1: (3)-(7) Beam shape parms
>>> AIPS 1: INFILE ' '
>>> AIPS 1: NVSS input file name
>>> AIPS 1: ' ' => AIPS provided.
>>>
>>>
>>>
>>> The message is:
>>> localh> SETFC1: Task SETFC (release of 31DEC07) begins
>>> localh> SETFC1: Found EISD_P1 SPLIT Seq 1 Disk: 1 in slot 5
>>> localh> SETFC1: ZTXOP2: using translated file name =
>>> localh> SETFC1: ZTXOP2:
>>> /home/mgendre/Research/CENSORS/327MHz_Data/BOXFILE_1
>>> localh> SETFC1: First field number written was 1
>>> localh> SETFC1: Highest field number written was 0
>>> localh> SETFC1: returns adverbs to AIPS
>>> localh> SETFC1: Appears to have ended successfully
>>> localh> SETFC1: localhost 31DEC07 TST: Cpu= 0.0 Real= 0
>>>
>>>
>>>
>>> My boxfile is empty (see attached).
>>>
>>> Melanie
>>>
>>>
>>>
>>>> Send me your SETFC messages and inputs if you still have problems.
>>>>
>>>> Aamy
>>>>
>>>> Melanie Gendre wrote:
>>>>> Hi Amy,
>>>>>
>>>>> Thank you very much. Some things make much more sense now. I will try
>>>>> to
>>>>> see what my SETFC does.
>>>>> Unfortunately, I am the only person working with AIPS on VLA data
>>>>> here,
>>>>> so
>>>>> I am a bit on my own. But I will get it! Not gonna get discouraged by
>>>>> AIPS! Lol
>>>>>
>>>>> I'll let you know if I have any more problems. Thanks again for your
>>>>> help.
>>>>>
>>>>> Melanie
>>>>>
>>>>>
>>>>>> Eric is away for a couple weeks, I will try to answer your questions.
>>>>>>
>>>>>> Melanie Gendre wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have been in communication with Eric Greisen about some issues I
>>>>>>> have
>>>>>>> with AIPS, but I am still nowhere near understanding what's going
>>>>>>> on,
>>>>>>> and
>>>>>>> I can't seem to get anything from the Cookbook.
>>>>>>>
>>>>>>> Here's the situation:
>>>>>>> I have VLA data at 90cm taken in BnA and CnB configurations,
>>>>>>> covering
>>>>>>> a
>>>>>>> 6
>>>>>>> deg^2 field in 2 pointings (I have therefore 4 uv data files when I
>>>>>>> do
>>>>>>> SPLIT).
>>>>>>> I did the calibration of the data using the standard procedure
>>>>>>> FILLM,
>>>>>>> LISTR, QUACK, SETJY, CALIB, EDITA, GETJY, EXTDEST, CLCAL, SNPLT,
>>>>>>> SPLIT,
>>>>>>> UVSRT.
>>>>>>>
>>>>>>> The difference between these data and what I usually do is that I
>>>>>>> have
>>>>>>> several sources for each uv file (each pointings) and I'd like to
>>>>>>> get
>>>>>>> flux
>>>>>>> and contour plots for each sources individually.
>>>>>>>
>>>>>>> Eric suggested that I:
>>>>>>> - use SETFC to get the recommended CELLSIZE
>>>>>>> - change the CELLSIZE to a rounder close number and re-run SETFC to
>>>>>>> write
>>>>>>> the boxfile
>>>>>>> - use FLATN to make one large image of all the facets
>>>>>>> - use SAD or JMFIT to get the flux
>>>>>>>
>>>>>>> My (numerous) issues are:
>>>>>>> (1) What are the differences between "pointings", "sources",
>>>>>>> "fields"
>>>>>>> and
>>>>>>> "facets" in the AIPS jargon? I am confused between all those terms.
>>>>>>> If
>>>>>>> I
>>>>>>> have several sources in one pointing, does that mean I have one
>>>>>>> field
>>>>>>> or
>>>>>>> several fields?
>>>>>> A pointing is where the telescope was pointing, so it sounds like you
>>>>>> have
>>>>>> 2
>>>>>> pointings. Sources are sources. Fields is harder, he probably means
>>>>>> the
>>>>>> same
>>>>>> things as facets, because you set "fields" in IMAGR, which are the
>>>>>> individual
>>>>>> areas to image.
>>>>>>
>>>>>> What SETFC does is split the area you observed into smaller areas for
>>>>>> wide-field
>>>>>> 3D imaging. IMAGR assumes that the sky is flat and since it
>>>>>> obviously
>>>>>> isn't you
>>>>>> need to break a large area into smaller areas. You can run SETFC so
>>>>>> it
>>>>>> will
>>>>>> create fields around sources found in the NVSS or WENSS surveys as
>>>>>> well
>>>>>> (see
>>>>>> EXPLAIN SETFC). But if you don't do this then it just breaks the
>>>>>> area
>>>>>> up
>>>>>> regardless of if you have a source or sources in the field.
>>>>>>
>>>>>>> (2) Why do I have to run SETFC twice?
>>>>>> You don't *have* to run SETFC twice, it is just it usually picks a
>>>>>> cell
>>>>>> size
>>>>>> that is not aesthetically pleasing (for the lack of a better
>>>>>> description),
>>>>>> like
>>>>>> 2.1028469264asec when it would just be more pleasant to have a cell
>>>>>> size
>>>>>> of
>>>>>> something like 2asec.
>>>>>>
>>>>>>> (3) What exactly does the BOXFILE do? Does it isolate my sources?
>>>>>> BOXFILE from SETFC defines the fields to be imaged. BOXFILEs can
>>>>>> also
>>>>>> have
>>>>>> clean boxes defined in them, but SETFC does not do this.
>>>>>>
>>>>>>> (4) When I follow the procedure with SETFC, the output boxfile is
>>>>>>> empty.
>>>>>>> Why? (My guess would be that it's because nowhere do I tell AIPS
>>>>>>> there
>>>>>>> should be several boxes)
>>>>>> Does SETFC run without error? Send me your inputs. SETFC should
>>>>>> figures
>>>>>> out on
>>>>>> its own how many boxes (fields) you need. Maybe you don't need more
>>>>>> than
>>>>>> one
>>>>>> field.
>>>>>>
>>>>>>> (5) I actually know where the sources should be (I have the list of
>>>>>>> coordinates). Could that help in the reduction? If so, how?
>>>>>>> I tried to input this list of sources in INFILE in SETFC, and I get
>>>>>>> a
>>>>>>> BOXFILE output, but I am not sure of how reliable it is.
>>>>>> Yes, you should be able to get SETFC to make fields around your
>>>>>> sources.
>>>>>> How
>>>>>> reliable what is? Do you use the correct format for your list?
>>>>>>
>>>>>>> (6) Which leads to the question: how do I isolate my sources?
>>>>>> I don't know what you are asking. Isolate in what way? Clean them?
>>>>>> If
>>>>>> you
>>>>>> want to set clean boxes, you box them in IMAGR.
>>>>>>
>>>>>>> (7) In JMFIT, how do you point to each source individually? I can't
>>>>>>> see
>>>>>>> any input coordinate/file
>>>>>>>
>>>>>> You box them with TVWIN, (ie, fill in BLC, TRC), JMFIT needs to fit
>>>>>> an
>>>>>> area not
>>>>>> just a coordinate.
>>>>>>
>>>>>>> Maybe getting some insight of what the procedure is when you don't
>>>>>>> know
>>>>>>> what sources you have in the image would help me understand how this
>>>>>>> all
>>>>>>> works. I am getting really confused and a bit frustrated, and I'm
>>>>>>> sure
>>>>>>> it's just because I'm missing (or misunderstanding) something
>>>>>>> small...
>>>>>> Well it sounds like SETFC didn't give you what you wanted. Once you
>>>>>> get
>>>>>> the
>>>>>> fields set up it should be pretty easy. Is there anyone there that
>>>>>> can
>>>>>> help you
>>>>>> run IMAGR?
>>>>>>
>>>>>> Good luck!
>>>>>>
>>>>>> Amy
>>>>>>
>>>
>
>
More information about the Daip
mailing list