All-Day Synthesis Issues: Difference between revisions

From EOVSA Wiki
Jump to navigation Jump to search
Line 64: Line 64:


=== CASA commands for accessing the data ===
=== CASA commands for accessing the data ===
The following commands give access to the ms as a table:
The following commands give access to a copy of the ms as a table:
  !cp -r /data1/eovsa/fits/UDBms/201806/UDB20180623.ms .
  !cp -r /data1/eovsa/fits/UDBms/201806/UDB20180623.ms .
  msfile = 'UDB20180623.ms'
  msfile = 'UDB20180623.ms'

Revision as of 18:48, 8 January 2022

Correcting for Solar Rotation

Deconvolving solar images integrated over a substantial period of time presents a complex challenge due to at least two effects:

  • Solar rotation: Sources near disk center are carried from east to west at a rate of about 9 arcsec/hour. Those nearer the limb move very little in the plane of the sky. The rate of rotation is also latitude dependent due to differential solar rotation. This solar-rotation issue is made far more serious by the fact that the psf (point-spread-function, aka synthesized beam) also varies with time.
  • Intrinsic variations versus time: Even without actual flaring, evolution of active region sources in shape and or brightness can occur. In applications not involving aperture synthesis, such evolution is simply averaged out in the familiar way. However, when coupled with the changing psf due to solar rotation these intrinsic variations present a more serious challenge.

One way to overcome these problems, when reasonably good uv-coverage is available, is simply to make images over a shorter time (e.g. 10 min, during which the rotation is less than 2 arcsec), then differentially rotate the images and average them in the image plane. There is some relatively minor problem in doing this, since the emission is distributed at varying heights and one must generally choose a reference height at which to do the rotation. Luckily, the emission near the limbs does not move in the plane of the sky, and so it is not a bad approximation to rotate emission on the disk and leave the emission above the limb unchanged. This "shorter-integration-time" approach is worthwhile with EOVSA when there is relatively bright active region emission that is the focus of the science study, but the fainter disk or off-limb emission is not well imaged in such short integrations.

In cases where all of the emission is weak, long integrations with EOVSA are required, and this page describes an alternative method for improving image deconvolution in that case. This approach involves creating a spatially variable psf, and hence deconvolving model sources in various parts of the solar disk with the appropriate psf for that location. Software does not yet exist for the entire process, but some exploration is possible with the current software.

Description of the Problem

If solar rotation is ignored in an 8-hour integration, say, then sources near disk center will shift 72 arcsec! If the standard psf is used to clean such sources, two errors result: (1) the source is smeared in the east-west direction, appearing larger and fainter than it should, and (2) the psf sidelobes used in the deconvolution are not those created by the moving source, so much larger residuals (and possibly false sources) are left in the image.

If the correct psf could be calculated and used, however, then applying it would reduce the residuals. Additionally the smearing of the source could be eliminated by restoring with the ideal psf core, which would also restore the true brightness. The problem, though, is that the correct psf varies with location on the solar disk.

Calculating the Correct PSF

No matter the shape of the source, assuming for now that it does not evolve with time, the smeared source is a convolution of the true source with an evolving psf that is created by changing uv sampling function of the array. In calculating the standard psf, the "point" in the point-spread-function is considered to be a unit amplitude point source at the phase center (amplitude 1, phase 0). If instead we consider a moving point source (amplitude 1, but shifting phase) when calculating the sythesized beam, then this would create a psf appropriate to that source. This amounts to creating a model visibility database with unit amplitudes, but properly calculated phases.

Consider the case of a time-dependent shift of the point source in RA and Dec, . The phase shift to be applied to a uv point with coordinate is (see Lecture 9, eqn 3). Thus, the visibility to be calculated is just .

A complication, of course, is that the psf so calculated is valid only for a source that follows the assumed time-dependent shift, hence it varies with position on the solar disk. A full solution to this problem would be to calculate a different psf for every point in a radio image and then during each step of the cleaning process select the psf corresponding to the position of a particular clean component. An alternative that might be good enough is to divide the solar disk into a finite number of segments, identify which of a selected number of psfs is most appropriate to that location, and apply that psf.

An Initial Test of the Idea

At present, there is no CLEAN deconvolution software capable of applying a spatially variable psf. However, the CASA tclean task allows a parameter calcpsf=False. This will then cause tclean to use an existing psf instead of calculating it. Thus, a valid test of the idea might be to select a date when there is a rather bright active region at some heliographic latitude and longitude on the disk, calculate the time-dependent RA, Dec coordinates, and then create a model visibility database that is the same as the MS of the date, but whose visibilities are replaced by with calculated as above. An image with zero clean iterations will then form the point-spread-function required. The task tclean can then be run on the original data with calcpsf=False, and with a restoring beam specified as the unsmeared psf.

Selection of date

A good date that I have already explored is 2018 Jun 23, which has a relatively strong active region source at heliocentric coordinates (x, y) = (290, 103). This has to be converted to heliographic coordinates for a specific time (e.g. 2000 UT). The result (using IDL arcsec2helio procedure) is (lat, lon) = (8.169, 18.009) degrees (N and W). Then the rotation has to be calculated, which I did (using IDL track_h2a procedure) to get (once per hour):

Heliocentric X, Y offsets
 UT        X (arcsec)      Y (arcsec)
16:00      251.60518       102.46113
17:00      260.93304       102.47842
18:00      270.23273       102.49959
19:00      279.50323       102.52464
20:00      288.74353       102.55360
21:00      297.95264       102.58646
22:00      307.12958       102.62324
23:00      316.27335       102.66396
24:00      325.38297       102.70862

These coordinates have to be rotated for the P-angle (354 deg on this date), which gives:

Geocentric X, Y offsets
 UT        X (arcsec)      Y (arcsec)
16:00      239.517         128.200
17:00      248.792         129.192
18:00      258.038         130.185
19:00      267.255         131.179
20:00      276.442         132.174
21:00      285.597         133.169
22:00      294.720         134.165
23:00      303.809         135.161
24:00      312.865         136.158

and finally converted to . Note that absolute coordinates are not needed, only the relative shift vs. time. Thus, to a good approximation, this is just and , where = (276.442,132.174) is the coordinate at 20:00 UT, and = 23.42 is the declination of the Sun. This gives the following final result:

RA/Dec shifts relative to 20:00 UT
  UT        dRA         dDec
16:00     40.1859     -3.97398
17:00     30.0920     -2.98175
18:00     20.0289     -1.98862
19:00      9.9979     -0.99468
20:00      0.0000      0.00000
21:00     -9.9637      0.99529
22:00    -19.8921      1.99112
23:00    -29.7841      2.98740
24:00    -39.6388      3.98402

The above hourly positions can be interpolated to finer timescales.

CASA commands for accessing the data

The following commands give access to a copy of the ms as a table:

!cp -r /data1/eovsa/fits/UDBms/201806/UDB20180623.ms .
msfile = 'UDB20180623.ms'
tb.open(msfile)
tb.browse()

The browser shows that there are columns for UVW, TIME, and DATA, which are the ones we need. We also need the list of frequencies from the SPECTRAL_WINDOW sub-table. One can then convert UVW in ns to U, V in wavelengths, interpolate the dRA and dDec to the relevant time, calculate for each time, and overwrite the data as . The resulting database can then be used to create images which will represent the psf of the smeared point source.