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.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 1, Airbus Defense and Space, 4 December 2015 5. ``Product Overview - HAS2: High Accuracy Star Tracker CMOS Active Pixel Image Sensor'', ON Semiconductor, 24 October 2016 Contact Information ------------------------------------------------------------------------ If you have any questions regarding this file contact SPICE support at ESAC: Marc Costa Sitja (+34) 91-8131-457 mcosta@sciops.esa.int, esa_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 [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_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. The second camera is accommodated on the top of the +X side, looking towards –Z/-Y. Both cameras thus benefit from the +X S/C face favourable environment (no direct Sun illumination). 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. Detector 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 this: ^ +Xjmc | (+Xsc) | --- +---------|---------+ ^ | | | | 70deg | | | | | | | | | | | | 1024 | x-------------> +Yjmc | lines | +Zjmc | (+Ysc) | | | | | | V | | --- Pixel (0,0)-----------------+ 1024 pixels/line | 70 deg | Boresight (+Z axis) |<----------------->| is into the page | | Optical Parameters -------------------------------------------------------- [TBD]. Detector CMOS Parameters -------------------------------------------------------- The JMC CMOS detectors geometry parameters are included in the data section below, taken from [5]: --------------------------------------------- parameter JMC --------------------------------------------- Detector Array Size Cross-track 1024 Along-track 1024 Detector Array Center 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 Wavelength Ranges --------------------------------------------------------------------------- [TBD]. 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 = 'CIRCLE' 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 = ( 35 ) INS-28081_FOV_ANGLE_UNITS = 'DEGREES' INS-28082_FOV_FRAME = 'JUICE_JMC-2' INS-28082_FOV_SHAPE = 'CIRCLE' 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 = ( 35 ) INS-28082_FOV_ANGLE_UNITS = 'DEGREES' \begintext Optical Distortion -------------------------------------------------------- [TBD]. End of IK file.