Model Process Control Language

Metadata Updated: July 17, 2020

The MPC (Model Process Control) language enables the capture, communication and preservation of a simulation instance, with sufficient detail that it can be analyzed, augmented, aggregated, replayed [HTML_REMOVED]and preserved without the need for the initial simulation tool or resources (infrastructure, team, tools). [HTML_REMOVED]MPC was initially focused on 4-D (visual across time) simulations, and this is where the majority of the work has occurred. [HTML_REMOVED]However additional domains can be supported. [HTML_REMOVED]In the 4-D case, MPC is focused on description of state and meta information associated with each of the items and elements in a simulation. [HTML_REMOVED]With these elements preserved, an appropriate tool can replay the simulation well past end of life for the associated simulator. [HTML_REMOVED]This is critical when system and mission lifecycles are measured in decades and generations. [HTML_REMOVED]An additional benefit is that the MPC representation of a simulation does not need to contain critical software codes, models or intellectual property; allowing it to be easily shared with partners (domestic or international). [HTML_REMOVED] MPC grew from the Constellation System Engineering and Integration (SE[HTML_REMOVED]I) Modeling and Simulation Teams (MaST). [HTML_REMOVED]It was created to capture simulation data in a manner more quantitative than recorded video and a more portable than an [HTML_REMOVED]in tool[HTML_REMOVED] recording (requiring use of the tool to view the data). [HTML_REMOVED]It allows simulation information to be preserved outside the simulation tools and re-used by other tools. [HTML_REMOVED]MPC data is also extensible. [HTML_REMOVED]In the most basic case, the simulator provides time and location information. [HTML_REMOVED]Average velocity can then be calculated from 2 time stamped, location entries; and acceleration is available from 2 velocity entries. [HTML_REMOVED]This new information can then be written back into the MPC file for use and re-use by others.MPC itself is extensible. [HTML_REMOVED]Constellation held annual Confabs to partner extensions. [HTML_REMOVED]MPC 1 consisted of a comma-delimited text file, with each line consisting of a single state definition for a single entity. [HTML_REMOVED]Version 2 added XML encoding with additional data elements and removed the requirement to update every element every time cycle. [HTML_REMOVED]MPC Version 3, the current version, added Parent Child Relationships, [HTML_REMOVED]a separate configuration file to accompany the dynamic data file and standardized some of the freeform metadata into structured information.[HTML_REMOVED] Recent additions include support for thruster and joint data types.

Access & Use Information

Public: This dataset is intended for public access and use. License: No license information was provided. If this work was prepared by an officer or employee of the United States government as part of that person's official duties it is considered a U.S. Government Work.

Downloads & Resources

Dates

Metadata Created Date August 1, 2018
Metadata Updated Date July 17, 2020

Metadata Source

Harvested from NASA Data.json

Additional Metadata

Resource Type Dataset
Metadata Created Date August 1, 2018
Metadata Updated Date July 17, 2020
Publisher Space Technology Mission Directorate
Unique Identifier TECHPORT_88197
Maintainer
TECHPORT SUPPORT
Maintainer Email
Public Access Level public
Bureau Code 026:00
Metadata Context https://project-open-data.cio.gov/v1.1/schema/catalog.jsonld
Metadata Catalog ID https://data.nasa.gov/data.json
Schema Version https://project-open-data.cio.gov/v1.1/schema
Catalog Describedby https://project-open-data.cio.gov/v1.1/schema/catalog.json
Harvest Object Id 353fc87b-4eb7-42dc-8378-1e33f44f6092
Harvest Source Id 39e4ad2a-47ca-4507-8258-852babd0fd99
Harvest Source Title NASA Data.json
Data First Published 2014-09-01
Homepage URL https://techport.nasa.gov/view/88197
Data Last Modified 2020-01-29
Program Code 026:027
Source Datajson Identifier True
Source Hash fcb11b85428077c5342881582409983f78aa0193
Source Schema Version 1.1

Didn't find what you're looking for? Suggest a dataset here.