- 1 Overview
- 2 AIPS
- 3 Getting the Data
- 4 About the Data
- 5 Starting AIPS and Loading the Data
- 6 Reducing the data
- 6.1 Preliminary Data Evaluation
- 6.2 Data Reduction Procedure
- 6.3 Calibrate Ionospheric Delay and Fix Earth Orientation Parameters
- 6.4 Apply Digital Sampling Correction to VLBA data
- 6.5 Plot Cross Power Spectrum
- 6.6 Determine Delay Corrections
- 6.7 Create BP Table and Calibrate Bandpass Shape
- 6.8 Apply Amplitude Corrections
- 6.9 Examine Amplitude Calibration
- 6.10 Correct Phases for Parallactic Angles
- 6.11 Manually Edit Data
- 6.12 Fringe Fit the Data
- 6.13 Apply FRING solutions
- 6.14 Backing up Your Calibration
- 6.15 Apply Calibration and SPLIT the Data
- 6.16 Imaging and Self-Cal on 1828+487
- 6.17 Create More Images
A good resource for reducing basic VLBI data in AIPS can be found in Appendix C of the AIPS Cookbook. Chapter 9:Reducing VLBI Data in AIPS of the AIPS Cookbook contains much more detail, but is best used as a reference. So with this tutorial you will:
- Calibrate the regular data all the way through imaging.
- Perform self-calibration to improve the imaging
This guide only give the important inputs to task. The other inputs should be default. An easy way to set all the inputs to the default in a task is to type "default taskname".
For a comprehensive overview of AIPS see the AIPS COOKBOOK, especially Chapter 3:Basic AIPS Utilities and Chapter 12:AIPS for the More Sophisticated Userfor the basics. Chapter 9:Reducing VLBI Data in AIPS is the chapter explaining VLBI data reduction, but it is rather overwhelming so Appendix C:A Step-by-Step Recipe for VLBA Data Calibration in AIPS is recommended as a first step. However, below I summarize some useful commands (in parenthesis are the short form of the command):
- getname (getn) catalog #: get the name of catalog # and put in INNAME, INCLASS and INSEQ. Other similar: geton (get outname); get2n (get in2name); get3n (getin3name) etc..
- input (inp) taskname: show the inputs of taskname.
- tget taskname: get a task and fill in the inputs of the last time the task was run, one of the most useful commands in AIPS.
- ucat (uc): list uvdata catalog.
- mcat (mc): list map catalog.
- tvlod (tvlo): load a map onto the TV.
- tvinit (tvin): initialize and clear TV.
- imhead (imh): Print the file header (this can be used on both uv data and images despite the name). This will list informative things like the date of observation and the number and types of tables attached to the data.
Getting the Data
To obtain the data, right click on these file below and select "Save Link As...":
- bl193bg_3sour_avg.fits (543 MB): Data we will be reducing today.
If that doesn't work you can also ftp the data using anonymous ftp:
- ftp ftp.aoc.nrao.edu
- login as anonymous
- cd pub/SIW
- get bl193bg_3sour_avg.fits
The best place to put the data is in your $FITS area. This is an AIPS data area that should already have an environmental variable set up for it.
About the Data
This is part of an observation from the MOJAVE survey. MOJAVE is a large project that uses the VLBA to monitor Active Galactic Nuclei at 15 GHz in total and polarized flux. This project has been monitoring AGN for over a decade. The the observation we are using took place on 16 June 2016 and contained 22 sources. However in order to make the data a managable size for a data reduction tutorial, three sources have been copied out of this dataset and the frequencies channels and integration time have both been averaged by a factor of two. The sources in the the bl193bg_3sour_avg.fits dataset are as follows:
- 0851+202 - BL Lac object, bright source with not a lot of structure, used as bandpass calibrator, aka OJ287. MOJAVE source page
- 1828+487 - Quasar, bright source with a very extended defuse jet, aka 3C380. MOJAVE source page
- 2200+420 - The original BL Lac object, bright source with extended curved jet, aka BL Lac. MOJAVE source page
We thank the MOJAVE team for maintaining the MOJAVE database and Matt Lister (Purdue) in particular for advice on the best data to select (Lister et al., 2009, AJ, 137, 3718).
Starting AIPS and Loading the Data
Start AIPS by typing aips or possibly aips tv=local:0.0 in a terminal window. Depending on your AIPS installation, you might be prompted to pick a printer, then you will be asked for an AIPS number, if you are not sharing disks with anyone pick any number other than 1. Remember that number because the data you load and work on will be under that number. It would be best for this tutorial for you to use a clean AIPS number, in other words, an AIPS number that you have not used for anything else and has no data loaded into it.
Loading Data Into AIPS
Load the data with FITLD. Note that I am forcing an outname, outclass and outseq, we are doing it here so it will be easy to take about specific files.
First load the target and calibrators
- default fitld
- clint 0.25 ➜ set CL table interval to 15 seconds.
- datain 'FITS:bl193bg_3sour_avg.fits ➜ Two things to note: 1) this assumes that the data is in the $FITS directory, you can use a full directory path (e.g., datain '/home/mydata/bl193bg_3sour_avg.fits) or another environmental variable if the data is elsewhere; 2) The lack of a close ' is not a typo, you must leave off the closing ' or AIPS will capitalize the everything within the ' ' and you will get an error because FITLD will not be able to find the data.
- outname 'bl193bg'
- outclass 'uvdata'
- outseq 1
- outdisk 1
- inp ➜ check the inputs
Lets look at our uv data catalog
You should get something that looks similar to (with a different Usid and Last access):
AIPS 1: Catalog on disk 1 AIPS 1: Cat Usid Mapname Class Seq Pt Last access Stat AIPS 1: 1 194 BL193BG .UVDATA. 1 UV 29-JUN-17 19:39:03
Note the data file, BL193BG.UVDATA.1, has a catalog number (Cat) which in this case 1. Catalog numbers can be, and usually are, used to fill in IN and OUTNAMES etc., using getn, geton etc..
Reducing the data
Preliminary Data Evaluation
Look at the structure of the data with LISTR. This will give you a listing of the scans as well as the sources and frequency structure in the observation. Note that even though this dataset contains only three sources, the SU (source) table still contains all the sources in the original dataset, so LISTR will list all the sources and show 0 visabilities for the sources with no data.
- default listr
- getn BL193BG.UVDATA.1 file; in other words getn 1
- optype 'scan'
- docrt 1
This will give you a listing of the scans and frequencies in the observation.
Data Reduction Procedure
Load in the VLBA data reduction procedures: see EXPLAIN VLBAUTIL for full description of procedures.
Procedures are run by just typing their name, rather than using "go".
- run vlbautil
If you get a BLEW CORE or other similar error message, you have filled your procedure memory (VLBAUTIL is very large and loading it three times will do this). To fix it type "restore 0" then reload VLBAUTIL
Calibrate Ionospheric Delay and Fix Earth Orientation Parameters
Data observed at 8 GHz or lower frequencies may be effected by the dispersive delay caused by the ionosphere. This will distort images and is especially bad at very low frequencies. An ionospheric correction based on maps of the electron content of the ionosphere can be performed with VLBATECR. BL193BG is observed at 15 GHz so no ionospheric correction is needed.
Data using phase referencing can be effected by imprecise Earth Orientation Parameters (EOPs) used in correlation. Therefore all phase referenced data should have its EOPs corrected. This can be done with VLBAEOPS. BL193BG does not use phase referencing so no EOP correction is needed.
Apply Digital Sampling Correction to VLBA data
Correct sampler threshold errors from correlator by running VLBACCOR.
- default vlbaccor
- getn 1
VLBACCOR runs ACCOR which creates an soulution (SN) table then smooths the table with SNSMO then runs CLCAL to apply the solutions to the calibration (CL) table. When VLBACCOR is finished you should get messages like those below that tell you what SN tanle and CL table are created. It is a good idea to keep save these messages.
AIPS 1: 'SN #1 CONTAINS SAMPLER CORRECTIONS' AIPS 1: 'CL #2 ADDS SAMPLER CORRECTIONS'
Plot Cross Power Spectrum
Now lets take a look at the fringe finders by running VLBACRPL. VLBACRPL runs POSSM and displays the spectrum of each baseline (to Fort Davis (antenna 2)), with the amplitude on the bottom and the phases on the top.
- default vlbacrpl
- getn 1
- stokes 'half'
- refant 2
- gainuse 0
- solint -1
- dotv 1
- source '0851+202'
As you can see from Figure 1, 0851+202 has very strong fringes. So we will use it as the calibrator to set the instrumental delays. Also look at your terminal for instructions on how to control POSSM:
POSSM1: Waiting 30 seconds: POSSM1: Hit TV button A to pause indefinitely. Hit button POSSM1: B or C to continue sooner, button D to stop plotting
So hit A if you want to look at a plot longer than the 30 seconds, B or C to go to the next plot, D to exit.
Determine Delay Corrections
Find and remove instrumental delay by running VLBAPCOR.
- default vlbapcor
- getn 1
- calsour '0851+202'
- timer 0 19 26 33 0 19 36 38 ➜ scan with good fringes on all telescopes we found in POSSM plots.
- refant 2 ➜ choose reference antenna from in the middle of array, antenna 2 or FD (Fort Davis, TX) is a good choice.
- gainu 0 ➜ apply highest CL table.
At this point you should check on the calibration:
- VLBAPCOR runs PCCOR which used the pulse cals to correct the intrumental phases and then runs CLCAL to apply the solutions to the CL (calbration table). The output from VLBAPCOR will look something like this:
AIPS 1: 'RUN PCCOR' PCCOR1: Task PCCOR (release of 31DEC17) begins PCCOR1: Writing to SN table 2 PCCOR1: Appears to have ended successfully PCCOR1: localhos 31DEC17 TST: Cpu= 0.9 Real= 2 IO= 93 AIPS 1: Resumes AIPS 1: 'RUN CLCAL' CLCAL1: Task CLCAL (release of 31DEC17) begins CLCAL1: Using interpolation mode SELF CLCAL1: Copied CL file from vol/cno/vers 1 183 2 to 1 183 3 CLCAL1: CALSEL: Making room for new CL data by CLCAL1: Deleting CL table no. 3 CLCAL1: Processing SN table 2 CLCAL1: SNMRG: Merging SN table CLCAL1: SNMRG: Write 2974 merged records from 2974 input records CLCAL1: SN2CL: Applying SN tables to CL table 2, writing CL table 3 CLCAL1: Appears to have ended successfully CLCAL1: localhos 31DEC17 TST: Cpu= 0.3 Real= 1 IO= 138 AIPS 1: Resumes AIPS 1: 'SN #2 CONTAINS PCAL INSTR. PHASE CORRECTIONS' AIPS 1: 'CL #3 ADDS INSTR. PHASE CORRECTIONS'
Again, it is a good idea to make note of the last two lines that tell you which tables contain which corrections. Most VLBAUTIL calibration scripts produce such messages.
- check solutions in POSSM, the jumps in phase between the IFs should be gone. The phases may also be flattened.
- tget possm ➜ to "get" all the inputs from the last run (it was run when we ran the procedure VLBACRPL).
- gainu 3
As you can see from Figure 2, the phases for 0851+202 have been flattened and the phase jumps between the IFs are gone. For other sources farther away in time the phases may be different from 0 but there will still be no phase jumps.
Create BP Table and Calibrate Bandpass Shape
Calibrate bandpass shape with VLBABPSS.
- default vlbabpss
- getn 1
- calsour '0851+202' ➜ use both very strong sources as bandpass calibrators.
- refant 2
VLBABPSS will create a bandpass (BP) table:
AIPS 1: 'BP #1 BANDPASS TABLE'
Now check the bandpass solutions with POSSM.
- tget possm
- bpver=1; doband=1
Figure 3 shows the plots generated by POSSM. The solutions should look like a reasonable fit of the bandpass shape.
Apply Amplitude Corrections
Perform amplitude calibration by running VLBAAMP.
- default vlbaamp
- getn 1
Again, the procedure should finish with the following lines:
AIPS 1: 'SN #3 CONTAINS SAMPLER CORRECTIONS' AIPS 1: 'SN #4 CONTAINS GAIN CORRECTIONS' AIPS 1: 'CL #4 ADDS SAMPLER CORRECTIONS' AIPS 1: 'CL #5 ADDS GAIN CORRECTIONS'
which should be noted.
Examine Amplitude Calibration
Examine amplitude calibration by running SNPLT.
- default snplt
- getn 1
- dotv 1
- inext 'cl'
- invers 0
- opty 'amp' ➜ Plot amplitudes.
- nplots 10
- opco 'alsi' ➜ Plot all IFs and Stokes.
- do3col 1 ➜ Use 3-color symbols.
- tvin ➜ tvinitialize clears the tv before plotting. Otherwise you will get a mess as the table is plotted over the bandpass plot from before.
Figure 4 shows the amplitude gains change over time as the sources rise and set, with higher gains at lower elevations. The different IFs and polarizations (RR and LL in this case) are shown as different colors.
Correct Phases for Parallactic Angles
Correct phases for parallactic angle effects with VLBAPANG.
- default vlbapang
- getn 1
AIPS 1: 'CL #6 ADDS PARALLACTIC ANGLE CORRECTIONS'
Manually Edit Data
Edit the data using EDITR on each source separately.
- default editr
- getn 1
- docal 1; gainuse 0 ➜ calibrate data with highest CL table.
- crowded 1 ➜ to plot all polarization and IFs on top of each other.
- do3col 1
- doband 1
- bpver 1
- flagver 1
- outfgver 1
- antuse 1 2 3 4 5 6 7 8 9 10 ➜ to plot all the baselines to one antenna at the same time.
Run on one source at a time:
- source '0851+202''
Again look in you terminal window for intructions:
EDITR1: Press buttons A, B, or C to choose an operation EDITR1: Press button D for on-line help
EDITR plots both amplitudes and phases verses time, so this is a good way to just look at your data. For the inputs we chose all the polarizations and IFs are plotted on top of each other. The two boxes on the bottom plots these as different colors and shows the amplitude and phase for one baseline. The other boxes where the data is shown in green are the other baselines to that a single antenna. It is especially useful to look at the data this way because problems tend to be antenna based so all the baselines to an antenna will be effected. It you see potentially problematic data (especially high or low, or with bad phases (note that weak sources will have incoherent phases)) then you should wait to flag until you can see all the baselines to the other antenna in the baseline pair with the band data. That way you can flag once, telling EDITR to flag all the data to for one antenna (this is the default in EDITR, but can be changed). The data for this source looks great. Click "NEXT ANTENNA" found on the menu to the right and press "B" until you have looked at all the baselines on all the antenna for this source. At this point the data has been amplitude calibrated but the source amplitude changes from scan to scan, do you know the reason for this?
Now plot the other sources and inspect.
- source '1828+487''
1828+487 also looks pretty good, although there are some ratty amplitudes and phase on the last scan on baselines to antenna 10. We will just leave these for now because the final fringe fit and self-calibration might fix it.
- source '2200+420''
As you can see in Figure 5 this source the first scan on the baselines to antenna 10 looks bad. The amplitude is very low and the phases are noise. To flag this data click FLAG TIME RANGE and hit B (Figure 6), and a blue box appears in the 01-10 box on the bottom. By hitting A and moving the cursor move the sides of the box to encompass the data which needs to be flagged; then hit C. The data will be flagged on all the baselines to the antenna and will turn red in the display (Figure 7).
Fringe Fit the Data
Perform a global fringe fit with FRING. The following steps through imaging are not strictly necessary since we will have to redo them once the geodetic calibration is done, but is an excellent way to check the calibration up to this point is correct.
- default fring
- getn 1
- calsour '0851+202', '1828+487', '2200+420' ➜ do a global fringe fit on all sources.
- refant 2
- search 2 9 5 4 1 3 7 8 ➜ list of antennas to search if a solution is hard to find.
- solint 0.25
- doband 1
- bpver 1
- aparm(6) 2 ➜ print some information on solutions.
- aparm(9) 1 ➜ do exhaustive baseline search.
- docal 1; gainu 0
You should look at the number of good and failed solutions:
FRING1: Found 97646 good solutions FRING1: Failed on 1042 solutions FRING1: Adjusting solutions to a common reference antenna
You should get something similar but not necessarily exactly the same numbers of good and failed solutions. A small percentage of failed solutions are fine at this point. FRING will have created SN table number 5.
Note that if a model is not used (we are not using a model), FRING assumes that the source it is solving for is a point source at the phase center. None of these sources are point sources, therefore the corrections FRING found will not perfectly correct the data and once we apply all the calibration it will be necessary to do self-calibration with source models to get the best images. Also note that I said "at the phase center" so no matter what the the true position of your target this fringe fit will move brightest spot of the source to the phase center (the position of the target in the correlation).
Apply FRING solutions
Note that the previous step and this step can be done in the single procedure VLBAFRNG. It is broken up here just both to show the steps explicitly but also because running the tasks individually allows for more control. Here the global fring fit which was done in the last step is interpolated and applied to the all the calibration that has gone before with CLCAL.
- default clcal
- getn 1
- gainv 6 ➜ CL table with all the calibration.
- gainu 7 ➜ CL table to write next step of calibration in.
- snver 5 ➜ global fringe fit solutions from FRING
- interpol 'SELF' ➜ use 2PT interpolation.
- refant 2
- sour '0851+202', '1828+487', '2200+420' ➜ sources to which to apply calibration.
- calsour sour ➜ set calibrator sources to the same sources in parameter sources
So SN table #5 will be applied to CL table #6 and created CL table #7. CL table #7 now has all the calibration in it.
Backing up Your Calibration
We will want to save the calibration up to this point with TASAV. TASAV makes a new file with all your calibration tables, this is very useful because it contains everything you need to recalibrate your data in a very compact and portable form. It is also a good idea to do this before you do anything you are unsure about or will change important tables (AN, SU) in ways that are hard to change them back.
- default tasav
- getn 1
- outdisk 1
Lets look at our catalog again:
You should get something that look similar to:
AIPS 1: Catalog on disk 1 AIPS 1: Cat Usid Mapname Class Seq Pt Last access Stat AIPS 1: 1 193 BL193BG .UVAVG . 1 UV 01-JUL-17 14:28:24 AIPS 1: 2 193 BL193BG .TASAV . 1 UV 27-JUN-17 11:52:14
Note that you now have a second catalog entry which TASAV automtically named BL193BG.TASAV.1. This uv data file has 1 visibility and all the tables attached to BM272HC.UVDATA.1. Lets look at the TASAVed file.:
- getn 2
You should get something that looks like:
AIPS 1: Image=MULTI (UV) Filename=BL193BG .TASAV . 1 AIPS 1: Telescope=VLBA Receiver=VLBA AIPS 1: Observer=BL193BG User #= 193 AIPS 1: Observ. date=16-JUN-2016 Map date=27-JUN-2017 AIPS 1: # visibilities 1 Sort order TB AIPS 1: Rand axes: UU-L-SIN VV-L-SIN WW-L-SIN TIME1 SUBARRAY AIPS 1: SOURCE REMOVED INTTIM GATEID CORR-ID ANTENNA1 AIPS 1: ANTENNA2 AIPS 1: ---------------------------------------------------------------- AIPS 1: Type Pixels Coord value at Pixel Coord incr Rotat AIPS 1: COMPLEX 3 1.0000000E+00 1.00 1.0000000E+00 0.00 AIPS 1: STOKES 2 -1.0000000E+00 1.00 -1.0000000E+00 0.00 AIPS 1: FREQ 32 1.5240375E+10 17.00 1.0000000E+06 0.00 AIPS 1: IF 8 1.0000000E+00 1.00 1.0000000E+00 0.00 AIPS 1: RA 1 00 00 00.000 1.00 3600.000 0.00 AIPS 1: DEC 1 00 00 00.000 1.00 3600.000 0.00 AIPS 1: ---------------------------------------------------------------- AIPS 1: Coordinate equinox 2000.00 AIPS 1: Maximum version number of extension files of type HI is 1 AIPS 1: Maximum version number of extension files of type AT is 1 AIPS 1: Maximum version number of extension files of type CT is 1 AIPS 1: Maximum version number of extension files of type FQ is 1 AIPS 1: Maximum version number of extension files of type AN is 1 AIPS 1: Maximum version number of extension files of type CL is 7 AIPS 1: Maximum version number of extension files of type CQ is 1 AIPS 1: Maximum version number of extension files of type GC is 1 AIPS 1: Maximum version number of extension files of type IM is 1 AIPS 1: Maximum version number of extension files of type MC is 1 AIPS 1: Maximum version number of extension files of type PC is 1 AIPS 1: Maximum version number of extension files of type SU is 1 AIPS 1: Maximum version number of extension files of type TY is 1 AIPS 1: Maximum version number of extension files of type WX is 1 AIPS 1: Maximum version number of extension files of type SN is 5 AIPS 1: Maximum version number of extension files of type BP is 1 AIPS 1: Maximum version number of extension files of type FG is 1
Note that there is 1 visibility but 7 calibration (CL) tables and 5 solution (SN) tables. As well as numerous other tables with information about you data (history (HI), frequency (FQ), antenna (AN), system temperature (TY), bandpass (BP), flag (FG)...).
Apply Calibration and SPLIT the Data
Apply calibration and make single source data sets with SPLIT. I like to work with single source files, it's less confusing, especially when self-caling and imaging.
- default split
- getn 1
- freqid 0
- docal 1; gainu 7 ➜ apply calibration; from CL#2.
- sour '0851+202', '1828+487', '2200+420'
- doband 1; bpver 1
- aparm 2 0 0 0 1 1 ➜ aparm(1)=2 tells SPLIT to average all the channels in each IF, reducing the size of the data significantly.
This will produce three files named sourcename.SPLIT.1, again type uc to look at the catalog.
AIPS 1: Catalog on disk 1 AIPS 1: Cat Usid Mapname Class Seq Pt Last access Stat AIPS 1: 1 193 BL193BG .UVAVG . 1 UV 01-JUL-17 14:28:24 AIPS 1: 2 193 BL193BG .TASAV . 1 UV 03-JUL-17 15:01:55 AIPS 1: 3 193 2200+420 .SPLIT . 1 UV 03-JUL-17 15:12:12 AIPS 1: 4 193 0851+202 .SPLIT . 1 UV 03-JUL-17 15:14:41 AIPS 1: 5 193 1828+487 .SPLIT . 1 UV 03-JUL-17 15:15:29
Imaging and Self-Cal on 1828+487
Lets start by imaging 1828+487 with IMAGR. Either use the clean box files provided (make sure they are in the $FITS directory) or do interactive boxing. Using the supplied box file is easier. Note that I came up with the parameters below especially the IMSIZE, ROBUST, RASH and DECSH by imaging and experimenting.
- default imagr
- getn 5
- cell 0.0001; imsi 1024 512 ➜ cell size of 0.1 mas; image size of 512x512.
- rash -0.0125 0
- decsh 0.0125 0
- dotv 1
- robust 5 ➜ Do natural weighting. This source has a big diffuse jet, therefore sensitivity and more weight on the short spacings is more important than high resolution.
- niter 5000 ➜ do interactive clean; with 5000 iterations, you will probably "stop cleaning" before hitting 5000 on the first iteration of imaging.
- boxfile 'FITS:1828_1.box
Hit TVPSEUDO then "D" immediately to get color rather than grey scal. Figure 9 shows the dirty map. If you want to interactively clean, then click CONTINUE CLEAN (and "A"); after a few rounds of cleaning (about 350 clean components which the messages from IMAGR tell you) the residuals will look like Figure 10. You can see in Figure 10 there is not much else to clean inside the clean boxes although there is some flux outside the clean boxes it isn't significant enough to box at this point so click STOP CLEANING ("A"). IMAGR will return the cleaned map, Figure 11, as you can see there are artifacts in the map. Once IMAGR is done you can do a mcat (mc for short) to look at the maps in your catalog:
AIPS 1: Catalog on disk 1 AIPS 1: Cat Usid Mapname Class Seq Pt Last access Stat AIPS 1: 6 195 1828+487 .IBM001. 1 MA 04-JUL-17 10:33:14 AIPS 1: 7 195 1828+487 .ICL001. 1 MA 04-JUL-17 10:33:14
Note that you have made two file, a "dirty beam" (the IBM001 file) and a cleaned map (ICL001).
To look at the image use TVLOD (getn 6; tvin; tvlo). Use TVPSEUDO to put it into color (tvps). You can either use your mouse to manipulate the colors, again look at your terminal for instructions. Hit "D" once it looks the way you want.
So the image isn't the best there are some high frequency stripes and the noise is much higher than desirable. It looks like self-calibration would be beneficial. At some level self-cal is an art rather than a science, and there are various different philosophies concerning how to best do self-cal. I tend to be conservative, partially because VLBA data has fewer baselines and therefore it is easier to go off in a bad direction with the self-cal. However, these are fairly strong source so it will be harder to make big mistakes in the self-calibration. Self-cal is done by the task CALIB. Generally phase-only self-cal should be done first, the amplitude and phase. Also we will be using clean component models (i.e., the image we just made) for the self-calibration.
- default calib
- getn 5
- get2n 7 ➜ use clean components from this map as a model for the self-cal
- refant 2
- solint 1 ➜ 1 minute solution interval
- solty 'l1r' ➜ type of method for solution (see EXPLAIN CALIB for more details)
- solmo 'P' ➜ solve for phases only
You will get messages that look like this:
CALIB1: Task CALIB (release of 31DEC17) begins CALIB1: Using 1828+487 . SPLIT . 1 Disk= 1 Usid= 195 CALIB1: L1 Solution type CALIB1: UVGET: doing no flagging this time CALIB1: Create 1828+487 .CALIB . 1 (UV) on disk 1 cno 8 CALIB1: Selecting the data CALIB1: Using Clean Component self-cal source model CALIB1: FACSET: 1.381759 Jy found from 384 components CALIB1: Divide data by model - first compute model by summing CALIB1: QINIT: did a GET of 5120 Kwords, OFF 5243897 CALIB1: ALGMEM field 1 Ipol gridded model subtraction chns 1- 8 CALIB1: ALGMEM: at visibility number 1 CALIB1: ALGMEM: 1024 - 0 cells, with 23745 Pts CALIB1: Field 1 used 384 CCs CALIB1: Determining solutions using full vector averaging CALIB1: Writing SN table 1 CALIB1: Found 7424 good solutions CALIB1: Average closure rms = 0.03406 +- 0.00929 CALIB1: Fraction of times having data > 2.5 rms from solution CALIB1: 0.14370 of the times had 2 - 4 percent outside 2.5 times rms CALIB1: 0.13428 of the times had 4 - 6 percent outside 2.5 times rms CALIB1: 0.08716 of the times had 6 - 8 percent outside 2.5 times rms CALIB1: 0.11543 of the times had 8 - 10 percent outside 2.5 times rms CALIB1: 0.10718 of the times had 10 - 12 percent outside 2.5 times rms CALIB1: 0.07538 of the times had 12 - 14 percent outside 2.5 times rms CALIB1: 0.05300 of the times had 14 - 16 percent outside 2.5 times rms CALIB1: 0.04711 of the times had 16 - 18 percent outside 2.5 times rms CALIB1: 0.01885 of the times had 18 - 20 percent outside 2.5 times rms CALIB1: 0.01885 of the times had 22 - 24 percent outside 2.5 times rms CALIB1: 0.00353 of the times had 24 - 26 percent outside 2.5 times rms CALIB1: 0.00236 of the times had 26 - 28 percent outside 2.5 times rms CALIB1: 0.00236 of the times had 28 - 30 percent outside 2.5 times rms CALIB1: Applying solutions to data CALIB1: Previously flagged Flagged by gain Kept CALIB1: Partially 0 0 0 CALIB1: Fully 0 0 23745 CALIB1: Copied WX file from vol/cno/vers 1 5 1 to 1 8 1 CALIB1: Copied AN file from vol/cno/vers 1 5 1 to 1 8 1 CALIB1: Appears to have ended successfully
There are several things you should note in these messages:
- CALIB creates a new UV file called 1828+487.CALIB.1 at catalog number 8
- CALIB also writes an SN table attached to the input data file
- CALIB found 7424 good solutions and did not fail on any
- CALIB didn't flag any of the data. Since this is such a strong source CALIB probably will not flag any of the data. However for weaker sources this is a concern, a bad model and a weak source could mean that some portion of your input data is flagged by CALIB, meaning you can take your imaging to strange places if you are not careful.
Now we image the corrected data. We can either use the file that CALIB created or the original file applying the SN table that CALIB attached to it. Just for brevity we will use the file CALIB created:
- tget imagr
- getn 8
- boxfi 'FITS:1828_2.box
Create More Images
Image J2007+4029 and/or 20330+40003 with IMAGR to make sure phase referencing worked.
- default imagr
- getn 6 or 7
- bchan 0; echan 0; nchav 256; ➜ average all channels.
- cell 3e-5;imsi 2048 ➜ larger image size because sources might not be at center of field.
- im2parm 10 6 9 0.5 ➜ autoboxing again
- dotv 1; niter 1000 ➜ do interactive clean; with 1000 iterations.
Here I would check that the autobox looks OK (It should just be around the the obvious emission) and then hit TURN OFF DOTV ("A"). Figure 10 shows the end result of running IMAGR.
Now do an mcat to see the maps we have created:
AIPS 1: Catalog on disk 1 AIPS 1: Cat Usid Mapname Class Seq Pt Last access Stat AIPS 1: 8 1099 AFGL2591 .IBM001. 1 MA 14-APR-17 10:58:28 AIPS 1: 9 1099 AFGL2591 .ICL001. 1 MA 14-APR-17 11:02:50 AIPS 1: 10 1099 AFGL2591 .SQASH . 1 MA 14-APR-17 11:04:16 AIPS 1: 11 1099 J2007+4029 .IBM001. 1 MA 14-APR-17 11:14:05 AIPS 1: 12 1099 J2007+4029 .ICL001. 1 MA 14-APR-17 11:14:05
Then getn 12; tvin; tvlo; tvps.