Version as of 06:13, 16 May 2024

    to this version.

    Return to Version archive.

    View current version

    C212A Correlation Report

    Fringes

    Station Code Fringes Plots Comments
    Ef B yes    
    Pv P yes    
    On X yes    
    Ys Y yes    
    Mh Z yes    
    Br b yes    
    Fd f yes    
    La l yes    
    Nl n yes    
    Ov o yes    
    Kp k yes    
    Pt p yes    
    Mk m yes    
    Sc s     7mm only
    Hn h     7mm only
    Gb G yes   Problems with vdif thread offset
    Nn N yes    
    Ky y      
    Ku u yes    
    Kt t yes    

    Notes

    Ky: File /data/c212a/ky/c212a_KVNYS_274071501.vdif VDIF summary failed with return value -5

    Kt: File /data/c212a/kt/c212a_KVNTN_274070001.vdif VDIF summary failed with return value -5

    GBT issue with RCP polarization

    Issue: Strong GBT fringes in LCP found but detection in RCP (tested on scans 189 and 191).

    Diagnostics: Inspection of the VDIF structure shows 8 threads as expected, however the threads with odd IDs (representing LCP channels) are offset considerably (> 150 frames). The suspicion was that RCP frames get dropped by DiFX due to these gap sizes exceeding the read buffer sizesi (even though this seems unlikely because of the even-threaded data yields fringes). To check that the RCP data in principle is OK the following tests were done:

    • The v2d setup for GBT was split into two separate datastreams; one for LCP and one for RCP:

    DATASTREAM GBRCP
    {
        file=/data/c212a/gb/C212A_GB_No0762_RCP
        format=INTERLACEDVDIF/0:1:2:3/5032/2
    }
    DATASTREAM GBRCP
    {
        file=/mark6-06_fuse/1/C212A_GB_No0762
        format=INTERLACEDVDIF/1:3:5:7/5032/2
    }

    GBT: threads are offset. Fix with vmux?

    Fourfit plot with native 64MHz band stations e.g. BP show only USB channels (4 total instead of 8)

    Post-Correlation checks

    Residuals

    FITS completeness (pclist)