User Tools

Site Tools

Translations of this page?:


Bolidozor network conventions

This page contains proposal of conventions for stations' settings and operations within Bolidozor network.


In the context of Bolidozor network an observatory represents a locality where there is a potential to realise more observations. Typical examples include private or public observatories.

From the perspective of structure at data storage, an observatory is a place that stores data from individual stations. At the present time, the data server login id is the same as the name of the observatory.

It is possible that in the future one observatory will have more user accounts.


In the context of the Bolidozor network a station is a defined measuring device. Different stations, each measuring different quantities, can therefore exist at one observation spot / Observatory.

Radio detection stations

Radio detection stations have a following name convention: Station-Observatory-RX, where the observatory corresponds to the name of observatory where the station is located. The suffix RX is an ordinal number of the station in the observatory. For example OBSUPICE-R4 means the 4th station for meteor detection at OBSUPICE observation spot.

The ordinal number increases at every change of the station configuration that may influence the recorded data - e.g. moving the antenna, changing cables, changing the configuration of detection software, changing the format of output data etc.

A special case is a station with R0 revision - it is reserved for test purposes and the data from R0 stations are not considered valid.

There are cases when there is possible to distinguish stations according to the type of measurement using a suffix in their names. However, as there are so far no other types of radio stations apart from RMDS in Bolidozor networ, such differentiation has not been implemented yet.

Data structure

Example of name of data files: TIME_NAME_TYPE.EXTE

The length of the file name is limited to 50 characters.

  • TIME represents a timestamp with resolution of at least ms or ns
  • NAME represents the station's id and can have a length of a maximum allowed length of the name. The name should also include version of the current station's configuration, e.g. RADIO-SVAKOV-R1
  • TYPE represents the data identification. It is usually 'met', 'raws', 'snap', etc. according to the type of the recorded data
  • EXTE represents file's suffix, denoting its format (CSV, FITS)

In order to contribute to the database it is required that the file name has a form of the following regular expression:


Examples of files:


Station's directory structure

Directory structure of a correctly configured Bolidozor station looks as follows.

├── bolidozor
│   ├── radio-observer.log
│   └── station
│       ├── Bolidozor.json
│       ├──
│       ├── rmob.cfg
│       ├── data
│       ├── meteors
│       └── snapshots
├── repos
│   ├── pymlab
│   ├── pysdr
│   ├── python-mlab-utils
│   ├── radio-observer
│   ├── data-uploader
│   ├── sdr-widget
│   ├── signal-piping-tools
│   └── station-supervisor

All measured data, including metadata, are stored in bolidozor directory. This directory has a subdirectory called 'station' that contains recorded data in a hierarchical directory structure. The uppermost directory contains shared metadata files for nested data.

  • rmob.cfg - Station's parameters, its location, position, HW version. This file is necessary in order to export data to network.
  • Bolidozor.json - Configuration of station and measurements.

Bolidozor directory thus partially copies the data structure of the station at server.

Problems to solve

Identification of station's position

It is necessary to label the position of station by some unambiguous identification mark. There are several options:

en/convention.txt · Last modified: 2019/04/24 13:34 by fluktuacia