APID sequence flag
A bug has been found in APID sequence_flag for COMPRESSED PAS 3D data for both Burst mode and Snapshots.
This bug has been detected on data for 2019-06-19 and 2019-06-20.
PAS 3D snapshots
Data sequences are composed of :
96, 12, 21, 3, 202, "SWA_TM_SCI_PAS_TRIGG_SNAP_COMPR_START",
96, 12, 21, 3, 203, "SWA_TM_SCI_PAS_TRIGG_SNAP_COMPR_FIRST",
96, 12, 21, 6, 204, "SWA_TM_SCI_PAS_TRIGG_SNAP_COMPR_DATA",PAS 3D burst mode
Data sequences are composed of :
98, 12, 21, 3, 208, "SWA_TM_SCI_PAS_TRIGG_CBURST_COMPR_START",
98, 12, 21, 3, 209, "SWA_TM_SCI_PAS_TRIGG_CBURST_COMPR_FIRST",
98, 12, 21, 6, 210, "SWA_TM_SCI_PAS_TRIGG_CBURST_COMPR_DATA",Description
A normal sequence is composed by:
-
a first 3D packet of type START giving the number of samples = N
Then a sequence 1..N composed by:
-
an unique packet of type FIRST that describe the following 3D data content
-
an unique packet or a sequence of packets of type DATA
Packet of type START or FIRST have an APID sequence_flag = 3 (unique packet sequence)
Packets ot type DATA can be :
-
unique with sequence_flag = 3
-
a sequence of packets with sequence_flag = [1, 0, 0, …, 2]
where 1 : start of sequence, 0 : middle of sequence, 2 : end of sequence
|
Bug
For SID = 204 and 210, we could just find DATA packet with sequence_flag = 1 |
See SID = 204
See SID = 210
