## CHANGE LOG ## 1.0.0.0 - Initial version 1.1.0.0, CDC - Upgraded to v1B00 of the IM. - Re-classified this dictionary as a Discipline Dictionary, instead of Mission Dictionary. - Renamed Surface_Mission_Parameters to Surface_Mission_Information, Command_Execution_Information to Command_Execution, and Telemetry_Information to Telemetry. 1.1.1.0, CDC - Upgraded to v1D00 of the IM. - Fixed bugs in download_priority attribute: removed min and max value constraints, made definition more generic. 1.2.0.0, Trent Hare - Added Observational_Intent class and attributes: campaign, goal, task, activity_notes, keyword - Added command_dispatch_sclk to msn_surface:Command_Execution. Cardinality 0:1 - Added several telemetry attibutes for MSL/M2020 - Added Commanded_Parameters class with download_priority attribute - Update command_source_id definition per GitHub PDS4-LDD-Issue-Repo/issues/37 - Added boot_counter, rtt_version attributes to Command_Execution - Added activity_id, target_id attributes to Observational_Intent - Update to PDS IM 1E00 - Update sequence_execution_count to have a min=0 - Update telemetry_source_start_time to ASCII_Date_Time_DOY_UTC and formation_rule - Added Commanded_Parameters to Surface_Mission_Information 1.2.1.0, Trent Hare - Added "Team-generated Image" enumeration value under transport_protocol 1.2.2.0 T.Hare - Added telemetry_alternate_name The Command_Execution class contains information about how the command that acquired this data was executed, such as sequence or activity. The Commanded_Parameters class contains attributes used to identify or describe the commands sent to a spacecraft to perform one or more actions resulting in the acquisition of the current data product. These are distinct from similar values in the root Surface_Mission_Information class which indicate the state of the data as acquired. Describes the intent and context of the observation. The Surface_Mission_Information class contains attributes specific to surface missions which apply across instrument types. The Telemetry class contains downlink-related attributes used primarily during mission operations. This section contains the simpleTypes that provide more constraints than those at the base data type level. The simpleTypes defined here build on the base data types. This is another component of the common dictionary and therefore falls within the common namespace. Identifier specifying the activity this observation is a part of. Provides additional notes regarding the activity. The application_id (often abbreviated APID) attribute identifies the process, or source, which created the data. This can include information such as an identification of the instrument which generated the telemetry stream, its operating mode at the time of data acquisition, and any onboard compression of the data. The application_name attribute provides the name associated with the source or process which created the data. The application_subtype_id attribute provides further distinction (i.e., greater specificity) among application_id types. Indicates if the product was to be automatically deleted onboard after it is transmitted. Counter indicating the number of times the spacecraft flight software has been booted. The intent is that this is a global counter that can uniquely identify the current FSW boot, so other counters that reset at boot time can be disambiguated. Identifies the long-term observational campaign of which this observation is a part. Specifies the spacecraft clock time at which the command execution was started. The command_sequence_number attribute provides a numeric identifier for a sequence of commands sent to a spacecraft or instrument. Specifies where the command that triggered acquisition of this data came from. This may be "GROUND" for ground commanding, or the name of a flight software module that initiated the request. Identifies the communication session used to acquire this data. The data_size specifies number of bytes in the compressed data stream, not including headers. The download_priority attribute specifies which data to downlink/transmit, based on order of importance. The ranking and meaning of specific values will vary depending on the mission, and should be defined in the mission software interface specification (SIS). The earth_received_start_date_time attribute provides the earliest time at which any component telemetry data for a particular product was received. The earth_received_stop_date_time attribute provides the latest time at which any component telemetry data for a particular product was received. The expected_packets attribute provides the total number of telemetry packets which constitute a complete data product, i.e., a data product without missing data. Specifies the planned transmission path (route) for the telemetry data. See also transmission_path and communication_session_id. Specifies the active flight software mode at the time of data product creation. Interpretation of specific modes is mission-dependent. The flight_software_version_id attribute identifies the version of the instrument flight software used to acquire the image. Identifies the goal of this observation. Identifies geological characteristics of a feature or target. The observation_id specifies a unique identifier for a scientific observation within a data set. The product_completion_status attribute indicates whether or not a product is complete or is in one of a number of incomplete states. Sample values might indicate that all portions of the product have been downlinked and received correctly, that all portions have not yet been received, or that the product contains transmission errors. The specific values are mission-dependent. The provider_id attribute identifies the organization or subsystem that supplied the telemetry data product to the producer of the raw (EDR) PDS data product. This is typically (but not always) the organization responsible for reassembling packetized data into a single product. These may vary by mission so the permissible values should be set by the mission dictionaries. The received_packets attribute provides the total number of telemetry packets actually used to construct this data product. cf. expected_packets. The request_id is used to group related datasets together by science or engineering application or theme, such as frames in a mosaic. Identifies the version of the Round-Trip Tracking (RTT) system used to create metadata in this observation The sequence_execution_count specifies how many times this sequence has executed since the last reset of the flight computer. The sequence_id identifies the command sequence used to acquire this product. The sequence_version_id identifies which of potentially several versions of a sequence_id were used to acquire this product. The surface_gravity attribute specifies the acceleration of gravity (magnitude, not direction). Identifier specifying the name or identifier of the primary target this observation is observing. This is distinct from the pds:Target class in that pds:Target typically refers to a large entity such as a planet or satellite, whereas this keyword is intended to capture much finer target information, for example a rock name or even a specific location on a rock. Identifies the specific task for this observation. The telemetry_alternate_name is similar to telemetry_source_name but specifies an alternate name that may be used to additionally identify the source of the telemetry data in the parent class. Specifies the checksum for the telemetry stream from which this product was derived. Specifies the name of the host venue that provided the telemetry source data used in the creation of this data set. The telemetry_source_name specifies the name source of the telemetry data described in the parent class. The telemetry_source_sclk_start attribute specifies the value of the spacecraft clock (in seconds) at the creation time of the source product from which this product was derived. Specifies the length in bytes of the telemetry stream from which this product was derived. The telemetry_source_start_time specifies the creation time of the source product from which this product was derived. It is the same as the telemetry_source_sclk_start converted to Spacecraft Event Time (SCET). Indicates the actual transmission path (route) for the telemetry data. See also expected_transmission_path and communication_session_id. The transport_protocol attribute specifies the protocol used in the creation of the telemetry data products by the subsystem which generates the telemetry stream. Specifies the type of data flowing in the telemetry virtual channel.