A web based mission control framework.
Open MCT (Open Mission Control Technologies) is a next-generation mission control framework for visualization of data on desktop and mobile devices. It is developed at NASA's Ames Research Center, and is being used by NASA for data analysis of spacecraft missions, as well as planning and operation of experimental rover systems. As a generalizable and open source framework, Open MCT could be used as the basis for building applications for planning, operation, and analysis of any systems producing telemetry data.
Try Open MCT now with our live demo.
Building and running Open MCT in your local dev environment is very easy. Be sure you have Git and Node.js installed, then follow the directions below. Need additional information? Check out the Getting Started page on our website. (These instructions assume you are installing as a non-root user; developers have reported issues running these steps with root privileges.)
git clone https://github.com/nasa/openmct.git
Open MCT is now running, and can be accessed by pointing a web browser at http://localhost:8080/
This represents a major overhaul of Open MCT with significant changes under the hood. We aim to maintain backward compatibility but if you do find compatibility issues, please let us know by filing an issue in this repository. If you are having major issues with v1.0.0 please check-out the v0.14.0 tag until we can resolve them for you.
If you are migrating an application built with Open MCT as a dependency to v1.0.0 from an earlier version, please refer to our migration guide.
Documentation is available on the Open MCT website.
The clearest examples for developing Open MCT plugins are in the tutorials provided in our documentation.
We want Open MCT to be as easy to use, install, run, and develop for as possible, and your feedback will help us get there! Feedback can be provided via GitHub issues, or by emailing us at [email protected].
See our documentation for a guide on building Applications with Open MCT.
Open MCT can be extended via plugins that make calls to the Open MCT API. A plugin is a group of software components (including source code and resources such as images and HTML templates) that is intended to be added or removed as a single unit.
As well as providing an extension mechanism, most of the core Open MCT codebase is also written as plugins.
For information on writing plugins, please see our API documentation.
The test suite is configured to load any scripts ending with
Spec.jsfound in the
srchierarchy. Full configuration details are found in
karma.conf.js. By convention, unit test scripts should be located alongside the units that they test; for example,
src/foo/Bar.jswould be tested by
src/foo/BarSpec.js. (For legacy reasons, some existing tests may be located in separate
testfolders near the units they test, but the naming convention is otherwise the same.)
npm testis run, test results will be written as HTML to
dist/reports/tests/. Code coverage information is written to
Certain terms are used throughout Open MCT with consistent meanings or conventions. Any deviations from the below are issues and should be addressed (either by updating this glossary or changing code to reflect correct usage.) Other developer documentation, particularly in-line documentation, may presume an understanding of these terms.