version from IKI

KPL/IK

ExoMars Surface Platform (ExoMars-20) Instrument Kernel

===============================================================================

   This frame kernel contains a complete set of field of view definitions 

   for the surface platform television system (TSPP):

   SP_TS_CAM_1, SP_TS_CAM_2, SP_TS_CAM_3, SP_TS_CAM_4. 

Version and Date

------------------------------------------------------------------------

   Version 0.0.0-draft -- January 21, 2020 -- Stanislav Bober, IKI

      Draft Version. Based on emrsp_rm_navcam_v001.ti.

References

-------------------------------------------------------------------------------

   1. SP Frames Definition Kernel (FK), latest version

   2. ''Kernel Pool Required Reading''

   3. Программа научных исследований ПНИ-12022019.docx

Contact Information

-------------------------------------------------------------------------------

   If you have any questions regarding this file contact SPICE support at

   ESA:

           Marc Costa Sitja

           (+34) 91-8131-457

           mcosta@sciops.esa.int, esa_spice@sciops.esa.int

   or ROCC at Altec Space:

           Federico Salvioli

           +1 (818) 354-8136

           federico.salvioli@altecspace.it

   or SPICE support at IKI:

           Alexander Abbakumov

           +7 (495) 333-40-13

           aabbakumov@romance.iki.rssi.ru

           Stanislav Bober

           +7 (985) 285-24-94

           stasbober@rlab.iki.rssi.ru

Implementation Notes

-------------------------------------------------------------------------------

   Applications that need SPICE I-kernel data must ``load'' the I-kernel file,

   normally during program initialization. The SPICE routine FURNSH loads a

   kernel file into the pool as shown below.

      CALL FURNSH ( 'frame_kernel_name' )    -- FORTRAN

      furnsh_c ( "frame_kernel_name" );      -- C

      cspice_furnsh, frame_kernel_name       -- IDL

      cspice_furnsh( 'frame_kernel_name' )   -- MATLAB

      spiceypy.furnsh( 'frame_kernel_name' ) -- PYTHON

   Loading the kernel using the SPICELIB routine FURNSH causes the data

   items and their associated values present in the kernel to become

   associated with a data structure called the ``kernel pool''.

   Once the file has been loaded, the SPICE routine GETFOV (getfov_c in

   C, cspice_getfov in IDL and MATLAB) can be used to retrieve FOV

   parameters for a given instrument or structure.

   The application program may obtain the value(s) for any other IK data

   item using the SPICELIB routines GDPOOL, GIPOOL, GCPOOL (gdpool_c, gipool_c,

   gcpool_c in C, cspice_gdpool, cspice_gipool, cspice_gcpool in IDL and

   MATLAB). See [1] for details.

   This file was created with, and can be updated with a text editor or

   word processor.

Naming Conventions and Conventions for Specifying Data

-------------------------------------------------------------------------------

   Data items are specified using ``keyword=value'' assignments [1].

   All keywords referencing values in this I-kernel start with the

   characters `INS' followed by the NAIF RM instrument ID code.

               Instrument name          ID

               --------------------     -------

               SP_TS_CAM_1              -173011

               SP_TS_CAM_2              -173012

               SP_TS_CAM_3              -173013

               SP_TS_CAM_4              -173014

   The remainder of the keyword is an underscore character followed by

   the unique name of the data item. For example, the boresight of

   the SP_TS_CAM_1 is specified by

               INS-173011_BORESIGHT

   The upper bound on the length of all keywords is 32 characters.

   If a keyword is included in more than one file, or if the same

   keyword appears more than once within a single file, the last

   assignment supersedes any earlier assignments.

Apparent FOV Layout

---------------------------------------------------------------------------

   This section provides a diagram illustrating the SP_TS_CAM_1, SP_TS_CAM_2, 

   SP_TS_CAM_3, SP_TS_CAM_4 detectors apparent FOVs layout in the corresponding

   reference frames.

   The SP_TS_CAM surface slit creates a rectangular field of view with half cone

   angle of 57.5 degrees. The following diagrams illustrate the above field of

   view in the instrument frame:

                 Y                                 X

                  ins                               ins

                ^     /                           ^     /

                |    /                            |    /

                |   /                             |   /

                |  /                              |  /

           X    | /    o                     Y    | /    o

            ins |/ 57.5                       ins |/ 57.5

                x-------->                        o-------->

                |\         Z                      |\         Z

                | \         ins                   | \         ins

                |  \                              |  \

                |   \                             |   \

                |    \                            |    \

                |     \                           |     \

                              Plane X = 0                       Plane Y = 0

   Please note that the FOV reference and cross angles are defined with half

   angle values.

FOV Definitions

-------------------------------------------------------------------------------

   This section contains definitions for the NavCam FOVs. These definitions

   are provided in the format required by the SPICE (CSPICE) function GETFOV

   (getfov_c).

   Please note that the FOV reference and cross angles are defined with half

   angle values. The FoV definition corresponds to the NAIF Body Name:

   SP_TS_CAM_1, SP_TS_CAM_2, SP_TS_CAM_3, SP_TS_CAM_4.

\begindata

INS-173011_FOV_CLASS_SPEC       = 'ANGLES'

INS-173011_FOV_SHAPE            = 'RECTANGLE'

INS-173011_FOV_FRAME            = 'SP_TS_CAM_1'

INS-173011_BORESIGHT            = ( 0.0, 0.0, 1.0 )

INS-173011_FOV_REF_VECTOR       = ( 1.0, 0.0, 0.0 )

INS-173011_FOV_REF_ANGLE        = ( 57.5 )

INS-173011_FOV_CROSS_ANGLE      = ( 57.5 )

INS-173011_FOV_ANGLE_UNITS      = ( 'DEGREES' )

INS-173012_FOV_CLASS_SPEC       = 'ANGLES'

INS-173012_FOV_SHAPE            = 'RECTANGLE'

INS-173012_FOV_FRAME            = 'SP_TS_CAM_2'

INS-173012_BORESIGHT            = ( 0.0, 0.0, 1.0 )

INS-173012_FOV_REF_VECTOR       = ( 1.0, 0.0, 0.0 )

INS-173012_FOV_REF_ANGLE        = ( 57.5 )

INS-173012_FOV_CROSS_ANGLE      = ( 57.5 )

INS-173012_FOV_ANGLE_UNITS      = ( 'DEGREES' )

INS-173013_FOV_CLASS_SPEC       = 'ANGLES'

INS-173013_FOV_SHAPE            = 'RECTANGLE'

INS-173013_FOV_FRAME            = 'SP_TS_CAM_3'

INS-173013_BORESIGHT            = ( 0.0, 0.0, 1.0 )

INS-173013_FOV_REF_VECTOR       = ( 1.0, 0.0, 0.0 )

INS-173013_FOV_REF_ANGLE        = ( 57.5 )

INS-173013_FOV_CROSS_ANGLE      = ( 57.5 )

INS-173013_FOV_ANGLE_UNITS      = ( 'DEGREES' )

INS-173014_FOV_CLASS_SPEC       = 'ANGLES'

INS-173014_FOV_SHAPE            = 'RECTANGLE'

INS-173014_FOV_FRAME            = 'SP_TS_CAM_4'

INS-173014_BORESIGHT            = ( 0.0, 0.0, 1.0 )

INS-173014_FOV_REF_VECTOR       = ( 1.0, 0.0, 0.0 )

INS-173014_FOV_REF_ANGLE        = ( 57.5 )

INS-173014_FOV_CROSS_ANGLE      = ( 57.5 )

INS-173014_FOV_ANGLE_UNITS      = ( 'DEGREES' )

\begintext

 No newline at end of file