User Tools

Site Tools


en:programming_tasks

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:programming_tasks [2014/07/04 22:02] – [Considered data inputs (network nodes)] kakliken:programming_tasks [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
Line 24: Line 24:
   * Nodes acting as data storage, or performing some calculations on the data (data mining servers)   * Nodes acting as data storage, or performing some calculations on the data (data mining servers)
  
-Each node as part of a network will be operated by the observational application (eg, [[en:radio-observer]], Meteor Observer, Visual Observer, etc.) in cooperation with  [[en:station-supervisor|Station-supervisor]] daemon that will handle communication with the rest of the network and data distributionDaemon should therefore have an interface or file system in which data measuring application should store data. Station-supervisor daemon then solve optimal data distribution between data servers.+Each node as part of a network will be operated by the observational application (eg, [[en:radio-observer]], Meteor Observer, Visual Observer, etc.) in cooperation with  [[en:station-supervisor|Station-supervisor]] which manages the station verify its workAnother daemon should therefore have an interface or file system in which data measuring application should store data and then solve optimal data distribution between data servers.
  
 ====  System Properties  ==== ====  System Properties  ====
Line 33: Line 33:
   - An important parameter of the network is that data from individual stations were available at one time (with the least time scatter) in order to perform live calculations on the inter-station data.   - An important parameter of the network is that data from individual stations were available at one time (with the least time scatter) in order to perform live calculations on the inter-station data.
  
-==== The hardware implementation ====+ 
 +=== Typical station design === 
 + 
 +{{ :cs:designs:supervising_system.png?direct |}} 
 + 
 +Image above illustrates an typical station connected to the distributed measurement system. The measuring station itself consist several subsystems.  
 + 
 +== Local presentation node == 
 + 
 +A PC system located at same site where the measuring station operates but generally in another room or building.  The purpose of presentation node is displaying of measuring data in an interactive form which is attractive for visitors or should be used to demonstrate principle of measurement. 
 + 
 +== Measuring node == 
 + 
 +This is part which performs the measurement and it is responsible to data making. Measuring node has several minor subsystems. 
 + 
 +Measuring Hardware - A set of sensors and hardware required for measuring. 
 + 
 +Hardware station guard - A hardware recovery unit which could separately reset every hardware part of measuring node. The station-supervisor daemon should use this device for error outputs. Connection management between recovery unit and station-supervisor daemon will be self controlled by device. Interface between hardware recovery unit and main station computer should be terminal based.  The terminal functionality should be provided by station-supervisor monitor software (ssmon) (if it is running, otherwise by 
 +standard system console) in system console mode station 
 +supervisor-should write debug output on this device (similarly to dmesg 
 +for example) 
 + 
 +== Network interface == 
 + 
 +We will not have direct IP connectivity from Internet to stations. Station supervisor software should generate data file outputs and upload these data files to an web server which serves station status information. Telemetry information will be displayed in the web on separate central web server.  Web page served by central status server is primary diagnostic interface. Terminal interface to measuring node is secondary backup interface which is not accessible on all stations. 
 + 
 +Moreover web access is intended as file based. File based means that 
 +station-supervisor uploads an diagnostic file to the central web server. Web server takes this files (from more than one station) and serve a web page with stations status information. User interface in this case is limited only to modification of an station-supervisor configuration file stored 
 +on web server.  
 + 
 +For example configuration file may contain an parameter for station reboot 
 +request. After station-supervisor will notice a change or update in the 
 +web server stored configuration file, station-supervisor reboots the station and 
 +update its parameters according to actual configuration file.  
 + 
 + 
 +=== Node software === 
 + 
 +Node hardware will run a data-processing utility ([[en:radio-observer]] for example), data uploading and distributing utility and station-supervisor daemon. Station-supervisor acts as watchman which checks proper functioning of whole measuring node. Data-upload is another daemon, which manages storage space on measuring node.  
 + 
 +Station-supervisor does not have a screen output. Screen output may be served by client program ssmon (Station Supervisor Monitor) which generates interactive status screen after connection to Station Supervisor server. 
 + 
 + 
 +==== Hardware implementation ====
  
 === Computing power === === Computing power ===
Line 50: Line 93:
 ====  Software implementation  ==== ====  Software implementation  ====
  
-The network management would be advantageous to use the system to control robots [[http://www.ros.org/wiki/|ROS]], or any system designed for control [http://www.astro.physik.uni-goettingen.de/~hessman/MONET/software.html|robotics telescopes]].+The network management would be advantageous to use the system to control robots [[http://www.ros.org/wiki/|ROS]], or any system designed for control [[http://www.astro.physik.uni-goettingen.de/~hessman/MONET/software.html|robotics telescopes]]. Similar functions are implemented in [[http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol|SNMP]].
  
 ===  Data Processing  === ===  Data Processing  ===
Line 170: Line 213:
 The result of this calculation could be used for observation planning.  The result of this calculation could be used for observation planning. 
  
-=====  Implementation sources =====+==== References ==== 
 + 
 +  * [[https://openmeteoforecast.org/wiki/Main_Page|Open Meteo Forecast]] 
 +  * [[http://flymet.meteopress.cz/|Aeronautical meteograms]] 
 +=====  Implementation resources =====
  
 ==== Investigators ==== ==== Investigators ====
Line 176: Line 223:
 The project is implemented by a team of several students CTU, TU and members of Robozor robotics club:  The project is implemented by a team of several students CTU, TU and members of Robozor robotics club: 
  
-  * [[https://usermap.cvut.cz/profile/suchmari/|Bc. Marián Šuch]] - Visualization and preparation of the data distribution 
   * Martin Povišer - Signal digitalization and storage decentralization   * Martin Povišer - Signal digitalization and storage decentralization
   * [[https://usermap.cvut.cz/profile/milikjan/|Bc. Jan Milík]] - radio detection of meteors    * [[https://usermap.cvut.cz/profile/milikjan/|Bc. Jan Milík]] - radio detection of meteors 
en/programming_tasks.1404511334.txt.gz · Last modified: 2014/07/04 22:02 (external edit)