JUICE DSK files ============================================================================== This ``aareadme.txt'' file describes the contents of the kernels/dsk directory of the JUICE SPICE data server. It was last modified on May 21, 2024 by Rafael Andres Blasco, ESAC/ESA. Contact Information ----------------------------------------------------------------------------- If you have any questions regarding this file contact the ESA SPICE Service (ESS) at ESAC: Alfredo Escalante Lopez (+34) 91-8131-429 spice@sciops.esa.int or the JUICE Science Operations Center at ESAC: Marc Costa Sitja (+34) 646-746-711 Marc.Costa@ext.esa.int References and required readings ----------------------------------------------------------------------------- 1. ``Frames Required Reading'', NAIF Document 2. ``DS-Kernel Required Reading'', NAIF Document Brief Summary ----------------------------------------------------------------------------- This directory contains the SPICE DS-Kernel files for the JUICE spacecraft, its structures, science instruments, plasma tori, and Jupiter rings. File naming conventions ----------------------------------------------------------------------------- JUICE mission DSK: The naming scheme for the JUICE mission DSK is: juice_BODY_[STRUC]_vNN.bc where BODY spacecraft/model/body identifier: sc: for JUICE spacecraft; io: for Io; europa: for Europa; jup_halo_ring: for Jupiter Halo ring; jup_main_ring: for Jupiter Main ring; jup_ama_gos_ring: for Jupiter Amalthea Gossamer ring; jup_the_gos_ring: for Jupiter Thebe Gossamer ring; jup_the_ring_ext: for Jupiter Thebe extension; STRUC instrument/structure/sensor identifier (optional): bus: for the JUICE spacecraft bus; fixed: for the spacecraft non-movable components; sapy: for the solar array in the +Y direction; samy: for the solar array in the -Y direction; mga_apm: for the medium gain antenna APM; mga_dish: for the medium gain antenna dish; lpbN: for the N Langmuir probe; rimepx: for the RIME in the +X direction; rimemx: for the RIME in the -X direction; strN: for the N star tracker; jmcN: for the N JUICE Monitoring Camera; gala: for the GAnymede Laser Altimeter; janus: for the JANUS camera system; mag: for the magnetometer boom; navcamN: for the navigation camera; pep_jdc: for the PEP JDC unit; pep_jei: for the PEP JEI unit; pep_jeni: for the PEP JENI unit; pep_jna: for the PEP JNA unit; pep_nim: for the PEP NIM unit; swi: for the Sub-millimeter Wave Instrument; uvs: for the Ultraviolet Spectrograph; plasma_torus: for the plasma torus; NN CK version number -- 2 digits (required). If multiple versions of a DS-Kernel file are provided, always use the latest version (unless earlier version is needed for some special reasons.) Other directory contents ----------------------------------------------------------------------------- aareadme.txt This file. Particulars ----------------------------------------------------------------------------- JUICE in-situ and possibly J-MAG payload are interested in knowing when a particular sensor is illuminated or in shade, or when the spacecraft structures are blocking the solar wind, or particles coming in a particular direction defined by a dynamic frame of interest (one of the exiting scientific frames for these instruments). Up until the expansion of SPICE with the DTM capabilities, these checks were performed by defining "engineering" field-of-views for these instruments, using the location of each of these sensors within the spacecraft and the corner points of the spacecraft bus and solar panels. This was a complex modeling, which in some cases was not feasible due to the type of frames of interest or illumination sources' nature. With the new DTM capabilities, and by modeling the JUICE spacecraft as an irregularly shaped extended ephemerides object, it is possible to exploit the full capabilities of the DTM subsystem to find out whether these conditions are met or not given a particular attitude profile of the spacecraft at a given time. Kernel File Details ----------------------------------------------------------------------------- The most detailed description of the data in a binary DSK file is provided in metadata included inside the comment area of the file. This information can be viewed using the utility programs COMMNT and SPACIT included in the NAIF Toolkit. End of aareadme file.