MARVIN: An Open Machine Learning Corpus and Environment for Automated Machine Learning Primitive Annotation and Execution

MARVIN: An Open Machine Learning Corpus and Environment for Automated Machine Learning Primitive Annotation and Execution

Chris A. Mattmann
Jet Propulsion Laboratory
California Institute of Technology
Pasadena, CA 91109 USA
chris.a.mattmann@jpl.nasa.gov
   Sujen Shan
Jet Propulsion Laboratory
California Institute of Technology
Pasadena, CA 91109 USA
sujen.shah@jpl.nasa.gov
   Brian Wilson
Jet Propulsion Laboratory
California Institute of Technology
Pasadena, CA 91109 USA
brian.wilson@jpl.nasa.gov
Abstract

In this demo paper, we introduce the DARPA DM program for automatic machine learning (ML) and JPL’s MARVIN tool that provides an environment to locate, annotate, and execute machine learning primitives for use in ML pipelines. MARVIN is a web-based application and associated back-end interface written in Python that enables composition of ML pipelines from hundreds of primitives from the world of Scikit-Learn, Keras, DL4J, and other widely used libraries. MARVIN allows for the creation of Docker containers that run on Kubernetes clusters within DARPA to provide an execution environment for automated machine learning. MARVIN currently contains over 400 datasets and challenge problems from a wide array of ML domains including routine classification and regression to advanced video/image classification and remote sensing.

1 Introduction

The world of machine learning (ML) is exploding and new ways of applying ML for mundane, repetitive, and complex tasks is increasing: from using ML to reply to e-mail messages automatically [kannan2016smart] to self-driving cars and using ML for sustainable mobility [burns2013sustainable] . Today, machine learning requires human capital to perform a variety of tasks including 1) composition and aggregation of machine learning “primitives” [mitchell2006discipline], e.g., kernels of code that clean, decide, classify/label, cluster/organize, and rank the input dataset to produce an output; 2) selection of ML models that have already been generated such as from OpenML [vanschoren2014openml], ModelZoo [jia2015caffe], UC Irvine ML repository [frank2010uci], Kaggle [wiki:Kaggle], etc. or the generation of new models, datasets, and problems; and 3) development of metrics to evaluate how well machine learning is working on a particular problem.

Figure 1: DM Government Team responsibilities.

In 2016, the United States Defense Advanced Research Projects Agency (DARPA) incepted the Data Driven Discovery of Models (DM) program to automate the three core tasks of machine learning identified in the preceding paragraph. Twenty four performers on DM are working together in three technical areas corresponding to each of the core ML tasks (TA1: ML primitives development; TA2: Automated Machine Learning using Datasets, Problems, and Challenges; and TA3: User/SME Metrics for evaluating automated machine learning). The Jet Propulsion Laboratory, California Institute of Technology (NASA-JPL) is part of the DM government team, which consists of NASA-JPL, MIT Lincoln Laboratories, and the US National Institutes of Standards and Technology (NIST). The government team responsibilities, shown in Fig. 1, involve the creation of a baseline open source model corpus (TA1); the curation of 10s of thousands of ML datasets, problems, and baseline solutions (TA2) for proxy government and even direct governmental challenges across defense, civil agencies, and space; and a set of automated evaluation metrics to assess the performance of the automatic machine learning systems.

Our team at NASA-JPL has over the past two years designed and implemented a system that we call MARVIN (a reference to the character from the Looney Tunes cartoon series [beck2003looney]) whose main goals are to provide an environment for creating a performer baseline for machine learning primitive annotation, schema, and evaluation. MARVIN is a web-based tool that is built on ElasticSearch [gormley2015elasticsearch] and FacetView [facetview2018] and Kibana [gupta2015kibana]. ElasticSearch is used to capture JSON instances of metadata about machine learning primitives representing the world of ML - from SKLearn [pedregosa2011scikit], to DL4J [bahrampour2016comparative], to Keras [raschka2015python] and so on. Primitive “annotations” capture their inputs, outputs, and characteristics for composing the primitives into an ML pipeline for use by the TA2 performers. MARVIN allows for search and exploration of these primitive instances, and we have written an application programming interface to leverage MARVIN for invocation of the associated primitives (e.g., pick your LogisticRegression that supports particular hyperparameters, programming languages, etc.). In addition, Marvin also provides the ability to search ML datasets, and challenge problems for over 400 challenges at present (and soon 10s of thousands) ranging from introductory machine learning activities and data types e.g., predict Hall of Fame decisions based on baseball player statistics all the way to complex multi-source classification and decision making e.g., identify objects in videos and images with high accuracy. All primitives, datasets, and challenge problems are searchable and indexed in ElasticSearch and browseable using FacetView and Kibana.

MARVIN also provides the ability to generate a Dockerfile and allow for execution of ML primitives and pipelines based on the primitive type and associated preferred data and problem domain. We have classified domains into areas of video, text/NLP, classification, labeling, regression, etc. MARVIN also provides base Docker images containing the curated library of ML primitives and a base execution environment that DM performers can extend and use to run generated pipelines.

2 Data model

The Primitive “annotations” follow a [primitiveSchema] that allow TA2 systems to infer metadata about the primitive, like its “algorithm type”, “primitive family”, “hyperparameters”, etc. (JPL developed an initial schema but now it is jointly developed by the entire DM community – Performers and the government teams.)

Algorithm Types: The algorithm type field intends to capture the underlying implementation of the primitive. The field currently is an enumeration of values from a controlled vocabulary including, but not limited to, algorithms such as ADABOOST [adaboost1997], BAYESIAN LINEAR REGRESSION [minka1998bayesian], DECISION TREE [decisiontree1986], etc.

Figure 2: A screenshot of the MARVIN interface showing primitives (on the right) and their metadata, along with search criteria on the left, e.g., NO_JAGGED_VALUES, etc.

Primitive Family: This field intends to capture the high level purpose of the primitive. It is an enumeration of controlled values e.g., “CLASSIFICATION”, “FEATURE_SELECTION”, “DATA_TRANSFORMATION”, “TIMESERIES_FORECASTING”, etc.

Hyperparameter: The hyperparameter field captures all the parameters that a TA2 system could pass to a TA1 primitive to control its behavior. These could include tunable hyperparameters which affect the model performance, resource use hyperparameters that control the resource usage of that primitive, and metafeature parameters that control which meta-features are computed by the primitive.

Apart from the above, there are more key fields that help a TA2 system to determine whether to use the given primitive in a pipeline for solving a problem or not. For example, the preconditions field indicates what preconditions must evaluate to true before using this primitive. For instance the “NO_MISSING_VALUES” precondition would inform a TA2 system that this primitive cannot handle missing values in the data. Similarly there could be other preconditions like “NO_CONTINUOUS_VALUES”, “NO_JAGGED_VALUES”, etc., as show in Fig. 2.

The effects field in the schema informs a TA2 about the set of post conditions obtained by data processed by this primitive. Some of the effects include - “NO_MISSING_VALUES”, this indicates that the primitive removes missing values, “NO_CATEGORICAL_VALUES”, indicates that the primitive removes categorical columns, etc.

3 Execution environment

Figure 3: Our MARVIN execution environment architecture running on top of Kubernetes (K8s).

MARVIN leverages Docker containers and Kubernetes clusters (K8s) [bernstein2014containers] to provide an environment for DM performer testing (called the “Play Space” in Fig. 1 upper left corner). Depending on the machine learning problem type e.g., Image/Video, NLP/Text, Classification, performers can use MARVIN to create a Dockerfile containing a set of Primitives for a particular problem set and then create a running Docker image on our DM Kubernetes cluster. As shown in Fig. 3 starting from the left side of the figure, TA1 performers can publish a Docker image of their TA1 primitive if it requires special services such as e.g., graph databases, or particular Python libraries which can then be consumable and included in other performer containers. In addition, we offer base Master containers for our TA2 systems (top-middle of Fig. 3) to leverage e.g., NLP, Image/Video base, or a combination of all required libraries in the program. Then, using MARVIN’s API, TA2 performers can dynamically select, and execute their primitives. Data (shown in the middle-left of Fig. 3) is made available via shared K8s volumes to all the containers on the cluster.

4 Conclusion

We presented MARVIN, an automated system for discovering machine learning primitives, and executing them in an automated fashion. MARVIN is a core tool in the DARPA D3M program. At present MARVIN provides a web-based interface to browse over hundreds of ML primitives and 400 ML datasets and challenge problems, and over the next two years the tool will be expanded to support thousands of ML problems and primitives for the performers in the program.

Acknowledgement

This effort was supported in part by JPL, managed by the California Institute of Technology on behalf of NASA, and additionally in part by the DARPA Memex/XDATA/D3M/ASED programs and NSF award numbers ICER-1639753, PLR-1348450 and PLR-144562 funded a portion of the work. The authors would like to thank Maziyar Boustani, Kyle Hundman, Asitang Mishra, Tom Barber and Giuseppe Totaro at JPL who materially contributed to the design and construction of MARVIN. We also thank our collaborators at MIT Lincoln Labs and NIST. The library of primitives is now being further populated by the entire D3M community. We also credit Mr. Wade Shen for his support of our work.

References

Comments 0
Request Comment
You are adding the first comment!
How to quickly get a good reply:
  • Give credit where it’s due by listing out the positive aspects of a paper before getting into which changes should be made.
  • Be specific in your critique, and provide supporting evidence with appropriate references to substantiate general statements.
  • Your comment should inspire ideas to flow and help the author improves the paper.

The better we are at sharing our knowledge with each other, the faster we move forward.
""
The feedback must be of minimum 40 characters and the title a minimum of 5 characters
   
Add comment
Cancel
Loading ...
254347
This is a comment super asjknd jkasnjk adsnkj
Upvote
Downvote
""
The feedback must be of minumum 40 characters
The feedback must be of minumum 40 characters
Submit
Cancel

You are asking your first question!
How to quickly get a good answer:
  • Keep your question short and to the point
  • Check for grammar or spelling errors.
  • Phrase it like a question
Test
Test description