User Tools

Site Tools


en:convention

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:convention [2017/01/12 11:48]
fluktuacia
en:convention [2019/04/24 15:34] (current)
fluktuacia [Data structure]
Line 1: Line 1:
 ====== Bolidozor network conventions ====== ====== 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 ===== ===== Observatory =====
  
-In the context of the Bolidozor network 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 stores 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.
Line 17: Line 17:
 ==== Radio detection stations ==== ==== 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 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. ​ 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. ​
Line 26: Line 29:
 ==== Data structure ==== ==== 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// ​ 
 + 
 +The length of the file name is limited to 50 characters.
  
   * TIME represents a timestamp with resolution of at least ms or ns  ​   * TIME represents a timestamp with resolution of at least ms or ns  ​
-  * NAME represents the station'​s 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// ​  +  * NAME represents the station'​s id and can have a length of 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   * 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]])   * 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 require ​that the file name has a form of the following regular expression:+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})?​   ({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})?​
en/convention.1484218083.txt.gz · Last modified: 2017/01/12 11:48 by fluktuacia