KPL/IK JMC Instrument kernel =========================================================================== This instrument kernel (I-kernel) contains JUICE Monitoring Camera (JMC) optics, detector, and field-of-view parameters. Version and Date --------------------------------------------------------------------------- Version 0.2 -- April 8, 2021 -- Alfredo Escalante Lopez, ESAC/ESA Updated FOV angles to be consistent with [4]. Version 0.1 -- October 30, 2019 -- Marc Costa Sitja, ESAC/ESA Updated FOV from Circle to square. Version 0.0 -- October 24, 2016 -- Marc Costa Sitja, ESAC/ESA Initial Release based on the Mars Express Visual Monitoring Camera (VMC) 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 3, Airbus Defense and Space, 25 November 2018 5. ``Product Overview - HAS2: High Accuracy Star Tracker CMOS Active Pixel Image Sensor'', ON Semiconductor, 24 October 2016 6. ``JMC Instrument User Manual'', JUI-MCSE-JMC-MAN-000001, Issue 1, Micro-Cameras & Space Exploration SA, 12 March 2019 Contact Information ------------------------------------------------------------------------ If you have any questions regarding this file contact SPICE support at ESAC: Alfredo Escalante Lopez (+34) 91-8131-429 spice@sciops.esa.int or NAIF at JPL: Boris Semenov (818) 354-8136 Boris.Semenov@jpl.nasa.gov 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 [3]. All keywords referencing values in this I-kernel start with the characters `INS' followed by the NAIF JUICE instrument ID code. The JMC instrument IDs are defined in [3] as follows: Instrument name ID -------------------- ------- JUICE_JMC-1 -28081 JUICE_JMC-2 -28082 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 Monitoring Camera 1 (JMC-1) is specified by INS-28081_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 JUICE monitoring cameras are accommodated to enhance the observability of the spacecraft and its instruments, at marginal impact on spacecraft design and its budgets (power, mass). The monitoring cameras observe the deployable appendices in critical situations (especially main engine firing) and will produce stunning pictures of the spacecraft flying by Jupiter and its moons. The key objectives of the monitoring cameras are: - Provide low-rate video of solar generator and instruments booms deployment after launcher separation and LEOP phase; and during / after main engine firings; - Provide low-rate video of JUICE spacecraft arrival in the moon orbits of Jupiter, during the last 4 years of mission lifetime, after 8 years of interplanetary transfer. The small size of the camera (100 x 100 x 100 mm) helps to accommodate it on the optimum position, here also without impact on spacecraft design. The first camera is accommodated on the bottom of the +X wall, looking in +Z/+Y direction toward RIME +X antenna and +Y solar wing. The second camera is accommodated on the top of the +Z/+Y edge, looking towards –X/-Y allowing to monitor the first hinges of RIME –X antenna. Both cameras thus benefit from the +X spacecraft face favourable environment (no direct Sun illumination). Aparent FOV Layout -------------------------------------------------------- The JMC cameras comprise a single square CMOS detector. The view directions of the corners and the axes of the JUICE_JMC frame look like these: JMC-1 ----- ^ +Xjmc1 | | --- +---------|---------+ ^ (+Xsc)^ | | | 93deg | \ | | | | \ | | | | \| | | 1024 | x-------------> +Yjmc1 | lines | / +Zjmc1 | (+Ysc) | | / | | | / | V | V(+Zsc) | --- Pixel (0,0)-----------------+ 1024 pixels/line | 93 deg | Boresight (+Z axis) |<----------------->| is into the page | | JMC-2 ----- ^ +Xjmc2 | | --- +---------|---------+ ^ (+Xsc)^ | ^(+Zsc) | 93deg | \ | / | | | \ | / | | | \|/ | | 1024 | x-------------> +Yjmc2 | lines | +Zjmc2 | (+Ysc) | | | | | | V | | --- Pixel (0,0)-----------------+ 1024 pixels/line | 93 deg | Boresight (+Z axis) |<----------------->| is into the page | | 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 +Xjmc and +Yjmc axes is such that line and column number counts increase with increasing coordinate value. Mounting Alignment -------------------------------------------------------- Refer to the latest version of the JUICE Frames Definition Kernel (FK) [3] for the JMC reference frames definitions and mounting alignment information. Optical Parameters -------------------------------------------------------- The following JMC optical parameters are included in the data section below, from [6]: ----------------------------------------- parameter value ----------------------------------------- Focal Length, mm TBD f/ratio TBD Field of view (deg) along Xcam 93 along Ycam 93 Pixel Angular Size (arcsec) 326.95 ----------------------------------------- The keywords below provide nominal data for both cameras. Angular size values in the keywords are given in radians, with the Xcam size being the first value and the Ycam size being the second value in each pair. \begindata INS-28081_FOV_ANGULAR_SIZE = ( 1.623142, 1.623142 ) INS-28081_IFOV = ( 0.0015851 ) INS-28082_FOV_ANGULAR_SIZE = ( 1.623142, 1.623142 ) INS-28082_IFOV = ( 0.0015851 ) \begintext Detector CMOS Parameters -------------------------------------------------------- The JMC CMOS detectors geometry parameters are included in the data section below, taken from [5]: --------------------------------------------- parameter JMC --------------------------------------------- Detector Array Size, pixels Cross-track 1024 Along-track 1024 Detector Array Center, pixels Cross-track 512 Along-track 512 --------------------------------------------- The values are given in counts for PIXEL_SAMPLES, PIXEL_LINES, and CENTER keywords. \begindata INS-28081_PIXEL_SAMPLES = ( 1024 ) INS-28081_PIXEL_LINES = ( 1024 ) INS-28081_CCD_CENTER = ( 512, 512 ) INS-28082_PIXEL_SAMPLES = ( 1024 ) INS-28082_PIXEL_LINES = ( 1024 ) INS-28082_CCD_CENTER = ( 512, 512 ) \begintext FOV Definitions --------------------------------------------------------------------------- The set of assignments in the data section below defines the JMC-1 and JMC-2 FOVs with respect to the corresponding frame to be rectangles with the corners defined by CMOS and the boresight along the +Z axis. These FOV definitions use angular extent style specification with the cross and along track angular sizes taken from the ``Optics Parameters'' section above. This FOV definition corresponds to the NAIF Body Name: JUICE_JMC. Please note that the FOV reference and cross angles are defined with half angle values. \begindata INS-28081_FOV_FRAME = 'JUICE_JMC-1' INS-28081_FOV_SHAPE = 'RECTANGLE' INS-28081_BORESIGHT = ( 0.000, 0.000, 1.000 ) INS-28081_FOV_CLASS_SPEC = 'ANGLES' INS-28081_FOV_REF_VECTOR = ( 0.000, 1.000, 0.000 ) INS-28081_FOV_REF_ANGLE = ( 46.5 ) INS-28081_FOV_CROSS_ANGLE = ( 46.5 ) INS-28081_FOV_ANGLE_UNITS = 'DEGREES' INS-28082_FOV_FRAME = 'JUICE_JMC-2' INS-28082_FOV_SHAPE = 'RECTANGLE' INS-28082_BORESIGHT = ( 0.000, 0.000, 1.000 ) INS-28082_FOV_CLASS_SPEC = 'ANGLES' INS-28082_FOV_REF_VECTOR = ( 0.000, 1.000, 0.000 ) INS-28082_FOV_REF_ANGLE = ( 46.5 ) INS-28082_FOV_CROSS_ANGLE = ( 46.5 ) INS-28082_FOV_ANGLE_UNITS = 'DEGREES' \begintext Optical Distortion -------------------------------------------------------- [TBD]. Platform ID --------------------------------------------------------------------------- This number is the NAIF instrument ID of the platform on which the cameras are mounted. For both cameras this platform is the spacecraft. \begindata INS-28081_PLATFORM_ID = ( -28000 ) INS-28082_PLATFORM_ID = ( -28000 ) \begintext End of IK file.