Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.216.72
Lock expires at: 2026/08/02 05:08 (6 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Radio Observer ======

This is an application designed to operate radio observations: :

  - Meteor observation
  - Sun, Jupiter or galactic emissions
  - Observations of other objects

A key feature of the program is the ability to record time-tagged data, useful for further analysis after obtaining data from multiple stations. 

A test version is available at [[https://github.com/MLAB-project/radio-observer|radio-observer]]. It should run on a  [[cs:arm|ARM computer]].

Functional requirements for the resulting application-Observer Radio are written to [[http://www.mlab.cz/redmine/projects/rao01a|Redmine]].

====  Radio telescopes ====

One use case of the radio-observer is its deployment at stations The radio astronomy station [[cs:bras]] and advanced radio astronomy station [[cs:aras]], or the simple parabolic radio telescope .

==== Meteor observations ====

Software for meteor observations is engaged in a project [[http://wiki.bolidozor.cz/doku.php?id=cs:about|Bolidozor]]. 

====  Observing the Sun / Jupiter  ====

This type of observation would need waterfall display with a lower frequency and time resolution, but a large frequency bandwidth (in range of MHz) in order to see the entire band where emissions occur. This could be achieved by retuning the receiver. Tunning period should be slow because Sun or Jupiter emissions is a slow phenomena.

The result should be a long FITS file throughout the day, with intensity spots corresponding storms. 

==== Detector data outputs ====

  * Thumbnail image in the FITS to generate previews on the site. (Web browser might render the file and render colorize from data stored in FITS according to user requirements)
  * RAW recordings of the meteor reflection (raw recordings are important for later data analysis) 
  * Along with data large records should exist a metadata text file, common to all files in a folder (each file should have one line of metadata). This arrangement is intended to prevent necessity to open large files and browse their heads. Metadata file should be humanly readable. 

----

Suggestions for the title of data file //TIME_NAME_TYPE.EXTE// the length of the file name is limited to 50 characters.

  * NAME  is a station identifier can be up to the maximum permitted length of the full name. The title should include the version of the station configuration. Eg. SVAK1-RADIO-1-1
  * TYPE is data identifier.

Requirement for contributing to the database meets the following regular expression in a file name: 

  ({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: 
  20131215115953208_SVAKOV-R2_met.jpg
  20131215115954558_SVAKOV-R2_fb.jpg
  20131215115955002_SVAKOV-R2_nomet.jpg