This directory contains the SPICE Hands-on Lesson packages that
   include the following lessons:

      Navigating Through the SPICE Components  (toolkit_contents)
      Basics, Building SPICE Applications      (start_programming)
      Remote Sensing, using CASSINI            (remote_sensing)
      Geometric Event Finding, using MEX       (event_finding)
      In-situ Sensing, using CASSINI           (insitu_sensing)
      Binary PCK                               (binary_pck)
      Other Stuff                              (other_stuff)
      Practice Using Toolkit Applications      (toolkit_programs)
      Doing SPICE Hands-On Lessons Using WGC   (lessons_wgc)

   All lessons for each of supported languages (FORTRAN, C, IDL,
   MATLAB, Python (using SpiceyPy)) -- platform (Unix (Linux, Mac OSX,
   Solaris), Windows) combinations are provided in a single .zip file.
   For example, the ``spice_lessons_f_unix.zip'' file contains all
   FORTRAN lessons for Unix platforms.
 
   To install all lessons, you need to download only one package for
   your language/platform combination to the ``doc/html'' subdirectory
   of your toolkit and un-zip it in that subdirectory. For example, if
   you are using a CSPICE toolkit on Unix, you need to download
   ``spice_lessons_c_unix.zip'' to ``cspice/doc/html'' and un-zip it
   there. Un-zipping the package in ``doc/html'' is required in order
   for the links in the lesson HTML documents to work.

   CAUTION: we recommend that you unzip the package in an OS terminal
   (command) window by changing to the toolkit's ``doc/html''
   subdirectory and then running ``unzip'' in it. If command line
   ``unzip'' is not available on your system (e.g. on Windows) and you
   have to use the file browser unzip (extract) capabilities, please
   make sure to specify the ``doc/html'' as your destination path.

   Since toolkit applications and complete SPICE documentation are not
   included in SpiceyPy, if you are using SpiceyPy we encourage you to
   install a CSPICE toolkit first, in addition to SpiceyPy, and then
   un-zip a Python lessons package in that toolkit's
   ``cspice/doc/html'' directory.
 
   Each package contains the ``index.html'' file and the ``lessons''
   directory with HTML versions of all lesson documents and
   subdirectories for individual hands-on lessons, nine in total. Each
   individual lesson subdirectory contains a text version of the lesson
   document, a PDF version of the lesson's introduction/diagram slides,
   and a ``kernels'' subdirectory containing all kernels needed for
   primary tasks of the lesson, arranged under kernel-type
   subdirectories. For example, the contents of the
   ``spice_lessons_c_unix.zip'' package are:

      |-- index.html
      |
      +-- lessons/
         |  
         |-- binary_pck_c.html
         |   ...
         |
         |-- binary_pck/
         |   |
         |   |-- binary_pck_c.txt
         |   |-- binary_pck_diagram.pdf
         |   |
         |   +-- kernels/
         |       |
         |       |-- fk/
         |       |   |
         |       |   +-- *.tf
         |       |...
         |       |
         |       +-- spk/
         |           |
         |           +-- *.bsp
         ...
   
   (Notice the document file name suffix for C lessons -- _c. Suffixes
   for other languages are different -- _f, _idl, _m, and _py.)
 
   The ``index.html'' file provided in the package contains links to
   all lesson HTML documents in addition to the links to the standard
   SPICE HTML documentation and is intended to replace the
   ``index.html'' file that was included in the toolkit. For
   replacement to take place during un-zipping you might be required to
   confirm that replacing is OK (i.e. if prompted by unzip, please
   respond "Replace All").
 
   NAIF suggests that you load the ``index.html'' file into your
   browser to get access to all lesson documents.

   NAIF also recommends that you write source code, build, and
   execute your lesson solution program(s) in the subdirectory
   having the name corresponding to the lesson you're working on.
   For example when working on the Remote Sensing lesson, do that under
   the ``doc/html/lessons/remote_sensing'' subdirectory. This will make
   it easier for you to check your solutions and meta-kernels against
   the lesson document example solutions, which all use relative kernel
   paths with respect to the lesson's subdirectory.