Merge pull request #33 from discos/master

Fix #27: done al the required modification in order to match the current Noto configuration

user/noto/Appendix_A.rst

@@ -366,44 +366,9 @@ running schedule, if any.
 To close the monitor, type ``exit`` in its prompt (the grey line). 
 
 
-MinorServo
-==========
+.. note:: All the monitors can be closed at a time using the command::
 
-.. figure:: images/Screenshot-MinorServo.png
-   :scale: 100%
-   :alt: Minor Servo TUI
-   :align: left
-
-This monitor shows details on the Minor Servo systems:
-
-  * **Current Setup**: current setup code (**CCC**, **XXP**, **KKC**,
-    …)
-
-  * **Ready**: when green, the receiver is in its working position
-
-  * **Starting** : when green, the minor servo are moving in order to put 
-    the selected receiver in its working position
-
-  * **AS Conf**: when green, the subreflector position is computed by assuming 
-    the primary mirror surface is shaped and active (it is changing 
-    with the antenna elavation)
-
-  * **Elevation Track**: when green, the subreflector is changing its 
-    position with the elevation
-
-  * **Scan active**: when green, a scan is active. That means either the system 
-    is performing a scan or a scan is terminated and so the system is waiting 
-    for a stopScan command or for a new scan 
-
-  * **Scanning**: when green, the system is performing a scan
-
-To close the monitor, type ``exit`` in its prompt (the grey line). 
-
-
-.. note:: All the monitors can be closed at a time using the command (in a 
-   terminal on escsRemote)::
-
-	$ escsConsole --stop
+	$ discosConsole --stop
 
 
 Logging Display

user/noto/Appendix_B.rst

@@ -73,6 +73,10 @@ Here follow all the commands exploitable in ESCS:
 
    Example: ``> azelOffsets=-0.05d,0.05d``
 
+.. describe:: > calmux=[code]
+
+   (``code`` can be ``TOTALPOWER``, ``DBBC``) 
+   configures the calibration diode multiplexer 
 
 .. describe:: > calOn
 

user/noto/Appendix_D.rst

@@ -13,7 +13,7 @@ inside the LIS file) or in the command::
 Along with their J2000 Equatorial coordinates, the catalogue records usually 
 contain further information such as apparent size, proper motion, radial 
 velocity, coefficients of the *Ott et al.* polynomials describing the spectra, 
-etc… ESCS uses these parameters to make computations during certain 
+etc… DISCOS uses these parameters to make computations during certain 
 operations (e.g. when calibration tools are used – under development, they 
 will be described in future releases of this manual).
 

user/noto/Backend.rst

@@ -59,7 +59,7 @@ long as the receivers' IF bandwidth is restricted to 500 MHz.
 
 Consider that the above-listed bandwidths do not correspond to the true 
 observed ones, for the reason discussed in Initial Setup. When accumulations 
-of the data “dumps” are requiredbefore integrating them to the output file, it 
+of the data “dumps” are required before integrating them to the output file, it 
 is possible to set the integration time as follows::
 
     > integration=[N] 
@@ -91,5 +91,25 @@ pointing accuracy. This is accomplished using the command::
 
 which uploads to the system the parameters relative to section number [sect] 
 (you can generally use 0, which exists for all the receivers, unless you need 
-to observe only with a different feed).   
+to observe only with a different feed).
 
+
+.. _EN_calmux-focus-selector:
+
+Calmux - calibration diode multiplexer
+======================================
+
+The Calmux is a multiplexer that allows to choose which backend is entitled to control the
+calibration diode on the frontend. This device is required when more than one backend has the
+capability to exploit the fast switching. This is the case for DBBC (VLBI) and TotalPower
+backends in Noto. When observing with DISCOS, the proper calmux configuration is set
+transparently during the setup phase. In case a specific configuration is required, use::
+
+    > calmux=[code] 
+	
+(``code`` can be ``TOTALPOWER``, ``DBBC``)
+
+.. admonition:: WARNING:  
+
+	* Since then calmux control port is single-client, it is mandatory for DISCOS to properly configure it to make sure that no other clients are connected at the time of the telescope setup.
+

user/noto/Checklist.rst

@@ -4,24 +4,21 @@
 Checklist for schedule-based observations
 *****************************************
 
-Notice that actions take place in three different “locations”:
+Notice that actions can take place either locally or remotely.
 
-  * **(1)** = action to be performed in a terminal on escs
-  * **(2)** = action to be performed in a terminal on euser
-  * **(op)** = command to be given in the *operatorInput* panel of ESCS
+**Login control system(1)** 
+*Locally*: login on discos-manager using the discos credentials. 
+*Remotely*: connect via VNC to discos-manager with the proper credentials and instructions
+provided by local staff. 
+**login your user or poject home(2)** you can ssh into discos-manager with proper credentials.
 
-**Login on both (1) and (2)** 
-*Locally*: login on (2) using the euser credentials, then Using the ESCS icon 
-on the Desktop, connect to (1).
-*Remotely*: connect via VNC to (1) with the proper credentials, 
-then use ssh to access (2). 
 
 .. note:: Remember that spaces within the command line content are **not** 
    allowed!
 
-**Launch the monitors, if necessary** (1):: 
+**Launch the monitors, if necessary**:: 
 
-	$ escsConsole 
+	$ discosConsole
 
 **Initial setup** (op)::
 
@@ -118,7 +115,7 @@ then use ssh to access (2).
 
 **Close the monitors, if necessary** (1)::
 
-	$ escsConsole —-stop   (individual panels are closed typing “exit” in their command lines)
+	$ discosConsole —-stop   (individual panels are closed typing “exit” in their command lines)
 
 
 

user/noto/DataRetrieval.rst

@@ -4,7 +4,7 @@
 Retrieving the data
 *******************
 
-Open a terminal on the euser machine. Your data folder is::
+Open a terminal on the discos-manager machine(using your userID). Your data folder is::
 
     ~/data
 
@@ -37,12 +37,12 @@ FITS files, each corresponding to a subscan, are composed as:
 
 **YYYYMMDD-HHMMSS-User-Suffix_Scan#_Subscan#.fits**
 
-Data can be copied from *escsConsole* to your laptop using  'ssh’  or   
+Data can be copied to your laptop using  'ssh’  or   
 ‘rsync –e ssh’  commands.
 
 
 .. note:: When recording manually-acquired data in FITS format, the output 
-   files are still accessible from the euser machine, yet they are found in a 
+   files are still accessible from the discos-manager machine, yet they are found in a 
    peculiar path, different from the one employed when schedules run.
    You can find these FITS files in /archive/extraData. 
    This implies that they also cannot be automatically showed by the quick-look 

user/noto/Frontend.rst

@@ -24,7 +24,7 @@ To change the frontend Local Oscillator frequency, use the following command::
     > setLO=[freq1];[freq2];…;[freqN]
 
 Notice the semicolon. Ideally, different values could be assigned to different 
-IFs, thus tuning each section to a different sub-band. For the present 
+IFs, thus tuning each IFs to a different sub-band. For the present 
 hardware, though, this is not possible, so a single value must be specified: 
 
 	e.g. ``> setLO=4900`` 
@@ -39,10 +39,14 @@ The calibration mark can be manually switched on and off respectively with::
     > calOn 
     > calOff
 
+.. admonition:: WARNING:  
+
+    * Even if the calibration diode is a device included in the frontend, it is
+      controlled through the TotalPower backend. As a consequence, the "calmux"
+      must be properly configured - see details in the backend section.
 
 If the user wants to perform the setup for the frontend only (without 
 affecting the mount, the minor servo or the backend), the command is:: 
 
     > receiversSetup=[code]   (CCC, MMC, KKC, QQC)
 
-

user/noto/Introduction.rst

@@ -6,18 +6,18 @@ Overview
 ********
 
 
-What ESCS is
+What DISCOS is
 ============
 
-ESCS is the DISCOS control software flavour produced for the Medicina and Noto 
+DISCOS is the control software produced for the Medicina, Noto and SRT 
 radio telescopes. 
 It is a distributed system based on ACS (ALMA Common Software), commanding all
 the devices of the telescope and allowing the user to perform single-dish
 observations in the most common modes. 
 As of today, the code actually implemented for the telescopes (i.e. excluding
 the huge ACS framework) amounts to > 550000 active lines. 
 
-This guide is meant to help the observer in the use of ESCS, without dealing
+This guide is meant to help the observer in the use of DISCOS, without dealing
 with the “behind-the-curtains” complex details of the system. 
 This release focuses on **single-dish continuum
 observations**, as the fully integrated backend available on-site is the
@@ -26,7 +26,7 @@ software implementations are continuously updated, this manual will forcibly
 undergo frequent revisions. 
 
 Here follows a simple schematization of the observing system, helpful to
-visualize all the main devices ESCS deals with and the most important
+visualize all the main devices DISCOS deals with and the most important
 operations it performs. 
 *Notice: the features not yet available in this release are shown in brackets*.
 

user/noto/Quicklook.rst

@@ -7,59 +7,33 @@ Data formats and online quick-look
 Details on the FITS file structure are given in a separate document. Download 
 it here: :download:`pdf <attachments/MED-MAN-FITS-02.pdf>` 
 
-Waiting for a comprehensive GUI which is going to include also a real-time 
-preview of the data under acquisition, users are provided with two different 
+Users are provided with two different 
 tools in order to inspect the data produced by the TPB. 
 
 If writer is MANAGEMENT/FitsZilla
 =================================
-When acquiring FITS files through a schedule, there is an IDL tool available 
+When acquiring FITS files through a schedule, there is a tool available 
 for the almost-realtime quick-look of the saved data.
 
-Open a terminal on *euser*. Launch IDL::
+Open an internet browser and visit the page "http://XXX.XXX.XXX.XXX:8080".
+The address corresponds to the discos-manager workstation. Otherwise if
+you are directly connected to discos-manager through ssh you can simply
+visit "http://localhost:8080".
 
-    $ idl
-
-At the IDL prompt, compile and run the program fitslook.pro:: 
-
-    IDL> .r fitslook
-    IDL> fitslook
-
-The last completed FITS file (i.e. the most recent subscan carried out) will be 
-displayed in terms of arbitrary counts vs sample number (i.e. raw intensity 
-against time). 
+The last completed FITS file (i.e. the most recent subscan carried out)
+will be displayed with some ancillary information.
 
 .. note:: The program automatically identifies the recorded sections and 
    plots them all.
 
-There are different options in order to plot the datai in terms of other 
-quantities. Read all these options using::
-
-    IDL> fitslook, /help
-
-.. note:: Data streams in antenna temperature are available - and selectable - 
-   only for the TPB and under the condition that a Tsys has been correctly 
-   acquired prior to the execution of the scan. 
-
-Please report any problem/request about this tool, as it is under development.
-
-.. figure:: images/IDL_quicklook.png
-   :scale: 100%
-   :alt: Quick-look of a continuum OTF scan acquired with a single-feed receiver 
-   :align: center
-
-.. note:: If you are OK with the default settings, you can also launch the 
-   quicklook using the icon provided on the euser desktop, without having to 
-   start IDL, etc.   
-
 
 If writer is MANAGEMENT/Point or MANAGEMENT/CalibrationTool
 ===========================================================
 
 When data are acquired – both manually or through a schedule – using the Point 
 or CalibrationTool writers, the quick-look must be performed using the 
 CalibrationToolClient. 
-Open a terminal on escs and use the command:: 
+Open a terminal and use the command:: 
 
     $ calibrationtoolclient  [componentName]
 
@@ -76,4 +50,4 @@ In this client, the subscan currently being acquired is shown *in real-time*
 completed subscan - in its full sampling - is shown. 
 
 .. note:: You can also launch the calibrationtoolclient using the icon provided 
-   on the euser desktop, without having to open a terminal, etc. 
+   on the euser desktop, without having to open a terminal, etc. 

user/noto/ReleaseNotes.rst

@@ -16,5 +16,6 @@ Issue	     Release     What’s
 ===========  =========== =====================================================
 -----------  ----------- -----------------------------------------------------
 01           30/11/16    Issue 01 - first ESCS installation at Noto
+02				 04/04/19    Issue 02 - updated to discos 1.0, version 64bits 
 ===========  =========== =====================================================
 

user/noto/Setup.rst

@@ -9,7 +9,7 @@ Initial setup
 Antenna overall setup
 =====================
 
-When opening an ESCS observing session, it is necessary to perform a setup 
+When opening a DISCOS observing session, it is necessary to perform a setup 
 which includes the antenna unstow, the mount configuration in tracking mode, 
 the minor servo setup. This is done by means of a unique command, which is 
 specific for the wanted receiver, to be written in the **operatorInput**. 
@@ -66,7 +66,7 @@ bandwidth and the band starting frequency are recorded in the output files
 (see :ref:`EN_Appendix-C-Output-files`).
 
 (1) For this setup, the FITS file will **NOT** report the actual values 
-relative to frequency and bandwidth, as the present ESCS release does not take 
+relative to frequency and bandwidth, as the present DISCOS release does not take 
 into account the different conversion taking place for this receiver.