[daip] PCCOR

[Leonia Kogan]

Enno,

I guess, you may make a mistake with PCCOR input parameter TIMERANG
If you use timerang=0,  you'll get your message
TIMERANG has to be specified (NO default).
This sentence is there (in the inputs list) with 3 signs !!!

LK




Enno Middelberg wrote:
> Dear Leonid Kogan,
>
>
> I am writing to ask a question about the Aips task PCCOR, which 
> appears to have been written by you. It doesn't work in my case and I 
> am trying to figure out why.
>
> The experiment is bm261, a 20cm VLBA-only observation of the CDFS. 
> Correlation has not been carried out in Socorro, but is currently 
> underway at the MPIfR in Bonn, using Adam Deller's software 
> correlator, DiFX.
>
> DiFX does not process any of the auxiliary data, so there are no TY, 
> GC, or PC tables attached to the data. However, these data exist in 
> http://www.vlba.nrao.edu/astro/VOBS/astronomy/jul07/bm261. I have 
> downloaded the file bm261cal.vlba and extracted the pulse cal 
> information using VLOG. I then used PCLOD to load the file and PCCOR 
> to process it.
>
> Unfortunately, whatever settings I use in PCCOR, it always aborts with 
> the same error, saying:
>
> REDGUM> PCCOR1: Task PCCOR  (release of 31DEC07) begins
> REDGUM> PCCOR1: Writing to SN table   7
> REDGUM> PCCOR1: All rows of the PC table are bad for the selected 
> parameters
> REDGUM> PCCOR1: Purports to die of UNNATURAL causes
> REDGUM> PCCOR1: redgum       31DEC07 TST: Cpu=       0.0  Real=       0
>
>
> I have tried various time ranges and fringe finder scans in PCCOR, to 
> no avail. I have also tried to understand how PCCOR selects "good" and 
> "bad" rows, looking at the source code, but my understanding of 
> FORTRAN and how Aips is structured is much too limited to get make any 
> conclusions.
>
> Can you make a guess why PCCOR is unable to process the PC table? What 
> does it check for and why does it reject all the data?
>
>
> Your help would be much appreciated.
>
>
> Best regards,
>
> Enno Middelberg
> Bochum, Germany