README - 2018/03/26 =================== Bug Unexpected size ------------------- In some cases, the first packet of science data in LOW mode, data_ID = 0 is uncomplete. In this directory, you will find the following files : * Files : 59 lines List of test data where packet LOW data_ID=0, can be found found in telemetry. * Files_with_bug : 16 lines List of test data were the first packet is uncomplete * Files_without_bug : 43 lines List of test data were the bug was not found. The first packet has sometimes an unexpected size of 1148 bytes / 1360. The MEA[12]_yyyymmdd.log files, contains the size of each science packets for LOW data ID = 0 Errors are indicated by : E : SCI.Parse_LOW_data_ID_0 : Unexpected size 1148 / 1360 Example : 1 : SDT.Reset_TI0_base : TI0 base = 2017-12-13T11:00:00.000000000 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1148 bytes) E : SCI.Parse_LOW_data_ID_0 : Unexpected size 1148 / 1360 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) 1 : SCI.Parse_SCI_data : Parse_LOW_data_ID_0 (1360 bytes) ... SPECIAL CASE : During the tests at ISAS on 2017/12/13 and 2017/12/15, we run several tests, with a reset between each one. We concatenate the resulting L0 data in a same source file, giving an artificial timetag for each one (11H, 12H, 13H...) We can find the same bug after each reset....