Open MCT 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.
Please visit our Official Site and Getting Started Guide
Open MCT alternatives and similar libraries
Based on the "Misc" category.
Alternatively, view Open MCT alternatives based on common mentions on social networks and blogs.
picturefill8.0 0.0 L2 Open MCT VS picturefillA responsive image polyfill for <picture>, srcset, sizes, and more
list.js8.0 0.0 L3 Open MCT VS list.jsThe perfect library for adding search, sort, filters and flexibility to tables, lists and various HTML elements. Built to be invisible and work on existing HTML.
nlp_compromise7.8 9.5 L3 Open MCT VS nlp_compromisemodest natural-language processing
Autotrack6.4 0.0 L2 Open MCT VS AutotrackAutomatic and enhanced Google Analytics tracking for common user interactions on the web.
mixitup6.3 0.0 L3 Open MCT VS mixitupA high-performance, dependency-free library for animated filtering, sorting, insertion, removal and more
echo5.8 0.0 L3 Open MCT VS echoLazy-loading images with data-* attributes
jquery-match-height5.8 0.0 L5 Open MCT VS jquery-match-heighta responsive equal heights plugin
grid5.7 1.7 L5 Open MCT VS gridDrag and drop library for two-dimensional, resizable and responsive lists
platform.js5.4 0.0 L1 Open MCT VS platform.jsA platform detection library.
ouibounce4.9 0.0 L5 Open MCT VS ouibounceIncrease your landing page conversion rates.
Expounder2.3 5.3 Open MCT VS ExpounderA library for explaining things in HTML.
jquery.vibrate.js1.7 0.0 Open MCT VS jquery.vibrate.js:heavy_dollar_sign: Vibration API Wrappers
Selectable1.6 2.1 Open MCT VS SelectableTouch enabled selectable plugin inspired by the jQuery UI widget.
Ditox.js1.1 1.3 Open MCT VS Ditox.jsDependency injection for modular web applications
Dandy UI0.1 0.0 Open MCT VS Dandy UIMinimalistic UI (boxes, colored text, menu and some more) for Node.js
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Open MCT or a related project?
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.
Please visit our Official Site and Getting Started Guide
Once you've created something amazing with Open MCT, showcase your work in our GitHub Discussions Show and Tell section. We love seeing unique and wonderful implementations of Open MCT!
Building and Running Open MCT Locally
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.)
- Clone the source code
git clone https://github.com/nasa/openmct.git
- Install development dependencies. Note: Check the package.json engine for our tested and supported node versions.
- Run a local development server
Open MCT is now running, and can be accessed by pointing a web browser at http://localhost:8080/
Open MCT is built using
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, Starting a GitHub Discussion, or by emailing us at [email protected].
Developing Applications With Open MCT
For more on developing with Open MCT, see our documentation for a guide on [Developing Applications with Open MCT](./API.md#starting-an-open-mct-application).
This is a fast moving project and we do our best to test and support the widest possible range of browsers, operating systems, and nodejs APIs. We have a published list of support available in our package.json's
If you encounter an issue with a particular browser, OS, or nodejs API, please file a GitHub issue
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](./API.md#plugins).
Our automated test coverage comes in the form of unit, e2e, visual, performance, and security tests.
Unit Tests are written for Jasmine and run by Karma. To run:
The test suite is configured to load any scripts ending with
src hierarchy. 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.js would be
e2e, Visual, and Performance tests
The e2e, Visual, and Performance tests are written for playwright and run by playwright's new test runner @playwright/test.
To run the e2e tests which are part of every commit:
npm run test:e2e:stable
To run the visual test suite:
npm run test:e2e:visual
To run the performance tests:
npm run test:perf
The test suite is configured to all tests localed in
e2e/tests/ ending in
*.e2e.spec.js. For more about the e2e test suite, please see the [README](./e2e/README.md)
Each commit is analyzed for known security vulnerabilities using CodeQL and our overall security report is available on LGTM. The list of CWE coverage items is avaiable in the CodeQL docs. The CodeQL workflow is specified in the [CodeQL analysis file](./.github/workflows/codeql-analysis.yml) and the custom [CodeQL config](./.github/codeql/codeql-config.yml).
Test Reporting and Code Coverage
Each test suite generates a report in CircleCI. For a complete overview of testing functionality, please see our Circle CI Test Insights Dashboard
Our code coverage is generated during the runtime of our unit, e2e, and visual tests. The combination of those reports is published to codecov.io
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.
- plugin: A plugin is a removable, reusable grouping of software elements. The application is composed of plugins.
- composition: In the context of a domain object, this refers to the set of other domain objects that compose or are contained by that object. A domain object's composition is the set of domain objects that should appear immediately beneath it in a tree hierarchy. A domain object's composition is described in its model as an array of id's; its composition capability provides a means to retrieve the actual domain object instances associated with these identifiers asynchronously.
- description: When used as an object property, this refers to the human-readable description of a thing; usually a single sentence or short paragraph. (Most often used in the context of extensions, domain object models, or other similar application-specific objects.)
- domain object: A meaningful object to the user; a distinct thing in the work support by Open MCT. Anything that appears in the left-hand tree is a domain object.
- identifier: A tuple consisting of a namespace and a key, which together uniquely identifies a domain object.
- name: When used as an object property, this refers to the human-readable name for a thing. (Most often used in the context of extensions, domain object models, or other similar application-specific objects.)
- navigation: Refers to the current state of the application with respect to the user's expressed interest in a specific domain object; e.g. when a user clicks on a domain object in the tree, they are navigating to it, and it is thereafter considered the navigated object (until the user makes another such choice.)
- namespace: A name used to identify a persistence store. A running open MCT application could potentially use multiple persistence stores, with the
Open MCT v2.0.0
Support for our legacy bundle-based API, and the libraries that it was built on (like Angular 1.x), have now been removed entirely from this repository.
For now if you have an Open MCT application that makes use of the legacy API, a plugin is provided that bootstraps the legacy bundling mechanism and API. This plugin will not be maintained over the long term however, and the legacy support plugin will not be tested for compatibility with future versions of Open MCT. It is provided for convenience only.
How do I know if I am using legacy API?
You might still be using legacy API if your source code
- Contains files named bundle.js, or bundle.json,
- Makes calls to
- Makes calls to
What should I do if I am using legacy API?
Please refer to the modern Open MCT API. Post any questions to the Discussions section of the Open MCT GitHub repository.
*Note that all licence references and agreements mentioned in the Open MCT README section above are relevant to that project's source code only.