Bolidozor wiki

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)//

====== Bolidozor network conventions ======

This page contains proposal of conventions for stations' settings and operation in Bolidozor network.

===== Observatory =====

In the context of Bolidozor 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 [[en:servers|data storage]], an observatory is a place that store 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.

===== Stations =====

In the context of 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 is the station located. The suffix RX is the 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 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 no other types of radio stations apart from [[en:rmds|RMDS]] in Bolidozor networ, such differentiation has not been implemented yet.

==== Data structure ====

Examples of names of data files //TIME_NAME_TYPE.EXTE// The length of the file name is limited to 50 characters.

* TIME represents timestamp with resolution at least ms or ns  
  * NAME represents the station id and can have a length of the 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 formate ([[https://en.wikipedia.org/wiki/Comma-separated_values|CSV]], [[http://en.wikipedia.org/wiki/FITS|FITS]])

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

({0-9}{4})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{3})([A-Z]{1})?_[A-Z0-9]{1,20}(_([A-Z0-9]{1,4}))?(\.[0-9a-zA-Z]{1,4})?
  
Examples of files:
  20140815131105154_OBSUPICE-R1_snap.fits
  20140815150803480_OBSUPICE-R1_raws.fits
  20140815150948269_OBSUPICE-R1_met.fits
  20131215115954558_SVAKOV-R2_fb.jpg
  20131215115955002_SVAKOV-R2_nomet.jpg
  20140808100000_OBSUPICE-R1_meta.csv

==== Station's directory structure ====

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

User_Name
  ├── bolidozor
  │   ├── radio-observer.log
  │   └── station
  │       ├── Bolidozor.json
  │       ├── bus_config.py
  │       ├── rmob.cfg
  │       ├── data
  │       ├── meteors
  │       └── snapshots
  ├── repos
  │   ├── pymlab
  │   ├── pysdr
  │   ├── python-mlab-utils
  │   ├── radio-observer
  │   ├── data-uploader
  │   ├── sdr-widget
  │   ├── signal-piping-tools
  │   └── station-supervisor
  ├── resize_fs.sh
  └── setup_reverse_tunnel.sh
  
All measured data, including metadata, are stored in //bolidozor// directory. This directory has a subdirectory called station that contains recorded data in a hierarchic directory structure. The uppermost directory contain 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 [[en:rmob-export|rmob.org]] network.
  * **Bolidozor.json** - Configuration of station and measurements.

Bolidozor directory thus partially copies data structure of the station at [[en:servers|space.astro.cz]] server.

===== Problems to solve =====

==== Identifikace pozice stanice ====

Pozice stanic je potřeba označit jednoznačným identifikátorem. Jsou následující možnosti, jak to řešit:

* Latitude, Longitude
  * [[http://en.wikipedia.org/wiki/Geohash|Geohash]]
  * Lokátor
  * Adresa [[https://en.wikipedia.org/wiki/What3words|What3words]]

Please fill all the letters into the box to prove you're human. M B O Q L Please keep this field empty:

Edit summary

Note: By editing this page you agree to license your content under the following license: GNU Free Documentation License 1.3