Add note what to do when the download does not work

Jürgen Knödlseder
1 parent 9fb6b02a
Showing 3 changed files with 81 additions and 63 deletions
doc/source/users/tutorials/1dc/data_organisation.rst
doc/source/users/tutorials/1dc/getting_data.rst
doc/source/users/tutorials/1dc/getting_tools.rst
@@ -134,44 +134,44 @@ have been simulated (see figure below).
    :align: center
  
    *Header of an event list*
-
-
-.. warning::
-   Only the following header keywords in the ``EVENTS`` table have meaningful
-   values:
-
-   * ``DSTYPx`` - Data sub-space type
-   * ``DSUNIx`` - Data sub-space unit
-   * ``DSVALx`` - Data sub-space value
-   * ``DSREFx`` - Data sub-space reference
-   * ``NDSKEYS`` - Number of data sub-space keys
-   * ``NMCIDS`` - Number of Monte Carlo identifiers
-   * ``MIDxxxxx`` - Monte Carlo identifier
-   * ``MMNxxxxx`` - Model name for Monte Carlo identifier
-   * ``OBS_ID`` - Observation identifier
-   * ``DATE_OBS`` - start date of observation (UTC)
-   * ``TIME_OBS`` - start time of observation (UTC)
-   * ``DATE_END`` - end date of observation (UTC)
-   * ``TIME_END`` - end time of observation (UTC)
-   * ``TSTART`` - start time of observation, counted from time reference (s)
-   * ``TSTOP`` - stop time of observation, counted from time reference (s)
-   * ``MJDREFI`` - integer part of time reference MJD (days)
-   * ``MJDREFF`` - fractional part of time reference MJD (days)
-   * ``TIMEUNIT`` - time unit
-   * ``TIMESYS`` - time system
-   * ``TIMEREF`` - time reference
-   * ``TELAPSE`` - elapsed time (s)
-   * ``ONTIME`` - exposure time (s)
-   * ``LIVETIME`` - livetime (s)
-   * ``DEADC`` - deadtime correction factor, livetime / exposure time
-   * ``TIMEDEL`` - time resolution
-   * ``RA_PNT`` - Right Ascension of pointing direction (deg)
-   * ``DEC_PNT`` - Declination of pointing direction (deg)
-   * ``RADECSYS`` - Coordinate system
-   * ``EQUINOX`` - Coordinate epoch
-
-   All remaining header keywords have arbitrary values and should not be
-   used for the analysis.
+..
+
+  .. warning::
+     Only the following header keywords in the ``EVENTS`` table have meaningful
+     values:
+
+     * ``DSTYPx`` - Data sub-space type
+     * ``DSUNIx`` - Data sub-space unit
+     * ``DSVALx`` - Data sub-space value
+     * ``DSREFx`` - Data sub-space reference
+     * ``NDSKEYS`` - Number of data sub-space keys
+     * ``NMCIDS`` - Number of Monte Carlo identifiers
+     * ``MIDxxxxx`` - Monte Carlo identifier
+     * ``MMNxxxxx`` - Model name for Monte Carlo identifier
+     * ``OBS_ID`` - Observation identifier
+     * ``DATE_OBS`` - start date of observation (UTC)
+     * ``TIME_OBS`` - start time of observation (UTC)
+     * ``DATE_END`` - end date of observation (UTC)
+     * ``TIME_END`` - end time of observation (UTC)
+     * ``TSTART`` - start time of observation, counted from time reference (s)
+     * ``TSTOP`` - stop time of observation, counted from time reference (s)
+     * ``MJDREFI`` - integer part of time reference MJD (days)
+     * ``MJDREFF`` - fractional part of time reference MJD (days)
+     * ``TIMEUNIT`` - time unit
+     * ``TIMESYS`` - time system
+     * ``TIMEREF`` - time reference
+     * ``TELAPSE`` - elapsed time (s)
+     * ``ONTIME`` - exposure time (s)
+     * ``LIVETIME`` - livetime (s)
+     * ``DEADC`` - deadtime correction factor, livetime / exposure time
+     * ``TIMEDEL`` - time resolution
+     * ``RA_PNT`` - Right Ascension of pointing direction (deg)
+     * ``DEC_PNT`` - Declination of pointing direction (deg)
+     * ``RADECSYS`` - Coordinate system
+     * ``EQUINOX`` - Coordinate epoch
+
+     All remaining header keywords have arbitrary values and should not be
+     used for the analysis.
  
 Each row of the ``EVENTS`` table corresponds to a single event.
 Each event is characterised by
@@ -203,10 +203,11 @@ An example of an ``EVENTS`` table is shown below.
    :align: center
  
    *Content of an event list*
+..
  
-.. warning::
-   The time stamps in the ``TIME`` column are **not** necessarily in ascending
-   order.
+  .. warning::
+     The time stamps in the ``TIME`` column are **not** necessarily in ascending
+     order.
  
  
 Observation Definition Files
@@ -234,10 +235,10 @@ identical.
 The other files in the folder are ASCII and FITS files containing spectral,
 temporal and spatial information that was used in the simulations.
  
-.. warning::
-   The ASCII and FITS files should always reside in the same folder as the
-   :ref:`model definition XML files <glossary_moddef>`
-   since the latter reference the former.
+  .. warning::
+     The ASCII and FITS files should always reside in the same folder as the
+     :ref:`model definition XML files <glossary_moddef>`
+     since the latter reference the former.
  
  
  
@@ -36,11 +36,27 @@ line by typing:
    $ wget https://owncloud.cta-observatory.org/remote.php/webdav/1dc/agn.tar.gz --user=<user> --ask-password
    $ wget https://owncloud.cta-observatory.org/remote.php/webdav/1dc/caldb.tar.gz --user=<user> --ask-password
    $ wget https://owncloud.cta-observatory.org/remote.php/webdav/1dc/models.tar.gz --user=<user> --ask-password
+..
  
-.. warning::
-   ``<user>`` needs to be replaced by your CTA user name.
-   Don't type the ``$`` symbol. It indicates that a command should be typed
-   on the command line of your terminal.
+  .. warning::
+     ``<user>`` needs to be replaced by your CTA user name.
+     Don't type the ``$`` symbol. It indicates that a command should be typed
+     on the command line of your terminal.
+
+  .. note::
+     In case you encounter the following error message
+
+
+     .. code-block:: bash
+
+        HTTP request sent, awaiting response... 401 Unauthorized
+        Authentication selected: Basic realm="ownCloud"
+        Reusing existing connection to owncloud.cta-observatory.org:443.
+        HTTP request sent, awaiting response... 404 Not Found
+        2017-06-06 14:43:33 ERROR 404: Not Found.
+
+     or any other problems with the download, please contact
+     sstober@cta-observatory.org.
  
 To make sure that you have the relevant files you may check the MD5 checksums
 after downloading by typing for example
@@ -94,11 +110,12 @@ Before continuing, please set the following environment variables:
  
    $ export CTADATA=$PWD/1dc
    $ export CALDB=$CTADATA/caldb
-
-.. note::
-   You may consider adding the ``CTADATA`` and ``CALDB`` environment variables
-   to your ``.bashrc`` file (or equivalent) so that your analysis environment
-   for the
-   :ref:`first CTA Data Challenge <glossary_1dc>`
-   is always setup correctly.
+..
+
+  .. note::
+     You may consider adding the ``CTADATA`` and ``CALDB`` environment variables
+     to your ``.bashrc`` file (or equivalent) so that your analysis environment
+     for the
+     :ref:`first CTA Data Challenge <glossary_1dc>`
+     is always setup correctly.
  
@@ -27,13 +27,13 @@ After downloading, configure GammaLib and ctools as follows:
 Have a look at :ref:`getting the ctools <sec_install>` if you need more
 information about the installation and configuration process.
  
-.. note::
-   You may consider adding the ``GAMMALIB`` and ``CTOOLS`` environment variables
-   as well as the sourcing of the configuration scripts to your ``.bashrc`` file
-   (or equivalent) so that your analysis environment
-   for the
-   :ref:`first CTA Data Challenge <glossary_1dc>`
-   is always setup correctly.
+  .. note::
+     You may consider adding the ``GAMMALIB`` and ``CTOOLS`` environment variables
+     as well as the sourcing of the configuration scripts to your ``.bashrc`` file
+     (or equivalent) so that your analysis environment
+     for the
+     :ref:`first CTA Data Challenge <glossary_1dc>`
+     is always setup correctly.