Changes for v0.2.0 including LocCams, ADRON-RM and ISEM FK and IK updates. (c5bf7ca3) · Commits · Alessandro Frigeri / MaMISSspice

kernels/fk/emrsp_mlg_00_v00.tf→kernels/fk/emrsp_mlg_00_v01.tf

+14 −14

Original line number	Diff line number	Diff line
		@@ -19,7 +19,7 @@ KPL/FK
		\begindata

		NAIF_BODY_NAME += 'RM_SITE_DISPOSAL'
		NAIF_BODY_CODE += -999900
		NAIF_BODY_CODE += -174900

		\begintext

		@@ -56,19 +56,19 @@ KPL/FK

		\begindata

		FRAME_RM_MLG_DISPOSAL = -999900
		FRAME_-999900_NAME = 'RM_MLG_DISPOSAL'
		FRAME_-999900_CLASS = 4
		FRAME_-999900_CLASS_ID = -999900
		FRAME_-999900_CENTER = -999900
		FRAME_RM_MLG_DISPOSAL = -174900
		FRAME_-174900_NAME = 'RM_MLG_DISPOSAL'
		FRAME_-174900_CLASS = 4
		FRAME_-174900_CLASS_ID = -174900
		FRAME_-174900_CENTER = -174900

		OBJECT_-999900_FRAME = 'RM_MLG_DISPOSAL'
		OBJECT_-174900_FRAME = 'RM_MLG_DISPOSAL'

		TKFRAME_-999900_RELATIVE = 'IAU_MARS'
		TKFRAME_-999900_SPEC = 'ANGLES'
		TKFRAME_-999900_UNITS = 'DEGREES'
		TKFRAME_-999900_AXES = ( 3, 2, 3 )
		TKFRAME_-999900_ANGLES = ( -335.4500000000000,
		TKFRAME_-174900_RELATIVE = 'IAU_MARS'
		TKFRAME_-174900_SPEC = 'ANGLES'
		TKFRAME_-174900_UNITS = 'DEGREES'
		TKFRAME_-174900_AXES = ( 3, 2, 3 )
		TKFRAME_-174900_ANGLES = ( -335.4500000000000,
		-71.8000000000000,
		270.0000000000000 )

		@@ -84,7 +84,7 @@ Definitions file pinpoint.defs

		RM_SITE_DISPOSAL_CENTER = 499
		RM_SITE_DISPOSAL_FRAME = 'IAU_MARS'
		RM_SITE_DISPOSAL_IDCODE = -999900
		RM_SITE_DISPOSAL_IDCODE = -174900
		RM_SITE_DISPOSAL_LATLON = ( 18.20 335.45 0 )
		RM_SITE_DISPOSAL_BOUNDS = ( @2020-01-01T00:00:00, @2100-01-01 )

		@@ -92,7 +92,7 @@ Definitions file pinpoint.defs
		RM_SITE_DISPOSAL_NORTH = 'Y'

		RM_SITE_DISPOSAL_TOPO_FRAME = 'RM_MLG_DISPOSAL'
		RM_SITE_DISPOSAL_TOPO_ID = -999900
		RM_SITE_DISPOSAL_TOPO_ID = -174900

		begintext

kernels/fk/emrsp_rm_v00.tf→kernels/fk/emrsp_rm_v01.tf

+636 −254

File changed and moved.

Preview size limit exceeded, changes collapsed.

kernels/ik/emrsp_rm_adron-rm_v00.ti

0 → 100644

+184 −0

Original line number	Diff line number	Diff line
		KPL/IK

		ADRON-RM Instrument kernel
		===============================================================================

		This instrument kernel (I-kernel) contains the Autonomous Detector of
		Radiation of Neutrons Onboard Rover (ADRON-RM) optics, detector, and
		field-of-view parameters.


		Version and Date
		-------------------------------------------------------------------------------

		Version 0.0 -- February 7, 2019 -- Marc Costa Sitja, ESA/ESAC

		Preliminary Version.


		References
		-------------------------------------------------------------------------------

		1. RM Frames Definition Kernel (FK), latest version

		2. ''Kernel Pool Required Reading''

		3. ``The ADRON-RM Instrument Onboard the ExoMars Rover'', I.G. Mitrofanov
		et al, ASTROBIOLOGY, Volume 17, Numbers 6 and 7, 2017,
		DOI:10.1089/ast.2016.1548


		Contact Information
		-------------------------------------------------------------------------------

		If you have any questions regarding this file contact SPICE support at
		ESA:

		Marc Costa Sitja
		(+34) 91-8131-457
		mcosta@sciops.esa.int, esa_spice@sciops.esa.int

		or ROCC at Altec Space:

		Federico Salvioli
		+1 (818) 354-8136
		federico.salvioli@altecspace.it


		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
		spiceypy.furnsh( 'frame_kernel_name' ) -- PYTHON

		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 RM instrument ID code.
		The ADRON-RM instrument IDs are defined in [1] as follows:

		Instrument name ID
		-------------------- -------
		RM_ADRON-RM -174300


		The remainder of the keyword is an underscore character followed by
		the unique name of the data item. For example, the boresight of
		the RM_ADRON-RM is specified by

		INS-174300_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
		-------------------------------------------------------------------------------

		TBD.


		Apparent FOV Layout
		---------------------------------------------------------------------------

		This section provides a diagram illustrating the ADRON-RM apparent FOVs
		layout in the corresponding reference frame.

		According to [3] the ADRON-RM spatial resolution is a circular area with a
		radius of about 1.5m at distance of 0.8 meters.

		The ADRON-RM surface slit creates a circular field of view with half cone
		angle of 43.15 degrees. The following diagrams illustrate the above field of
		view in the instrument frame:

		Y X
		ins ins
		^ / ^ /
		\| / \| /
		\| / \| /
		\| / \| /
		X \| / o Y \| / o
		ins \|/ 43.15 ins \|/ 43.15
		x--------> o-------->
		\|\ Z \|\ Z
		\| \ ins \| \ ins
		\| \ \| \
		\| \ \| \
		\| \ \| \
		\| \ \| \
		Plane X = 0 Plane Y = 0


		Please note that the FOV reference and cross angles are defined with half
		angle values.


		Mounting Alignment
		-------------------------------------------------------------------------------

		Refer to the latest version of the RM Frames Definition Kernel
		(FK) [1] for the ADRON-RM reference frames definitions and
		mounting alignment information.


		Optical Parameters
		---------------------------------------------------------------------------

		TBD.


		FOV Definitions
		-------------------------------------------------------------------------------

		This section contains definitions for the ADRON-RM FOVs. These definitions
		are provided in the format required by the SPICE (CSPICE) function GETFOV
		(getfov_c).

		Please note that the FOV reference anlges are defined with halfangle values.
		The FoV definition corresponds to the NAIF Body Name: RM_ADRON-RM.


		\begindata

		INS-174300_NAME = 'RM_ADRON-RM'
		INS-174300_BORESIGHT = ( 0.000 0.0000 -1.000 )
		INS-174300_FOV_FRAME = 'RM_ADRON-RM'
		INS-174300_FOV_SHAPE = 'CIRCLE'
		INS-174300_FOV_CLASS_SPEC = 'ANGLES'
		INS-174300_FOV_REF_VECTOR = ( 1.000 0.000 0.0000 )
		INS-174300_FOV_REF_ANGLE = ( 43.15 )
		INS-174300_FOV_ANGLE_UNITS = 'DEGREES'

		\begintext


		End of IK file.
		No newline at end of file

kernels/ik/emrsp_rm_isem_v00.ti

0 → 100644

+182 −0

Original line number	Diff line number	Diff line
		KPL/IK

		ISEM Instrument kernel
		===============================================================================

		This instrument kernel (I-kernel) contains Rover Module Infrared
		Spectrometer for ExoMars (ISEM). optics, detector, and field-of-view
		parameters.


		Version and Date
		-------------------------------------------------------------------------------

		Version 0.0 -- February 6, 2019 -- Marc Costa Sitja, ESA/ESAC

		Preliminary Version.


		References
		-------------------------------------------------------------------------------

		1. RM Frames Definition Kernel (FK), latest version.

		2. ''Kernel Pool Required Reading''.

		3. ``Infrared Spectrometer for ExoMars: A Mast-Mounted Instrument for the
		Rover'', O. I. Korablev et al, ASTROBIOLOGY Volume 17, Number 6 and 7,
		2017, DOI: 10.1089/ast.2016.1543


		Contact Information
		-------------------------------------------------------------------------------

		If you have any questions regarding this file contact SPICE support at
		ESA:

		Marc Costa Sitja
		(+34) 91-8131-457
		mcosta@sciops.esa.int, esa_spice@sciops.esa.int

		or ROCC at Altec Space:

		Federico Salvioli
		+1 (818) 354-8136
		federico.salvioli@altecspace.it


		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
		spiceypy.furnsh( 'frame_kernel_name' ) -- PYTHON

		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 RM instrument ID code.
		The ISEM instrument IDs are defined in [1] as follows:

		Instrument name ID
		-------------------- -------
		RM_ISEM -174200


		The remainder of the keyword is an underscore character followed by
		the unique name of the data item. For example, the boresight of
		ISEM is specified by

		INS-174200_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
		-------------------------------------------------------------------------------

		TBD.


		Apparent FOV Layout
		---------------------------------------------------------------------------

		This section provides a diagram illustrating the ISEM detectors apparent
		FOVs layout in the corresponding reference frames.

		The NAVCAM surface slit creates a circular field of view with half cone
		angle of 0.65 degrees. The following diagrams illustrate the above field of
		view in the instrument frame:

		Y X
		ins ins
		^ / ^ /
		\| / \| /
		\| / \| /
		\| / \| /
		X \| / o Y \| / o
		ins \|/ 0.65 ins \|/ 0.65
		x--------> o-------->
		\|\ Z \|\ Z
		\| \ ins \| \ ins
		\| \ \| \
		\| \ \| \
		\| \ \| \
		\| \ \| \
		Plane X = 0 Plane Y = 0


		Please note that the FOV reference and cross angles are defined with half
		angle values.


		Mounting Alignment
		-------------------------------------------------------------------------------

		Refer to the latest version of the RM Frames Definition Kernel
		(FK) [1] for the ISEM reference frames definitions and
		mounting alignment information.


		Optical Parameters
		---------------------------------------------------------------------------

		TBD.


		FOV Definitions
		-------------------------------------------------------------------------------

		This section contains definitions for the ISEM FOV. These definitions
		are provided in the format required by the SPICE (CSPICE) function GETFOV
		(getfov_c).

		Please note that the FOV reference and cross angles are defined with half
		angle values. The FoV definition corresponds to the NAIF Body Names:
		RM_ISEM.


		\begindata

		INS-174200_NAME = 'RM_ISEM'
		INS-174200_BORESIGHT = ( 0.000 0.0000 1.000 )
		INS-174200_FOV_FRAME = 'RM_ISEM'
		INS-174200_FOV_SHAPE = 'CIRCLE'
		INS-174200_FOV_CLASS_SPEC = 'ANGLES'
		INS-174200_FOV_REF_VECTOR = ( 1.000 0.000 0.0000 )
		INS-174200_FOV_REF_ANGLE = ( 0.65 )
		INS-174200_FOV_ANGLE_UNITS = 'DEGREES'

		\begintext


		End of IK file.
		No newline at end of file

kernels/ik/emrsp_rm_loccam_v00.ti

0 → 100644

+199 −0

Original line number	Diff line number	Diff line
		KPL/IK

		LocCam Instrument kernel
		===============================================================================

		This instrument kernel (I-kernel) contains Rover Module (LOCCAM_L
		and LOCCAM_R) optics, detector, and field-of-view parameters.


		Version and Date
		-------------------------------------------------------------------------------

		Version 0.0 -- January 6, 2019 -- Marc Costa Sitja, ESA/ESAC

		Preliminary Version.


		References
		-------------------------------------------------------------------------------

		1. RM Frames Definition Kernel (FK), latest version

		2. ''Kernel Pool Required Reading''

		3. ``Detailed Design Document for the ExoMars Rover Vehicle Navigation
		and Localisation Cameras'', N. Cristello, Airbus Defence and Space,
		EXM-RM-DDD-NDG-30000, Issue 8, January 2017


		Contact Information
		-------------------------------------------------------------------------------

		If you have any questions regarding this file contact SPICE support at
		ESA:

		Marc Costa Sitja
		(+34) 91-8131-457
		mcosta@sciops.esa.int, esa_spice@sciops.esa.int

		or ROCC at Altec Space:

		Federico Salvioli
		+1 (818) 354-8136
		federico.salvioli@altecspace.it


		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
		spiceypy.furnsh( 'frame_kernel_name' ) -- PYTHON

		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 RM instrument ID code.
		The Star Tracker instrument IDs are defined in [1] as follows:

		Instrument name ID
		-------------------- -------
		RM_LOCCAM_L -174031
		RM_LOCCAM_R -174032


		The remainder of the keyword is an underscore character followed by
		the unique name of the data item. For example, the boresight of
		the NavCam 1 (LOCCAM_L) is specified by

		INS-174031_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
		-------------------------------------------------------------------------------

		TBD.


		Apparent FOV Layout
		---------------------------------------------------------------------------

		This section provides a diagram illustrating the LOCCAM_L and LOCCAM_R
		detectors apparent FOVs layout in the corresponding reference frames.

		The LOCCAM surface slit creates a rectangular field of view with half cone
		angle of 32.5 degrees. The following diagrams illustrate the above field of
		view in the instrument frame:

		Y X
		ins ins
		^ / ^ /
		\| / \| /
		\| / \| /
		\| / \| /
		X \| / o Y \| / o
		ins \|/ 32.5 ins \|/ 32.5
		x--------> o-------->
		\|\ Z \|\ Z
		\| \ ins \| \ ins
		\| \ \| \
		\| \ \| \
		\| \ \| \
		\| \ \| \
		Plane X = 0 Plane Y = 0


		Please note that the FOV reference and cross angles are defined with half
		angle values.


		Mounting Alignment
		-------------------------------------------------------------------------------

		Refer to the latest version of the RM Frames Definition Kernel
		(FK) [1] for the NavCam reference frames definitions and
		mounting alignment information.


		Optical Parameters
		---------------------------------------------------------------------------

		TBD.


		CCD Parameters
		---------------------------------------------------------------------------

		TBD.


		FOV Definitions
		-------------------------------------------------------------------------------

		This section contains definitions for the NavCam FOVs. These definitions
		are provided in the format required by the SPICE (CSPICE) function GETFOV
		(getfov_c).

		Please note that the FOV reference and cross angles are defined with half
		angle values. The FoV definition corresponds to the NAIF Body Name:
		RM_LOCCAM_L and RM_LOCCAM_R.


		\begindata

		INS-174031_NAME = 'RM_LOCCAM_L'
		INS-174031_BORESIGHT = ( 0.000 0.0000 1.000 )
		INS-174031_FOV_FRAME = 'RM_LOCCAM_L'
		INS-174031_FOV_SHAPE = 'RECTANGLE'
		INS-174031_FOV_CLASS_SPEC = 'ANGLES'
		INS-174031_FOV_REF_VECTOR = ( 1.000 0.000 0.0000 )
		INS-174031_FOV_REF_ANGLE = ( 32.5 )
		INS-174031_FOV_CROSS_ANGLE = ( 32.5 )
		INS-174031_FOV_ANGLE_UNITS = 'DEGREES'

		INS-174032_NAME = 'RM_LOCCAM_R'
		INS-174032_BORESIGHT = ( 0.000 0.0000 1.000 )
		INS-174032_FOV_FRAME = 'RM_LOCCAM_R'
		INS-174032_FOV_SHAPE = 'RECTANGLE'
		INS-174032_FOV_CLASS_SPEC = 'ANGLES'
		INS-174032_FOV_REF_VECTOR = ( 1.000 0.000 0.0000 )
		INS-174032_FOV_REF_ANGLE = ( 32.5 )
		INS-174032_FOV_CROSS_ANGLE = ( 32.5 )
		INS-174032_FOV_ANGLE_UNITS = 'DEGREES'

		\begintext


		End of IK file.
		No newline at end of file