Skip to content

D
dtObsGUI
Commit 6be899a7 authored by marc's avatar marc
Browse files
Options

doc updates

parent 01483c63
Pipeline #14 failed with stages
      Hide whitespace changes
      Inline Side-by-side
      Showing with 8 additions and 8 deletions
      doc/chapters/installation.rst
      View file @ 6be899a7
      ......@@ -14,11 +14,10 @@ is build using QT designer and converted into a python UI window class by means
      - backend
      - createpointings
      The latter 4 classes are installed in the dtObsGUI directory and imported by
      python. Each class has an ini file and should be checked for each installation,
      see section: `Configuration`_. It sets e.g. the file locations of the measurement
      programmes, test modes, logging level etc. Make sure you can execute the
      programme, test modes, logging level etc. Make sure you can execute the
      programme as user.
      ::
      ......@@ -31,7 +30,7 @@ programme as user.
      git clone https://gitlab.camras.nl/marc/createpointings.git
      On mecury the telescope class is already installed. For other systems the
      class can be installed locally or in system.
      class can be installed locally or in system.
      ::
      ......@@ -55,7 +54,7 @@ To ease the DEVOPS customization of dtObsGUI, each class has its own `.ini` file
      used by the config manager of python. The `.ini` files are key/value entries read
      during the instantiation of the class.
      The configuration of the `telescope` Class is described on `git-lab`_.
      The configuration of the `Telescope` Class is described on `git-lab`_.
      dtobsgui ini
      ------------
      ......@@ -67,11 +66,12 @@ dtobsgui ini
      For normal operation the `INFO` level is sufficient and shows the entry and exit
      of executed methods.
      The demo can be set `True` to bypass the telescope class, which requires a
      connection to either the `consoledemo`_ or the DT telescope. This setting is for
      development purpose only. For proper operation of the software `demo` should be
      set to `False`
      The demo can be set `True` to bypass the Telescope class. Testing DTObs against
      a Telescope it is adviced to use the containerized dt_ctrl docker available on
      gitlab. The Telescope class double checks if it is hosted on Mercurius. In this
      case the Telescope class can control the DT.
      .. attention:: Please follow all savety steps prior controlling the DT!
      Example:
      ......
      Markdown is supported
      0% or
      You are about to add 0 people to the discussion. Proceed with caution.
      Finish editing this message first!
      Please register or to comment