This page was last updated on
2015 Jun 19 10:56 MDT
to keep track of known problems that affected data taken with the
VLA/EVLA and/or the VLBA that appears and is remaining either in the
data archive, or in the programs reading the data archive into the
data reduction packages. For current problems that are affecting
current data, and thus also are not fixed in the data archives and
data readers, check the VLA
Proposers/Observers/Data reduction
page.
If you cannot find the answer, have additional
concerns or want to point out a new problem, please use the NRAO Helpdesk.
Note that you may have good data that appears to have problems. Over the years bugs have been discovered and corrected in AIPS. Please make sure you have a reasonably recent version of AIPS, especially if you are dealing with data during the period of transition from VLA to EVLA to Karl G. Jansky Very Large array (VLA) and thereafter. The same holds for the CASA (formerly AIPS++) data reduction package.
Unfortunately this page remains a work in progress as new and old issues are found continuously. Of course if you know of an unlisted problem (which isn't unlikely as we've just started this page from our faded memories), suspect one, or have another question please contact the NRAO Helpdesk using your my.nrao.edu login.
Use these links to skip the introduction and jump to the list of (E)VLA or VLBA archive issues directly.
The following figure shows an example of a time line of three specific issues. The header on top shows the time line labeled in years. The first column contains an issue number that corresponds to issue numbers in the (long) listing below. To asses your data, find the appropriate (VLA or VLBA) time line below and draw a vertical line at the date of your data. Check each issue number for which your line crossses the corresponding issue line (and also the ones that start just after..). To be conservative, the lines include the whole month in which the issue appears; check the issue descriptiton for the exact dates and times.
'01 | '02 | '03 | '04 | '05 | '06 | '07 | '08 | '09 | '10 | '11 | '12 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
20 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
19 |
For example, if you download data from 2006, you need not to look at issue number 21, 20, nor 19. However, if your data is from 2008 you need to check issue #21 and can ignore issues #20 and #19. Similarly, if your data is from the end of 2002, you can skip issue #21 but need to study issue #19. And because issue #20 has been found just after your data was taken, it might be a good idea to check issue #20 too as is may be in your data and we don't know about it (in which case you should contact us through the NRAO Helpdesk using your my.nrao.edu login)!
Known problems are listed in reverse issue number, which over due time will become a random order of (approximate) starting date, separated for (E)VLA and VLBA issues (some may be listed under both if applicable). However, as some issues may not be related to the data, but to the data readers themselves, you may want to read the general reader (FILLM or FITLD) issues first. If your data includes EVLA antennas (as may be the case for data between 2005 and 2013), you should also check the EVLA returns page.
Now that you have your list of specific issues you have to check, you should do the following; remember that the time line is conservative in that it includes whole months, and that you also might be interested in issues that start just after your vertical data line.
If your data is from before the red "Begin" date or after the green "End" date, you should be fine for the specific issue listed. Also if you download any data after the blue "Archive fixed?" date, you should not be affected anymore by that specific issue. More exact begin and end times on the dates are given in the section describing the issue, which you can get at by clicking the link.
If your data is from between the red "Begin" and the green "End" date, and you obtained the data before the blue"Archive fixed?" date (either from an archive download, an on-line FILLM, or by any other means such as from your collaborator ...), your data may be affected! Because specific issues may only affect certain data, the "Notes" column should indicate under which circumstances the data is affected. Note that the "Archive fixed?" column is only given for the purpose of determining whether you should pay attention to the issue description below; it is not intened to give you a clue about whether we will (or even can) fix the archive or not if it says "not fixed".
The flow diagram on the right hand side of this page should help to determine how to deal with a specific issue; click on the image for a more readable version.
# | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 1020 | | | = | | | | | | | | | | 1019 | | == | | | | | | | | | | | 1018 | | = | | | | | | | | | | | 1017 | =|=== | | | | | | | | | | | 1016 | =|== | | | | | | | | | | | 1015 |==========>>| | | | | | | | | | | | 1014 | = | | | | | | | | | | | |
# | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 1013 | | | | | | | | | | | | == | 1012 | | | | | | | | | | | | == | 1011 | | | | | | | | | | ==========|=======-----|---- | 1010 | | | | | | | | | | | =|= | 1009 | | | | | | | | | | | ====| | 1008 | | | | | | | | | | | = | | 1007 | | | | | | | | | | | = | | 1006 | | | | | | | | | | | = | | 1004 | | | | | | | | | | = | | | 1002 | | | | | | | | | =|============|====> | | 1003 | | | | | | | | | =|============|====> | | 1001 | | | | | | | | | ===> | | | | 019 | | | | | | | | | | ==========|====>> | | 018 | | | | | | | | | =======|= | | | 017 | | | | | | ?=|============|============|============| | | | 016 | | | | | | | | | = | | | | 015 | | | | | | | | | = | | | | 003 | | | | | | | | |=== | | | | 004 | | | | | | | | ?== | | | | | 005 | | | | | | | |= | | | | | 009 | | | | | | | = | | | | | | 006 | | | | | | | == | | | | | | 008 | | | | | | | === | | | | | | 007 | | | | | | | === | | | | | | 002 | | | | | | | == | | | | | | 014 | | | | | | | =======|============|============|==>> | | | 013 | | | | | | | =======|============|?? | | | | 011 | | | | | | ??======|============|==== | | | | | 012 | | | | | | ??======|=== | | | | | | 001 | | | | | | ??== | | | | | | | 010 |============|============|============|============|============|============|====== | | | | | |
# | 1989 | 1990 | 1991 | 1992 | 1993 | 1994 | 1995 | 1996 | 1997 | 1998 | 1999 | 2000 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 010 |============|============|============|============|============|============|============|============|============|============|============|============|
# | 1977 | 1978 | 1979 | 1980 | 1981 | 1982 | 1983 | 1984 | 1985 | 1986 | 1987 | 1988 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 010 |============|============|============|============|============|============|============|============|============|============|============|============|
General AIPS FILLM (and FILLR) issues | ||||||
Check the EVLA returns page, last updated on 2015 June 19 | ||||||
Specific (E)VLA archive issues: | ||||||
# | Begin | End | Archive fixed? | Issue (follow links) | Notes | |
001 | 2006 Jul/Aug | not fixed | First EVLA antennas | |||
002 | 2007 Jun 28 | 2007 Jul 29 | fixed | Wrong u,v, and w coordinates | TWO separate issues | |
003 | 2009 Jan 14 | 2009 Mar 08 | not fixed | Timing error | Data taken on Fri (UT) | |
004 | 2008 Mar/Apr | 2008 May | not fixed | Online flagging | ||
005 | 2008 Jan 04 | 2008 Jan 24 | not fixed | IAT clock error | ||
006 | 2007 Jul 30 | 2007 Sep 20 | 2008 Apr 22 | Sideband issue | All line data | |
007 | 2007 Jun 28 | 2007 Aug 21 | not fixed | System Temperature | Antennas 11 and 19 | |
008 | 2007 Jun 29 | 2007 Aug 29 | not fixed | Pointing error | Antennas 1 to 9 | |
009 | 2007 Sep 14 | 2007 Sep 19 | 2007 Sep 24 | Frequency increment | ||
010 | 1979 Jun | 2007 Jun 29 | not fixed | (u,v,w) error | ||
011 | 2006 | 2008 Apr 09 | not fixed | Doppler tracking | EVLA antennas | |
012 | 2006 | 2007 Mar 02 | not fixed | Mozaicing error | EVLA antennas | |
013 | 2007 Jun 27 | 2008 ?? | not fixed | 25 MHz BW problem | ||
014 | 2007 Jun 27 | not fixed | 12.5 MHz noise | |||
015 | 2009 Mar 10 | 2009 Mar 19 | not fixed | Phase jumps | EVLA antennas | |
016 | 2009 Nov 17 | 2009 Nov 20 | not fixed | Tsys/Timing error | ||
017 | 2006 Dec | 2009 Dec 18 | not fixed | Wrong Doppler calculations | dynamic time (J)observe files | |
018 | 2009 Jun 17 | 2010 Jan 10 | not fixed | Wrong Tsys in Ka band | 7 of the Ka antennas | |
019 | 2010 Mar 01 | not yet | not fixed | Bad Stokes V | ||
1001 | 2009 June 17 | 2009 fall | CASA | importasdm fails | ||
1002 | 2009 Dec 31 | not fixed | Scans missed | |||
1003 | 2009 Dec 31 | not fixed | BDFs missing | |||
1004 | 2010 May 22 | 2010 May 25 | not fixed | Bad data | ||
1006 | 2011 May 15 | 2011 May | not fixed | Clock problem | ||
1007 | 2011 Jul 28 | 2011 Aug 01 | not fixed | No SysPower | (not essential) | |
1008 | 2011 Jul 07 | 2011 Jul 11 | not fixed | Unstable IFs B,C | ||
1009 | 2011 Sep 20 | 2011 Dec 02 | not fixed | CBE integration failed | For Tint > 1 sec | |
1010 | 2011 Dec 23 | 2012 Jan 12 | not fixed | Weather data | Opacity corrections | |
1011 | 2010 Mar 01 | 2012 Apr (2011 Aug) | not fixed | Spectral splatter | spectral artifacts at high SNR | |
1012 | 2012 May 15 | 2012 Jun 15 | 2012 Jun 22 | OnLine Flags | too much online flagging | |
1013 | 2012 Jun 07 | 2012 Jul 24 | not fixed | BD tuning | ||
1014 | 2013 Feb 05 22UT | 2013 Feb 11 20UT | not fixed | Timing error | ||
1015 | 2013 Jan 20 | not fixed | Incomplete data | not suitable for pipelining | ||
1016 | 2013 Dec 20 | 2014 Feb 14 | not fixed | Slewing flags | "QUACK" data | |
1017 | 2013 Dec 12 | 2014 Mar 11 | not fixed | Requantizer | 3-bit: "QUACK" data | |
1018 | 2014 Apr 09 | 2014 Apr 09 | not fixed | CMIB | disregard data | |
1019 | 2014 May 29 | 2014 Jun 19 | not fixed | P band | use Stokes I | |
1020 | 2015 Jun 02 | 2015 Jun 11 | pending | CBE averaging | wait for fix |
# | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 506 | ====|= | | | | | | | | | | |
# | 2001 | 2002 | 2003 | 2004 | 2005 | 2006 | 2007 | 2008 | 2009 | 2010 | 2011 | 2012 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------| 505 | | | | | | | | | =|== | | | 504 | | | | | | | | | === | | | | 501 | | | | | | | |= | | | | | 502 | | | ===|============|======== | | | | | | | | 503 | | | ========|============|======== | | | | | | | |
# | 1989 | 1990 | 1991 | 1992 | 1993 | 1994 | 1995 | 1996 | 1997 | 1998 | 1999 | 2000 | JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND JFMAMJJASOND ----|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|------------|
General AIPS FITLD issues | ||||||
Specific VLBA archive issues: | ||||||
# | Begin | End | Archive fixed? | Issue (follow links) | Notes | |
501 | 2008 Jan 04 | 2008 Jan 18 | not fixed | Weather table | ||
502 | 2003 Q4 | 2005 Aug 15 | fixed 2005 Aug 15 | Phased Array Sensitivity | Phased array only | |
503 | 2003 May | 2005 Aug 08 | not fixed | EOP errors | ||
504 | 2009 Sep 21 | 2009 Nov 26 | fixed 2010 Jan 03 | AN file error | preprocessed archive files only | |
505 | 2009 Dec 23 | 2010 Feb 01 | not fixed | Clock errors | few DiFX projects | |
506 | 2013 Nov | 2014 Jan | not fixed | sensitivity and cable swap | KP | |
AIPS task FILLM issues: | |
---|---|
Occasionally coding updates to FILLM introduced bugs. | |
Problem start: 1970 | |
Problem fixed: | |
Archive fixed: | |
Workaround: Not readily available; reload data. | |
Last update: Monday, 09-Mar-2009 11:30:41 MDT by L.O. Sjouwerman | |
Please read the
AIPS letter
or check the AIPS
AIPS patches.
Alternatively
search
the history of the current version (CHANGE.DOC) for
FILLM
to see if you are affected. If so and you have an old version of
AIPS, please
reinstall
a more recent version or if you are current, run the
MidNightJob
| |
Back | |
1 : EVLA antennas included in the array. | |
---|---|
First few EVLA antennas in the array. | |
Problem start: 2006 July/August | |
Problem fixed: | |
Archive fixed: | |
Workaround: For problems with the first few EVLA antennas, delete the data taken with these 1-3 antennas. | |
Last update: Friday, 24-Apr-2009 15:45:42 MDT by L.O. Sjouwerman | |
As of 1 August 2006, all regular observing programs were given the
EVLA antennas that had returned to operations (earlier for test
programs). They are expected to give reasonable data most of the
time, but the early days of the transition may have introduced bad
performance or unexpected artifacts at the few EVLA antennas in
the array. Probably the best and easiest solution is to delete the
few visibilities observed with these antennas. Note that the EVLA
antennas prior to the C array of 2006 have no antenna positions.
| |
Back | |
2 : Post-MODCOMP uvw errors | |
---|---|
New control software calculated u,v, and w coordinates wrongly. | |
Problem start: 2007 June 28 | |
Problem fixed: 2007 July 5 | |
Archive fixed: 2007 August 1 | |
Workaround: Reload data from the archive or run UVFIX on the data. | |
Last update: Friday, 01-May-2009 15:12:51 MDT by L.O. Sjouwerman | |
This item relates to TWO similar issues in this time range The MODCOMP computers that have run the VLA for many years were replaced by the EVLA monitor and control system on June 28, 2007. We have discovered that from that time until July 5, 18:20 UT, the u's v's and w's were written to the VLA data archive with the wrong sign. The data in the archive were corrected on July 10, 16:00 UT. A problem with the online calculation of negative u's, v's, and w's has been discovered for all data taken since the VLA's MODCOMP computers were replaced by the EVLA monitor and control system on June 27, 2007. All astronomical projects observed between June 28, 2007, 09:00 UT, and August 1, 2007, 23:45 UT, are affected. (Note that this problem is separate from the uvw sign error that affected data between June 28 and July 5.) Projects affected: AB1233, AB1239, AB1245, AB1246, AB1248, AB1251, AB1254, AB1256, AB1257, AB1278, AC856, AC874, AC879, AC888, AD562, AF452, AF456, AG744, AG745, AG753, AG756, AH939, AJ337, AK634, AK656, AL693, AL698, AM889, AM902, AM904, AM910, AN129, AR637, AR638, AR642, AR646, AS887, AS899, AS903, AS911, AT342, AT343, AT345, AW703, AY178, BB240, BC173, S8398, S8463, S8531, S8723, STUDE1, STUDE2 | |
Back | |
3 : Timing error | |
---|---|
EOP applied incorreclty | |
Problem start: 2009 January 14 | |
Problem fixed: 2009 March 08 | |
Archive fixed: | |
Workaround: (algorithm currently investigated) Make-up observations have been arranged. | |
Last update: Thursday, 23-Apr-2009 17:33:38 MDT by L.O. Sjouwerman | |
The VLA observations below were afflicted with a time error of
about a second, due to improper application of the Earth Orientation
Parameters. A time-correction scheme with the AIPS task CLCOR is not yet
available, but may eventually become available (the archive data
will not be fixed).
Affected data: StartIATDate-Time Code 2009-03-01 00:00 AM978 2009-02-28 23:06 AM978 2009-02-28 21:05 AB1301 2009-02-28 20:06 AR685 2009-02-28 19:36 AB1321 2009-02-28 09:37 SA598 2009-02-28 07:38 AM975 2009-02-27 19:40 AE172 2009-02-21 21:03 ST001 2009-02-20 17:07 AB1314 2009-02-14 17:01 AH984 2009-02-14 16:31 AB1321 2009-02-14 11:58 AW743 2009-02-14 00:04 AG807 2009-02-13 23:33 AB1321 2009-02-13 22:03 AG807 2009-02-07 22:58 AB1320 2009-02-07 12:00 AK706 2009-02-06 23:01 AB1320 2009-01-31 13:27 AR687 2009-01-31 09:28 AM941 2009-01-30 20:28 AR685 | |
Back | |
4 : Online flagging erratic | |
---|---|
Online flagging not always properly applied | |
Problem start: 2008 March/April | |
Problem fixed: yes | |
Archive fixed: not fixed | |
Workaround: Carefull inspection of data | |
Last update: Thursday, 23-Apr-2009 16:47:27 MDT by L.O. Sjouwerman | |
During one day in March 2008 and a three-day period in April 2008, online
flagging was not always applied in all cases. The most common effect is
that antennas did not always get flagged while slewing between scans. We
recommend particular care while inspecting and editing data taken in those
time intervals.
Projects potentially affected by online flagging problems. Dates and times in UT. Project Date begin end Project Date begin end AG778 March 6 05:44 07:43 AM932 March 6 07:43 08:42 AM932 March 6 10:12 12:42 AR661 March 6 12:42 14:41 AM932 March 6 14:41 17:11 AE165 April 15 23:32 04:32 AS929 April 16 04:32 05:02 AS945 April 16 05:02 06:01 AE165 April 16 06:01 11:00 AH967 April 17 08:27 15:56 BM257 April 17 15:56 16:26 AB1285 April 18 00:25 09:23 AH868 April 18 09:23 10:53 AR642 April 18 10:53 11:53 AW710 April 18 11:53 12:53 AR642 April 18 12:53 13:52 AR642 April 18 14:22 15:22 AT360 April 18 15:22 21:21 | |
Back | |
5 : IAT clock error | |
---|---|
A clock timing error | |
Problem start: 2008 January 4 | |
Problem fixed: 2008 January 24 | |
Archive fixed: not fixed | |
Workaround: Project segments have been reobserved; or disregard EVLA antennas. | |
Last update: Friday, 24-Apr-2009 15:38:48 MDT by L.O. Sjouwerman | |
An error occurred in the setting of the clock that drives the
VLA antennas and the VLA correlator, affecting all astronomical data
obtained between Jan 4, 02:18 IAT, and Jan 7, 18:04 IAT, and on Jan 24
(during AH927). The time error
was sufficiently small (~50 ms) that the effect on VLA observations is
negligible. However, the EVLA antennas, which do not use that clock, were
out of sync with respect to the VLA correlator during that time interval.
The effect of this out-of-sync condition is that: - VLA-EVLA baselines have reduced sensitivity and calibration difficulties - EVLA-EVLA baselines have very large (~100%) closure errors For most purposes, the EVLA antennas will be unusable. The overall effect on your data will be a loss in sensitivity. Projects potentially affected by this: Jan 4 - Jan 7: AD574, AH884, AH927, AK678, AL695, AR642, AR650, AS887 Jan 24: AH927 | |
Back | |
6 : Conjugated phases | |
---|---|
Incorrect sideband being set for certain spectral line projects | |
Problem start: 2007 Jul 30 | |
Problem fixed: 2007 Sep | |
Archive fixed: 2008 Apr 22 | |
Workaround: Reload data from the archive or inspect data and use FLOPM with OPCODE'VLAE' | |
Last update: Thursday, 23-Apr-2009 17:20:53 MDT by L.O. Sjouwerman | |
For a limited time period during July-September 2007 the incorrect
sideband information was occasionally being set by the VLA
correlator for certain spectral line projects. The resulting effect
on data is that the direction of the frequency labelling was
reversed, and the phases were conjugated. A table of the
dates/times affected is given below, and one or more of your
observations were compromised by this problem. We are working on
fixing the data in the online archive, but it will take a few weeks
to complete. If you have already started processing your data there
is a new AIPS task FLOPM, available in the frozen 31DEC07 version of
AIPS, and in the development 31DEC08 version. Specifying
OPTYPE='VLAE' will reverse the frequency labelling and conjugate the
phases. The time range of data to be corrected must also be
specified explicitly.
Projects, frequencies, and IAT dates/times affected by frequency labelling and phase conjugation problem: AF456, X band: Jul 30 from beginning to end (C band is OK) AC856, L band: Sep 09 from 17:34:15.8 to end AC882, 4&P bands: Sep 01 from beginning to end AF440, L band: Sep 04 from 15:34:22.5 to 15:51:21 AK664, C band: Sep 07 from 05:46:32.5 to end AM889, L band: Aug 23 from 13:58:01.7 to end Aug 26 from beginning to 10:01:28 Sep 06 from 13:29:01.7 to 13:32:01 and from 14:00:01.7 to end Sep 12 from 11:54:51.7 to end AR659, L band: Sep 20 from 04:56:11.7 to end | |
Back | |
7 : Incorrect system temperature | |
---|---|
Nominal sensitivity and system temperature wrong for antennas 11 and 19 | |
Problem start: 2007 June 28 | |
Problem fixed: 2007 August 21 | |
Archive fixed: not fixed | |
Workaround: Reload data using a patched FILLM | |
Last update: Thursday, 23-Apr-2009 17:36:45 MDT by L.O. Sjouwerman | |
For data taken between June 27 and August 21 antennas 11 and 19 had
an incorrect nominal sensitivity and system temperature stored with
the archival data. This can be identified by zeroes for the system
temperature in plots of Tsys in the TY table using SNPLT.
Unfortunately AIPS has not been calculating the weights for these
antennas correctly when loading the data using FILLM.
A patch dated September 28, 2007, is available for the 31DEC06 version of AIPS that handles this correctly. For the 31DEC07 version of AIPS, a midnight job run on September 22, 2007, or later is needed. You will need to update your version of AIPS and reload your data to obtain the correct weights for the affected antennas. Any flagging that has already been carried out is probably fine and FG tables can be copied directly to the new dataset using TACOP. Alternatively, if you already have fully calibrated data in a single source file, you can run WTMOD on that file with: NOISE=1; NOISE(11)=1/3; NOISE(19)=NOISE(11) Projects that may have been affected: AB1233, AB1239, AB1245, AB1246, AB1248, AB1250, AB1251, AB1254 AB1256, AB1257, AB1258, AB1278, AC843, AC856, AC874, AC879, AC881 AC884, AC888, AC908, AC909, AD562, AD565, AF452, AF456, AG744, AG745 AG752, AG753, AG756, AG757, AG777, AH939, AH941, AJ337, AK634, AK656 AL693, AL696, AL698, AL703, AM889, AM902, AM904, AM910, AN129, AO219 AO223, AR637, AR638, AR642, AR646, AS887, AS897, AS899, AS903, AS911 AS925, AT342, AT343, AT345, AU119, AW705, AY178, S8531 | |
Back | |
8 : Pointing errors | |
---|---|
Pointing solutions not applied to antennas 1-9 | |
Problem start: 2007 June 29 | |
Problem fixed: 2007 August 29 | |
Archive fixed: not fixed | |
Workaround: Not available. | |
Last update: Thursday, 23-Apr-2009 17:40:37 MDT by L.O. Sjouwerman | |
It was discovered that between the dates of June 27, 2007, and August
29, 2007 inclusive, reference pointing solutions were not being applied
to antennas numbered 1 through 9. The effect on your data will be
the following:
1) Pointing offsets may be different for your absolute flux calibrator from your phase calibrator and target source. Make sure you exclude antennas 1-9 when bootstrapping flux calibration using GETJY in AIPS, otherwise the absolute flux calibration will be highly uncertain. 2) The overall sensitivity may be somewhat lower than expected. 3) Extended sources may suffer from poor image fidelity if antennas with poor pointing are included. Projects that may have been affected: AB1233, AB1251, AB1258, AC843, AC879, AC884, AC888, AD565, AF452, AF454, AH941, AH942, AK634, AK656, AL698, AL703, AL704, AM910, AO219, AR642, AS887, AS897, AT342, AT343, AY178, BC173 | |
Back | |
9 : Incorrect VLA headers | |
---|---|
Incorrect frequency increment for spectral line data | |
Problem start: 2007 September 14 | |
Problem fixed: 2007 September 19 | |
Archive fixed: 2007 September 24 | |
Workaround: Reload data from the archive. | |
Last update: Friday, 24-Apr-2009 15:34:07 MDT by L.O. Sjouwerman | |
Due to an error in the EVLA online system, spectral line data taken
between September 13, 2007, and September 18, 2007, had incorrect
increments on the frequency axis. Rather than reporting the channel
width it instead reported the total bandwidth, or in some
cir
gipoco.com
is neither affiliated with the authors of this page or responsible
for its contents. This is a safe-cache copy of the original web site.
gipoco.com
is neither affiliated with the authors of this page nor responsible
for its contents. This is a safe-cache copy of the original web site.
|