KPL/IK RPC Instrument kernel =========================================================================== This instrument kernel (I-kernel) contains RPC sensor parameters and field-of-view definitions. Version and Date --------------------------------------------------------------------------- Version 1.1 -- May 31, 2005 -- Boris Semenov, NAIF Updated RPC/MAG instrument names based on the feedback comments from Dr. Ingo Richter [7]. Version 1.0 -- March 15, 2005 -- Boris Semenov, NAIF/JPL Version number change for the first official release. Version 0.1 -- September 24, 2004 -- Boris Semenov, NAIF/JPL Initial release. Version 0.0 -- September 24, 2004 -- Boris Semenov, NAIF/JPL This version number was skipped. References --------------------------------------------------------------------------- 1. ``Kernel Pool Required Reading'' 2. ``C-kernel Required Reading'' 3. ``RPC EID, Part B'', ROS-EST-RO-3012/EID B, 2001-05-15 4. Rosetta Frames Definition Kernel (FK), latest version. 5. ``RPC User Manual'', RO-RPC-UM, 2002-05-30 6. ESA Science and Technology Web Server, Rosetta Instruments Area, http://sci.esa.int/science-e/www/object/index.cfm?fobjectid=35061 7. E-mail "ROSETTA RPC-MAG FK / IK Comments" from Dr. Ingo Richter, 2005/04/19. Implementation Notes -------------------------------------------------------- Applications that need SPICE I-kernel data must ``load'' the I-kernel file, normally during program initialization. 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''. The application program may then obtain the value(s) for any IK data item using the SPICELIB routines GDPOOL, GIPOOL, GCPOOL. Routine GETFOV may be used if the file contains instrument field-of-view (FOV) specification. See [1] for details. This file was created with, and can be updated with a text editor or word processor. 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 Rosetta instrument ID code, constructed using the spacecraft ID number (-226) followed by the NAIF three digit ID number for RPC sensor or structure. The IDs for RPC are defined in [4] as follows: Instrument name ID -------------------- ------- ROS_RPC -226500 ROS_RPC_LAP1 -226511 ROS_RPC_LAP2 -226512 ROS_RPC_LAP1_URF -226515 ROS_RPC_LAP2_URF -226516 ROS_RPC_IES -226520 ROS_RPC_IES_ELECTRON -226521 ROS_RPC_IES_ION -226522 ROS_RPC_IES_URF -226525 ROS_RPC_IES_QUAD1 -226526 (*) ROS_RPC_IES_QUAD2 -226527 (*) ROS_RPC_IES_QUAD3 -226528 (*) ROS_RPC_IES_QUAD4 -226529 (*) ROS_RPC_ICA -226530 ROS_RPC_ICA_URF -226535 ROS_RPC_ICA_QUAD1 -226536 (*) ROS_RPC_ICA_QUAD2 -226537 (*) ROS_RPC_ICA_QUAD3 -226538 (*) ROS_RPC_ICA_QUAD4 -226539 (*) ROS_RPC_MAG_OB -226541 ROS_RPC_MAG_IB -226542 ROS_RPC_MAG_OB_URF -226545 ROS_RPC_MAG_IB_URF -226546 ROS_RPC_MIP -226550 ROS_RPC_MIP_R1 -226551 ROS_RPC_MIP_T1 -226552 ROS_RPC_MIP_T2 -226553 ROS_RPC_MIP_R2 -226554 ROS_RPC_MIP_URF -226555 ROS_RPC_BOOM1 -226560 ROS_RPC_BOOM2 -226570 (*) The "_QUAD#" names and IDs for IES and ICA do not correspond to any of the sensor's physical structures. They are introduced to make possible an approximation of the sensor's FOV with four rectangular 90 x 90 degrees quadrants. The remainder of the keyword is an underscore character followed by the unique name of the data item. For example, the boresight of the RPC ICA QUAD3 FOV is specified by INS-226538_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 -------------------------------------------------------- From [6]: RPC (Rosetta Plasma Consortium) is a set of five instruments sharing a common electrical and data interface with the Rosetta orbiter. The RPC instruments are designed to make complementary measurements of the plasma environment around comet 67P/Churyumov-Gerasimenko. The RPC instruments are: * an Ion Composition Analyser, which measures the three-dimensional velocity distribution and mass distribution of positive ions; * an Ion and Electron Sensor, which will simultaneously measure the flux of electrons and ions in the plasma surrounding the comet,; * a Langmuir Probe, which will measure the density, temperature and flow velocity of the cometary plasma ; * a Fluxgate Magnetometer, which will measure the magnetic field in the region where the solar wind plasma interacts with the comet; and * a Mutual Impedance Probe, which will derive the electron gas density, temperature, and drift velocity in the inner coma of the comet. Mounting Alignment -------------------------------------------------------- Refer to the latest version of the Rosetta Frames Definition Kernel (FK) [4] for the RPC reference frame definitions and mounting alignment information. Boom-Mounted Sensor Locations -------------------------------------------------------- The locations of the boom-mounted RPC sensors -- MIP, MAG_OB/MAG_IB, and LAP1/LAP2 -- are provided in the Rosetta structures SPK file. Refer to the comments in that file for specifics of the data stored in it and for recipes for using that data. Sensor Sector Layout -------------------------------------------------------- This section contains assignments specifying the sensor layout by defining individual sector view directions for IES and ICA sensors. The combined aperture of each of the sensors is broken down into a number of equally or unequally spaced sectors to achieve the necessary spatial resolution within the sensor's sensor plane and in the direction normal to it. This table summarizes the individual sensor sector layout (based on [5]): --------- --------------------- --------------------- Sensor Number of Sectors Sector size, deg Name in-plane cross-plane in-plane cross-plane --------- -------- ----------- ---------- ----------- IES/E 16 18 22.5 5.0 IES/I 16 18 45.0/5.0(1) 5.0 ICA 16 16 22.5 5.0 --------- --------------------- --------------------- (1) IES/Ion has seven 45 degree sectors and nine 5 degree sectors. The parameters from the table are provided for each sensor using the following keywords: NUMBER_OF_SECTORS -- contains two integers for in-plane and cross-plane sector numbers SECTOR_SIZE -- contains two numbers for in-plane and cross-plane sector size, in degrees FRAME -- contains the name of the frame in which the sector view directions are defined SECTOR_DIRECTIONS -- contains sector center view directions for each sector in the sensor symmetry plane. The order of vectors in the SECTOR_DIRECTIONS is different for different sensors. It is described for each particular sensor in that sensor's section of this IK. Section "IK Code Example" provided at the bottom of file includes a example C function and an example FORTRAN subroutine that can be used to retrieve values of these parameters for a specifies sensor. IES/Electron Sector Layout [This section is TBD until information about sector numbering and relationship to the sensor frame is provided by the RPC team; see IMA section of the MEX ASPERA IK for an example of how it will be done once the information is available.] IES/Ion Sector Layout [This section is TBD until information about sector numbering and relationship to the sensor frame is provided by the RPC team; see IMA section of the MEX ASPERA IK for an example of how it will be done once the information is available.] ICA Sector Layout [This section is TBD until information about sector numbering and relationship to the sensor frame is provided by the RPC team; see IMA section of the MEX ASPERA IK for an example of how it will be done once the information is available.] FOV Definitions --------------------------------------------------------------------------- This section contains definitions for the RPC IES and ICA quadrant 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 IES ICA quadrant FOV as 90 x 90 degrees rectangles centered around +X, +Y, -X, and -Y axes of the corresponding instrument frames. These FOVs do NOT represent actual sensor sector FOVs. Instead the combination of the four quadrant FOVs for each sensor serves as an approximation of the total 90 x 360 degrees toroidal FOV of the sensor. \begindata INS-226526_FOV_FRAME = 'ROS_RPC_IES' INS-226526_FOV_SHAPE = 'RECTANGLE' INS-226526_BORESIGHT = ( 1.000000 0.000000 0.000000 ) INS-226526_FOV_CLASS_SPEC = 'ANGLES' INS-226526_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226526_FOV_REF_ANGLE = ( 45.0 ) INS-226526_FOV_CROSS_ANGLE = ( 45.0 ) INS-226526_FOV_ANGLE_UNITS = 'DEGREES' INS-226527_FOV_FRAME = 'ROS_RPC_IES' INS-226527_FOV_SHAPE = 'RECTANGLE' INS-226527_BORESIGHT = ( 0.000000 1.000000 0.000000 ) INS-226527_FOV_CLASS_SPEC = 'ANGLES' INS-226527_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226527_FOV_REF_ANGLE = ( 45.0 ) INS-226527_FOV_CROSS_ANGLE = ( 45.0 ) INS-226527_FOV_ANGLE_UNITS = 'DEGREES' INS-226528_FOV_FRAME = 'ROS_RPC_IES' INS-226528_FOV_SHAPE = 'RECTANGLE' INS-226528_BORESIGHT = ( -1.000000 0.000000 0.000000 ) INS-226528_FOV_CLASS_SPEC = 'ANGLES' INS-226528_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226528_FOV_REF_ANGLE = ( 45.0 ) INS-226528_FOV_CROSS_ANGLE = ( 45.0 ) INS-226528_FOV_ANGLE_UNITS = 'DEGREES' INS-226529_FOV_FRAME = 'ROS_RPC_IES' INS-226529_FOV_SHAPE = 'RECTANGLE' INS-226529_BORESIGHT = ( 0.000000 -1.000000 0.000000 ) INS-226529_FOV_CLASS_SPEC = 'ANGLES' INS-226529_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226529_FOV_REF_ANGLE = ( 45.0 ) INS-226529_FOV_CROSS_ANGLE = ( 45.0 ) INS-226529_FOV_ANGLE_UNITS = 'DEGREES' INS-226536_FOV_FRAME = 'ROS_RPC_ICA' INS-226536_FOV_SHAPE = 'RECTANGLE' INS-226536_BORESIGHT = ( 1.000000 0.000000 0.000000 ) INS-226536_FOV_CLASS_SPEC = 'ANGLES' INS-226536_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226536_FOV_REF_ANGLE = ( 45.0 ) INS-226536_FOV_CROSS_ANGLE = ( 45.0 ) INS-226536_FOV_ANGLE_UNITS = 'DEGREES' INS-226537_FOV_FRAME = 'ROS_RPC_ICA' INS-226537_FOV_SHAPE = 'RECTANGLE' INS-226537_BORESIGHT = ( 0.000000 1.000000 0.000000 ) INS-226537_FOV_CLASS_SPEC = 'ANGLES' INS-226537_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226537_FOV_REF_ANGLE = ( 45.0 ) INS-226537_FOV_CROSS_ANGLE = ( 45.0 ) INS-226537_FOV_ANGLE_UNITS = 'DEGREES' INS-226538_FOV_FRAME = 'ROS_RPC_ICA' INS-226538_FOV_SHAPE = 'RECTANGLE' INS-226538_BORESIGHT = ( -1.000000 0.000000 0.000000 ) INS-226538_FOV_CLASS_SPEC = 'ANGLES' INS-226538_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226538_FOV_REF_ANGLE = ( 45.0 ) INS-226538_FOV_CROSS_ANGLE = ( 45.0 ) INS-226538_FOV_ANGLE_UNITS = 'DEGREES' INS-226539_FOV_FRAME = 'ROS_RPC_ICA' INS-226539_FOV_SHAPE = 'RECTANGLE' INS-226539_BORESIGHT = ( 0.000000 -1.000000 0.000000 ) INS-226539_FOV_CLASS_SPEC = 'ANGLES' INS-226539_FOV_REF_VECTOR = ( 0.000000 0.000000 1.00000 ) INS-226539_FOV_REF_ANGLE = ( 45.0 ) INS-226539_FOV_CROSS_ANGLE = ( 45.0 ) INS-226539_FOV_ANGLE_UNITS = 'DEGREES' \begintext Platform ID --------------------------------------------------------------------------- This number is the NAIF instrument ID of the platform on which the sensors are mounted. For IES and ICA sensors this platform is the spacecraft; for MIP and LAP1 this platform is Boom 1; for MAG_OB, MAG_IB, and LAP2 this platform is Boom 2. \begindata INS-226520_PLATFORM_ID = ( -226000 ) INS-226530_PLATFORM_ID = ( -226000 ) INS-226550_PLATFORM_ID = ( -226560 ) INS-226511_PLATFORM_ID = ( -226560 ) INS-226541_PLATFORM_ID = ( -226570 ) INS-226542_PLATFORM_ID = ( -226570 ) INS-226512_PLATFORM_ID = ( -226570 ) \begintext IK Code Example --------------------------------------------------------------------------- This section contains an example code, in C and FORTRAN, illustrating how geometry parameters for a given sensor can be retrieved using appropriate SPICE routine. Both examples are presented as stand-alone functions with SPICE-style header, ready to be cut-n-paste and called from an application. [TBD; see MEX ASPERA IK for similar example]