Problem with running scan_set

[vlbi-jun-yang]

I try to do some recording tests at 16 Gbps. The data loss at the scan begining caused a problm with running mk5=scan_set?. See the error messages beblow. Is there a way to help JIVE5ab to know the recorded data rate and thus avoid the errors? Moreover, these errors seems to cause the connection timeout.

2023.129.18:08:05.06;mk5=record=on:froste_on_no0001
2023.129.18:08:05.08/mk5/!record=  0  ;
2023.129.18:08:06.03;mk5=evlbi?
2023.129.18:08:06.03/mk5/!evlbi? 0 : total : 202928 : loss : 17783 ( 8.06%) : out-of-order : 0 ( 0.00%) : extent : 0seqnr/pkt ;
2023.129.18:08:11.05;mk5=record=off
2023.129.18:08:11.65/mk5/!record=  1 ;
2023.129.18:08:11.65;mk5=evlbi?
2023.129.18:08:11.65/mk5/!evlbi? 0 : total : 1500307 : loss : 27933 ( 1.83%) : out-of-order : 0 ( 0.00%) : extent : 0seqnr/pkt ;
2023.129.18:08:11.65;fb=scan_set=froste_on_no0001_ds0:18h08m08.00s:18h08m09.00s
2023.129.18:08:11.72?ERROR m5 -900 /usr/local/src/jive5ab-issue25-cf592eb/src/mk5command/scan_set_vbs.cc@344 assertion [scr.trackbitrate!=headersearch_type::UNKNOWN_TRACKBITRATE] fails could not deduce recorded data rate for time based scan_set
2023.129.18:08:11.72/fb/!scan_set = 6 : /usr/local/src/jive5ab-issue25-cf592eb/src/mk5command/scan_set_vbs.cc@344 assertion [scr.trackbitrate!=headersearch_type::UNKNOWN_TRACKBITRATE] fails could not deduce recorded data rate for time based scan_set;
2023.129.18:08:11.72?ERROR m5 -906 Mark5 return code 6: inconsistent or conflicting request
2023.129.18:08:11.72;fb=disk2file=/data/froste_d2r_test_ds0.vdif:::w
2023.129.18:08:11.90/fb/!disk2file= 1 ;
2023.129.18:08:16.90;fb=scan_set=froste_on_no0001_ds1:18h08m08.00s:18h08m09.00s
2023.129.18:08:16.96?ERROR m5 -900 /usr/local/src/jive5ab-issue25-cf592eb/src/mk5command/scan_set_vbs.cc@344 assertion [scr.trackbitrate!=headersearch_type::UNKNOWN_TRACKBITRATE] fails could not deduce recorded data rate for time based scan_set
2023.129.18:08:16.96/fb/!scan_set = 6 : /usr/local/src/jive5ab-issue25-cf592eb/src/mk5command/scan_set_vbs.cc@344 assertion [scr.trackbitrate!=headersearch_type::UNKNOWN_TRACKBITRATE] fails could not deduce recorded data rate for time based scan_set;
2023.129.18:08:16.96?ERROR m5 -906 Mark5 return code 6: inconsistent or conflicting request
2023.129.18:08:16.97;fb=disk2file=/data/froste_d2r_test_ds1.vdif:::w
2023.129.18:08:21.98?ERROR m5 -104 mk5cn: time-out, connection closed, will reopen on next attempt

[haavee]

Hi Jun, could you do a few things for me?

• (re)run jive5ab -m 5 and capture the output
• send fb=version?
• send fb=scan_set=froste_on_no0001_ds0;
• send fb=scan_check?
• send output to me It seems the scan_check that is happening behind the scenes when you do scan_set= ... : <start> : <end>; is failing and I need to know why. The code should be perfectly capable of running scan_check? and give a sensible result.