en:convention
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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 ====== | ====== Bolidozor network conventions ====== | ||
- | This page contains proposal of conventions for stations' | + | This page contains proposal of conventions for stations' |
===== Observatory ===== | ===== 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 |
- | From the perspective of structure at [[en: | + | From the perspective of structure at [[en: |
It is possible that in the future one observatory will have more user accounts. | It is possible that in the future one observatory will have more user accounts. | ||
Line 15: | Line 13: | ||
===== Stations ===== | ===== 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 ==== | ||
- | Radio detection stations have a following name convention **Station-Observatory-RX**, | + | Radio detection stations have a following name convention: **Station-Observatory-RX**, |
- | 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 | ||
+ | </ | ||
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. | 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: | + | 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: |
==== Data structure ==== | ==== Data structure ==== | ||
- | Examples | + | Example |
- | * 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ř. // | + | |
- | * TYPE je identifikátor dat, obvykle je " | + | |
- | * EXTE je přípona souboru, označující jeho formát ([[http:// | + | |
- | 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' | ||
+ | * TYPE represents the data identification. It is usually ' | ||
+ | * EXTE represents file's suffix, denoting its format ([[https:// | ||
+ | |||
+ | 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})? | ({0-9}{4})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{2})([0-9]{3})([A-Z]{1})? | ||
| | ||
- | Konkrétní příklady souborů: | + | Examples of files: |
20140815131105154_OBSUPICE-R1_snap.fits | 20140815131105154_OBSUPICE-R1_snap.fits | ||
20140815150803480_OBSUPICE-R1_raws.fits | 20140815150803480_OBSUPICE-R1_raws.fits | ||
Line 49: | Line 51: | ||
- | ==== Adresářová struktura na stanici | + | ==== Station' |
- | Adresářová struktura správně nakonfigurované stanice | + | Directory structure of a correctly configured |
User_Name | User_Name | ||
Line 75: | Line 77: | ||
└── setup_reverse_tunnel.sh | └── setup_reverse_tunnel.sh | ||
| | ||
- | Všechna měřená | + | All measured |
- | + | ||
- | * **rmob.cfg** - Parametry stanice, umístění, | + | |
- | * **Bolidozor.json** - Nastavení stanice a měření. | + | |
- | + | ||
- | Složka bolidozor tím pak částečně kopíruje datovou strukturu stanice na serveru [[cs: | + | |
+ | * **rmob.cfg** - Station' | ||
+ | * **Bolidozor.json** - Configuration of station and measurements. | ||
+ | Bolidozor directory thus partially copies the data structure of the station at [[en: | ||
- | ===== K vyřešení | + | ===== Problems to solve ===== |
- | ==== Identifikace pozice stanice | + | ==== Identification of station' |
- | 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 |
* Latitude, Longitude | * Latitude, Longitude | ||
* [[http:// | * [[http:// | ||
- | * Lokátor | + | * Locator |
- | * Adresa | + | * Address |
en/convention.txt · Last modified: 2019/04/24 13:34 by fluktuacia