The data produced by the detection stations are sent to the main data server running a JS9browser tool. It enables to view the visual portion of the data. Statistical data are available on Bolidozor RealTime web.
There are several types of files among the data records:
JS9 web viewer enables viewing only the first two records. A specialised application is required to see the rest of the records. The description of how the data files are sorted can be found on directory convenctions webpage. All the time records are stored either as Unix time or UTC.
The records are generated by a software running on the detection stations. Majority of data are produced by Radio-observer software. Other auxiliary meta-data outputs are generated by a software maintaining an integrity of data flow from the stations.
In our case:
The radar emitting frequency corresponds to the vertical intersected with the average positions of the meteor trails. This signal is static and thus has almost entirely zero Doppler shift.
The lower portion of the record shows a head-echo - a signal, always beginning at higher frequencies than the meteor trail. Head-echo is a signal formed by the reflection from an ionised plasma at the front of the meteor during its fly-by. It is a moving object whose signal (due to a considerable speed up to tens of km/s) has a large doppler shift that passes through zero (at the point of the shortest sum of distances transmitter → meteor → receiver). Some meteors lack head-echo signal as the geometry of their fly-by does not allow the reflection to the receiver station. On the other side, other meteors have a head-echo extending even behind the point of the zero doppler shift.
Following on the area of the head-echo signal there is an area of a static reflection from the meteor trail. Its intensity varies in time. The change in intensity is caused by a progressive recombination of the plasma trail of the meteor and the periodic changes in intensity are caused by a space modulation of the radar signal.