KPL/IK NAVCAM Instrument kernel =========================================================================== This instrument kernel (I-kernel) contains JUICE Navigation Camera (NAVCAM) optics, detector, and field-of-view parameters. Version and Date --------------------------------------------------------------------------- Version 0.0 -- October 24, 2016 -- Marc Costa Sitja, ESAC/ESA Initial Release based on the Rosetta Navigation Camera (NAVCAM) instrument kernel. References --------------------------------------------------------------------------- 1. ``Kernel Pool Required Reading'' 2. ``C-kernel Required Reading'' 3. JUICE Frames Definition Kernel (FK), latest version. 4. ``JUICE Spacecraft Design Report'', JUI-ADST-SYS-DD-000122, Issue 1, Airbus Defense and Space, 4 December 2015 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 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 JUICE instrument ID code. The Star Tracker instrument IDs are defined in [1] as follows: Instrument name ID -------------------- ------- JUICE_NAVCAM-1 -28051 JUICE_NAVCAM-2 -28052 The remainder of the keyword is an underscore character followed by the unique name of the data item. For example, the boresight of the JUICE NavCam 1 (NAVCAM-1) is specified by INS-28051_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. Overview --------------------------------------------------------------------------- The two JUICE Navigation Cameras (NavCam) are accommodated on the optical bench close to the STR-OH providing high pointing accuracy and stability to all the units. Navigation camera boresight axes are aligned to the spacecraft nadir-pointed axis (+Z). A potential small angular offset by 1.5 degrees in the – X direction will be investigated later (decision can be deferred late in the project). Indeed it would have an interest for the Closed Loop Attitude Guidance concept implemented in the baseline, to maximise the limb measurements availability prior to the flybys closest approach, thus improving navigation and therefore pointing performance. The spacecraft +X axis is always in the shadow during flybys for thermal constraints, so the camera boresight would be off-pointed towards the moon lit limb during the approach, which may improve the performance. Apparent FOV Layout --------------------------------------------------------------------------- This section provides a diagram illustrating the NAVCAM apparent FOV layout in the corresponding reference frames. ^ +Xcam | (+Xsc) | --- +---------|---------+ ^ | | | | 4 deg | | | | | | | | | | | | 1024 | x-------------> +Ycam | lines | +Zcam | (+Ysc) | | | | | | V | | --- Pixel (0,0)-----------------+ 1024 pixels/line | 4 deg | Boresight (+Z axis) |<----------------->| is into the page | | Nominally the +Xcam and +Ycam axes are co-aligned with the respective spacecraft reference frame axes +Xsc and +Ysc. According to the chosen convention the pixel coordinates start with zero in the lower left corner in the orientation shown in the sketch above. The orientation of the +Xcam and +Ycam axes is such that line and column number counts increase with increasing coordinate value. However, the optics of the instrument introduces an inversion of the image. This means that the signs of both coordinate values need to be reversed when transforming the position of an object in space into image coordinates. Or in other words, the image needs to be rotated by 180 degrees in order to match the orientation of the imaged scene. Mounting Alignment --------------------------------------------------------------------------- Refer to the latest version of the JUICE Frames Definition Kernel (FK) [1] for the NAVCAM reference frame definitions and mounting alignment information. Optical Parameters --------------------------------------------------------------------------- [TBD]. CCD Parameters --------------------------------------------------------------------------- [TBD]. FOV Definitions --------------------------------------------------------------------------- This section contains definitions for the NAVCAM 1 and 2 FOVs. These definitions are provided in the format required by the SPICE (CSPICE) function GETFOV (getfov_c). The set of assignments in the data section below defines the NAVCAM-1/2 FOV with respect to the JUICE_NAVCAM-1/2 frame to be a rectangle with the corners defined by the first and last pixels of the first and last lines of the CCD and the boresight along the +Z axis of the JUICE_NAVCAM-1/2 frame. This FOV definition uses angular extent style specification with the angular sizes along the Xcam and Ycam axes taken from the 'Optical Parameters' section above. \begindata INS-28051_FOV_FRAME = 'JUICE_NAVCAM-1' INS-28051_FOV_SHAPE = 'RECTANGLE' INS-28051_BORESIGHT = (0.0 0.0 1.0) INS-28051_FOV_CLASS_SPEC = 'ANGLES' INS-28051_FOV_REF_VECTOR = (1.0 0.0 0.0) INS-28051_FOV_REF_ANGLE = ( 2.000 ) INS-28051_FOV_CROSS_ANGLE = ( 2.000 ) INS-28051_FOV_ANGLE_UNITS = 'DEGREES' INS-28052_FOV_FRAME = 'JUICE_NAVCAM-2' INS-28052_FOV_SHAPE = 'RECTANGLE' INS-28052_BORESIGHT = (0.0 0.0 1.0) INS-28052_FOV_CLASS_SPEC = 'ANGLES' INS-28052_FOV_REF_VECTOR = (1.0 0.0 0.0) INS-28052_FOV_REF_ANGLE = ( 2.000 ) INS-28052_FOV_CROSS_ANGLE = ( 2.000 ) INS-28052_FOV_ANGLE_UNITS = 'DEGREES' \begintext Optical Distortion --------------------------------------------------------------------------- [TBD]. End of IK file.