Menu

#88 Digifil giving fake telescope ID by default for filterbanks

version_2.0
closed-fixed
None
5
2020-12-15
2020-06-10
No

On trying to merge filterbanks , the current digifil script gives the telescope ID as Fake be default. For example I run,
digifil /beegfs/DATA/TRAPUM/SCI-20180923-MK-01/20200416-0004/20200416_005928-merged/cfbf00000/*.fil -threads 15 -b 8 -o test1.fil

All the input files have the MeerKAT ID. But running a header on test1.fil gives:

Data file : test1.fil Header size (bytes) : 352 Data size (bytes) : 1443889152 Data type : filterbank (topocentric) Telescope : Fake Datataking Machine : ????? Source Name : J1748-2446A Source RA (J2000) : 17:48:02.3 Source DEC (J2000) : -24:46:36.9 Frequency of channel 1 (MHz) : 1711.791016 Channel bandwidth (MHz) : -0.208984 Number of channels : 4096 Number of beams : 0 Beam number : 0 Time stamp of first sample (MJD) : 58955.041275779804 Gregorian date (YYYY/MM/DD) : 2020/04/16 Sample time (us) : 76.56075 Number of samples : 352512 Observation length (seconds) : 27.0 Number of bits per sample : 8

Discussion

  • Prajwal V Padmanabh

    Digifil telescope ID issue

     

    Last edit: Prajwal V Padmanabh 2020-06-10
  • Andrew Jameson

    Andrew Jameson - 2020-12-15
    • status: open --> closed-fixed
    • assigned_to: Andrew Jameson
     
  • Andrew Jameson

    Andrew Jameson - 2020-12-15

    This has been fixed in commit #73757a. Running digifil on search mode data recorded with PTUSE now results in telescope_id 64 being set in the resulting output file:

    [ajameson@farnarkle1 ~/dspsr]$ header 2020-11-28-03:22:13.fil
    ...
    Telescope                        : MeerKAT
    Datataking Machine               : FAKE
    ...
    
     

    Last edit: Andrew Jameson 2020-12-15

Log in to post a comment.

MongoDB Logo MongoDB