Differences

This shows you the differences between two versions of the page.

--- en:convention [2017/01/11 18:18] – fluktuacia
+++ en:convention [2019/04/24 13:34] (current) – [Data structure] fluktuacia
@@ Line 1: / Line 1: @@
-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.
+This page contains proposal of conventions for stations' settings and operations within 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.
+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 [[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.
+From the perspective of structure at [[en:servers|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.
@@ Line 15: / Line 13: @@
 ===== 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.
+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 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.
+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 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.
+<WRAP center round important 80%>
+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.
+</WRAP>
 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.
+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 [[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.
+Example of name of data files: //TIME_NAME_TYPE.EXTE//
-  * TIME is
+The length of the file name is limited to 50 characters.
-  * je časový údaj s rozlišením alespoň ms, případně ns.
-  * NAME  je indentifikátor stanice a může mít délku do maximální povolené délky celého názvu. Název by měl obsahovat i verzi konfigurace stanice. Např. //RADIO-SVAKOV-R1//
-  * TYPE  je identifikátor dat, obvykle je "met", "raws", "snap" a tak dále podle typu zaznamenávaných dat
-  * EXTE je přípona souboru, označující jeho formát ([[http://cs.wikipedia.org/wiki/CSV|CSV]], [[http://en.wikipedia.org/wiki/FITS|FITS]])
-Podmínkou přispívání do databáze je splnění následujícího regulárního výrazu pro název souboru:
+  * 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 ([[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 required that the file name has a form of the 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})?
-Konkrétní příklady souborů:
+Examples of files:
   20140815131105154_OBSUPICE-R1_snap.fits
   20140815150803480_OBSUPICE-R1_raws.fits
@@ Line 49: / Line 51: @@
-==== Adresářová struktura na stanici ====
+==== Station's directory structure ====
-Adresářová struktura správně nakonfigurované stanice Bolidozor vypadá následovně.
+Directory structure of a correctly configured Bolidozor station looks as follows.
   User_Name
@@ Line 75: / Line 77: @@
   └── setup_reverse_tunnel.sh
-Všechna měřená data včetně metadat jsou ukládána do složky //bolidozor//. Ta obsahuje podsložku station, kde jsou v hierarchické adresářové struktuře uložena měřená data a v nejvyšším adresáři jsou společné meta datové soubory pro vnořená data.
+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** - Parametry stanice, umístění, poloha, verze HW. Tento soubor je potřebný pro export dat do sítě [[cs:rmob-export|rmob.org]].
-  * **Bolidozor.json** - Nastavení stanice a měření.
-Složka bolidozor tím pak částečně kopíruje datovou strukturu stanice na serveru [[cs:servers|space.astro.cz]].
+  * **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 the data structure of the station at [[en:servers|space.astro.cz]] server.
-===== K vyřešení =====
+===== Problems to solve =====
-==== Identifikace pozice stanice ====
+==== Identification of station's position ====
-Pozice stanic je potřeba označit jednoznačným identifikátorem. Jsou následující možnosti, jak to řešit:
+It is necessary to label the position of station by some unambiguous identification mark. There are several options:
   * Latitude, Longitude
   * [[http://en.wikipedia.org/wiki/Geohash|Geohash]]
-  * Lokátor
+  * Locator
-  * Adresa [[https://en.wikipedia.org/wiki/What3words|What3words]]
+  * Address [[https://en.wikipedia.org/wiki/What3words|What3words]]