Attitude Comprehensive Message (ACM)¶
- class ccsds_ndm.Acm(header, segment)¶
Attitude Comprehensive Message (ACM).
An ACM specifies the attitude state of a single object at multiple epochs, contained within a specified time range. The ACM aggregates and extends APM and AEM content in a single comprehensive hybrid message.
Capabilities include: - Optional rate data elements - Optional spacecraft physical properties - Optional covariance elements - Optional maneuver parameters - Optional estimator information
- static from_file(path, format=None)¶
- static from_str(data, format=None)¶
- header¶
Attitude Comprehensive Message (ACM).
An ACM specifies the attitude state of a single object at multiple epochs, contained within a specified time range. The ACM aggregates and extends APM and AEM content in a single comprehensive hybrid message.
Capabilities include: - Optional rate data elements - Optional spacecraft physical properties - Optional covariance elements - Optional maneuver parameters - Optional estimator information
- Type:
- segment¶
ACM Segment.
- Type:
- to_file(path, format, validate=True)¶
- to_str(format, validate=True)¶
- class ccsds_ndm.AcmSegment(metadata, data)¶
-
- metadata¶
ACM Metadata Section.
- Type:
- validate(header)¶
Validate the segment against CCSDS rules.
- class ccsds_ndm.AcmMetadata(object_name, epoch_tzero, time_system=None, international_designator=None, comment=None)¶
ACM Metadata Section.
- comment¶
Comments (allowed only at the beginning of the ACM Metadata). Each comment line shall begin with this keyword.
Examples: This is a comment.
- epoch_tzero¶
Epoch from which all ACM relative times are referenced. (For format specification, see 6.8.9.) The time scale for EPOCH_TZERO is the one specified by ‘TIME_SYSTEM’ keyword in the Metadata section.
Examples: 2016-11-10T00:00:00
- Type:
- international_designator¶
Free text field containing an international designator for the object as assigned by the UN Committee on Space Research (COSPAR) and the US National Space Science Data Center (NSSDC). Such designator values have the following COSPAR format: YYYY-NNNP{PP}, where: YYYY = Year of launch. NNN = Three-digit serial number of launch in year YYYY (with leading zeros). P{PP} = At least one capital letter for the identification of the part brought into space by the launch. In cases in which the object has no international designator, the value UNKNOWN may be used. NOTE – The international designator is typically specified by ‘OBJECT_ID’ in the APM and AEM.
Examples: 2000-052A, 1996-068A, 2000-053A, 1996-008A, UNKNOWN
- Type:
str | None
- object_name¶
Free-text field containing the name of the object. There is no CCSDS-based restriction on the value for this keyword, but it is recommended to use names from either the UN Office of Outer Space Affairs designator index (reference [2]), which include Object name and international designator), the spacecraft operator, or a State Actor or commercial Space Situational Awareness (SSA) provider maintaining the ‘CATALOG_NAME’ space catalog. If the object name is not known (uncorrelated object), ‘UNKNOWN’ may be used (or this keyword omitted).
Examples: SPOT, ENVISAT, IRIDIUM, INTELSAT
- Type:
- time_system¶
Time system used for metadata, attitude data, covariance data. The set of allowed values is described in annex B, subsection B2.
Examples: UTC, TAI
- Type:
- validate()¶
Validate the metadata section against CCSDS rules.
- class ccsds_ndm.AcmData(att=None, phys=None, cov=None, man=None, ad=None, user=None)¶
ACM Data Section.
- ad¶
A single attitude determination Data section.
- Type:
AcmAttitudeDetermination | None
- att¶
One or more optional attitude state time histories (each consisting of one or more attitude states).
- Type:
- cov¶
One or more optional covariance time histories (each consisting of one or more covariance matrix diagonals).
- Type:
- man¶
One or more optional maneuver specification section(s).
- Type:
- phys¶
A single space object physical characteristics section.
- Type:
AcmPhysicalDescription | None
- user¶
A single user-defined Data section.
- Type:
UserDefined | None
- validate(metadata)¶
Validate the data section against CCSDS rules.
- class ccsds_ndm.AcmAttitudeDetermination(ad_id=None, comment=None)¶
ACM Data: Attitude Determination Data Section.
- comment¶
Comments allowed only immediately after the AD_START keyword.
Examples: This is a comment.
- class ccsds_ndm.AcmAttitudeState(ref_frame_a, ref_frame_b, att_type, att_lines, comment=None)¶
ACM Data: Attitude State Time History Section.
- att_lines¶
Data lines that consist of attitude data followed by rate data. (For the data units, see above [ATT_TYPE and RATE_TYPE keywords]).
- att_type¶
Type of attitude data, selected per annex B, subsection B4. Attitude data must always be listed before rate data. The units that shall be used are given in annex B, subsection B4.
Examples: QUATERNION, EULER_ANGLES, DCM
- Type:
- comment¶
Comments allowed only immediately after the ATT_START keyword.
Examples: This is a comment.
- number_states¶
Number of data states included. States to be included are attitude states and optional rate states.
Examples: 3, 4, 7
- Type:
- ref_frame_a¶
Name of the reference frame that defines the starting point of the transformation. The set of allowed values is described in annex B, subsection B3.
Examples: J2000
- Type:
- class ccsds_ndm.AcmCovarianceMatrix(cov_basis, cov_ref_frame, cov_type, cov_lines, comment=None)¶
ACM Data: Covariance Time History Section.
- comment¶
Comments allowed only immediately after the COV_START keyword.
Examples: THIS is a comment.
- cov_basis¶
Basis of this covariance time history data.
Examples: PREDICTED, DETERMINED_GND, DETERMINED_OBC, SIMULATED
- Type:
- cov_lines¶
Covariance data lines (diagonal terms only). (For the data units, see annex B, subsection B6.)
- cov_ref_frame¶
Reference frame of the covariance time history. The full set of values is enumerated in annex B, subsection B3.
Examples: SC_BODY_1
- Type:
- class ccsds_ndm.AcmManeuverParameters(man_id=None, comment=None)¶
ACM Data: Maneuver Specification Section.
- comment¶
Comments allowed only immediately after the MAN_START keyword.
Examples: This is a comment.
- class ccsds_ndm.AcmPhysicalDescription(comment=None)¶
ACM Data: Space Object Physical Characteristics Section.
- comment¶
Comments allowed only immediately after the PHYS_START keyword.
Examples: This is a comment.
State Blocks¶
- class ccsds_ndm.AngVelState(ref_frame_a, ref_frame_b, angvel_frame, angvel_x, angvel_y, angvel_z, comment)¶
Angular velocity vector.
All mandatory elements are to be provided if the block is present. (See annex F for conventions and further detail.)
- angvel_frame¶
Reference frame in which the components of the angular velocity vector are given. The set of allowed values is described in annex B, subsection B3.
- Type:
- comment¶
One or more comment line(s). Each comment line shall begin with this keyword.
- ref_frame_a¶
Name of the reference frame that defines the starting point of the transformation. The set of allowed values is described in annex B, subsection B3.
- Type: