README.md 5.13 KB
Newer Older
marc's avatar
marc committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106
# Release 1.0 features
- loads ascii pointing file in QTable
- controls pointings using the Telescope class
- writes metadata in result file using MetaData class
- creates CLI commands to perform the measurements
- set backend in required mode

# DT Observartion GUI

The DTObsGUI provide a simplified way to operate the Dwingeloo Telescope by means
of a user friendly GUI, which reads the pointings and send these poinings to
the telescope using the python Telescope class. As soon the Telescope trackt the
source, the actual measurement starts after the backend is set into the correct
mode. The actual resultfiles are stored on the local drive and can be made 
available on Internet. Beside the actual results the meta data is written in each
result file required for post processing of the data.

## How to use DT Ovservation Application

The GUI consists of a standard menu and the mean purpose in the 1.0 release is to
load the pointings. This list needs to be provided in a simple ascii file having
3 columens, i.e. measurement number, RA and Dec. Using File->Open the required 
file is loaed and made available in the right hand Table panel, showing the
measument number, RA, Dec, Status and Result File.

On the left hand side you'll find 3 toolboxes to enter Meta Data, define your 
measurement tool and settings and the backend mode.

## Define Meta Data

After activating the Meta Tool box the generic meta data can be entered:
- Operator 1, 2 and 3
- Description, purpose of the measument.

Next to the generic data, the actual time, measurement and backend settings are
stored in the resultfiles.

## Measurements

A number of programmes are available defined in the Measurement toolbox. Depending
on the observation the following programmes can be used:

- dumpwide
- int32bin
- pulsarrecord
- rawrecord

Each programme needs 1 or more arguments like the integration time and central
frequency. [note: not implemented yet]. Also the telescope settings for Refraction
and DT Model needs to be checked and enabled if needed in the Measurement toolbox.
This information will be stored as meta data in the result file.

Please contact CAMRAS to get details on these programmes. The output directory
can be seleted and stores the resultfiles.

## Backend

The backend supports the following modes:
- Pulsar mode, used for e.g. the pulsar demo
- Line mode, this is used for HI observations and has be higher frequecy resolution.
- SDR mode outputs IQ data, compatible with e.g. gnuradio.
- Raw mode is used for more demanding requirements in time and frequency domain.

In case the backend mode will change, make sure that the backend is checked and 
set into the proper mode. Do not start the measurement prior the backend is set.

It is also possible to compensate for the Local Standard of Rest (LSR). In the
case the received frequency will be corrected fo LSR.

If the metadata, measurement and backend settings are set, the actual measurement
can start.

## Start measurement

The righthand side table list the pointings which are sent to the telescope after
clicking on the 'Start Measurement' button. Each point goes throug a status of
scheduled, slewing, measuring, completed indentified by a colour. As soon a
measurement is finished it is possible to view the result file in gnuplot, but
a 'double click' on the table row.

After the measurement is completed, the table can be cleaned using the File->Close
menu and a new file can be loaded. Minor mistakes can be corrected in the Table
but are not yet saved in the measurement file.

The result files do have date and measurement number, so in case you redo the
measurement, make sure you either select an other outpur directory or move the
result files to a save location.

# Installation

DTObsGUI is written in python3 and uses pyqt5 GUI framework. The user interface
is build using QT designer and coverted to a python UI window class. Therefore
the system depends on:
- python3
- pyqt5
- CAMRAS python classes, available on CAMRAS gitlab
    - dtObsGUI
    - measurements
    - metadata
    - backend

The latter 3 classes are installed in the dtObsGUI directory and imported by 
python. Each class has an ini file and should be checked for each installation.
It sets e.g. the file locations of the measurement programmes, test modes, logging
level etc. Make sure you can execute the programmas are current user.

marc's avatar
marc committed
107
```
marc's avatar
marc committed
108 109 110 111 112
git clone https://gitlab.camras.nl/marc/dtObsGUI.git
cd dtObsGUI
git clone https://gitlab.camras.nl/marc/measurements.git
git clone https://gitlab.camras.nl/marc/metadata.git
git clone https://gitlab.camras.nl/marc/backend.git
marc's avatar
marc committed
113
```
marc's avatar
marc committed
114 115 116 117

Check for each programme if DT Obs can find the proper location. Each class can
be tested individually if needed.

marc's avatar
marc committed
118 119 120 121 122
Add PYTHONPATH for createpointings
```
export PYTHONPATH=createpointings:${PYTHONPATH}
```

marc's avatar
marc committed
123 124 125 126 127 128 129 130 131 132 133
# TODO
- define central frequency
- internationalization
- predefine pointings for demo sources, e.g. M31, CASA, M101, hydrogen profiles
- set MJD in metadata, now local time
- INDI connection to show DT position on Stellarium
- estimation overall observation time
- update status field with status
- initial post processing of measuments
- Pause/resume of measument
- SETI transient setting in case of transient obserations