US20220092419A1

US20220092419A1 - Systems and methods to use neural networks for model transformations

Info

Publication number: US20220092419A1
Application number: US17/464,796
Authority: US
Inventors: Vincent Pham; Anh Truong; Fardin Abdi Taghi Abad; Jeremy Goodsitt; Austin Walters; Mark Watson; Reza Farivar; Kenneth Taylor
Original assignee: Capital One Services LLC
Current assignee: Capital One Services LLC
Priority date: 2018-07-06
Filing date: 2021-09-02
Publication date: 2022-03-24
Also published as: EP3591587A1; US11182223B2; US11113124B2; US10521719B1; US10860460B2; US20230073695A1; US10671884B2; US20220107851A1; US11822975B2; US20230153177A1; US11704169B2; US11900178B2; US20200012657A1; US20210081261A1; US20230195541A1; US20200012937A1; US20240054029A1; US20200218638A1; US20200012902A1; US20220075670A1

Abstract

Systems and methods for transforming legacy models and transforming a model into a neural network model are disclosed. In an embodiment, a method may include receiving input data comprising an input model, an input dataset, and an input command. The method may include applying the input model to the input dataset to generate model output and storing model output and at least one of input model features or a map of the input model. The method may include generating a candidate neural network models with parameters. The method may include tuning the candidate neural network models to the input model. The method may include receiving model output from the candidate neural network models and selecting a neural network model from the candidate neural network models based on the candidate model output and the model selection criteria. In some aspects, the method may include returning the selected neural network model.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/694,968, filed Jul. 6, 2018, and incorporated herein by reference in its entirety.
This application also relates to U.S. patent application Ser. No. 16/151,385 filed on Oct. 4, 2018, and titled Data Model Generation Using Generative Adversarial Networks, the disclosure of which is also incorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments concern a platform for management of artificial intelligence systems. In particular, the disclosed embodiments concern using the disclosed platform to create neural network models of data based on previously existing models, including legacy models. A legacy model is a model that runs in a programming environment that has been or is being replaced by a different programming environment. These data models can be used, for example, to generate synthetic data for testing or training artificial intelligence systems. The disclosed embodiments also concern improvements transforming any model, including a legacy model, into a neural network model.

BACKGROUND

Neural network models provide advantages over conventional modeling approaches. Neural network models model data efficiently, adaptably, and accurately than conventional models. Neural network models may be recurrent neural network models, deep learning models, long-short-term memory (LSTM) models, convolutional neural network (CNN) models, generative adversarial networks (GANs), and the like. Neural network models meet different modeling needs than conventional models and can analyze a wide variety of data as data analysis objectives evolve.
A neural network model may be designed according to an underlying physical or relational understanding of the data structure. Further, to assist user understanding of a model, it may be desirable to base the neural network model on an original model, e.g., a conventional model, that captures physical or statistical relationships between data elements. Further, a neural network model designed based on the features of the original model may behave more like the original model when encountering new datasets, and thereby yield similar insights that are easier for the user to understand. Therefore, it is often desirable to transform original models into neural network models instead of, for instance, replacing original models with completely new neural network models. For example, a neural network model may train more efficiently and more accurately predict an outcome if certain nodes are trained to replicate a linear regression model that had already identified certain statistically significant relationships between input variables. Further, a previously trained predictive neural network model may be an efficient seed model for an updated, more accurate predictive neural network model because the previously trained model may have learned to make predictions with some accuracy.
Conventional approaches to transform a model into a neural network model involve time consuming efforts to oversee the development of the neural network model. Many organizations lack the resources or capacity to engage in conventional approaches to transforming a model into a neural network model.
In addition, there is a need to transform models of a given type (e.g., a random forest model, a gradient boosting machine, a regression model, a linear regression model, a symbolic model, a neural network model, or other model), into a new model of the same type. This may happen, for instance, with a legacy model. For example, an organization may be in the process of phasing out SAS and implementing PYTHON across a platform, so the organization may need to transform legacy SAS models to PYTHON models.
Conventionally, to transform a legacy model into a model running in a new environment, developers manually performed many steps of the transformation, which is a time consuming, costly, and error-prone process. For example, to transform a random forest model built with SCIKIT into a gradient boosting model built for XGBOOST, the developer must configure the system, install dependencies, import libraries, modify code to accept new output types of XGBOOST, and remove outdated dependencies. Any of these steps could lead to errors and extensive time debugging the new model code . Many organizations lack the resources or capacity to engage in conventional approaches to transforming a legacy model.
Therefore, in light of the shortcomings and deficiencies of conventional methods of modeling and of transforming models, systems and methods that reduce development time, reduce cost, improve modeling accuracy, and increase flexibility are desirable. There is a need for systems and methods that transform a model of any type, e.g., a legacy model, into a new neural network model. There is also a need for systems and methods that transform a legacy model running in one type of environment into a model (e.g., a conventional model or a neural network model) that can run in a different environment. Further, for organizations or users that lack the resources or capacity to transform models independently, there is a need for model transformation to be provided as a service.

SUMMARY

The disclosed embodiments provide unconventional systems and methods for transforming models that are more efficient, less costly, more flexible, and more accurate than conventional approaches. The disclosed embodiments provide unconventional systems and methods to transform any input model into a neural network model. The transformed neural network model is designed based on the features of the input model and is designed to overfit the input model. By overfitting the input model, the transformed neural network model accurately reproduces the modeling results of the input model on training datasets and is likely to behave like the input model when analyzing other, non-training datasets.
Further, the disclosed embodiments provide systems and methods to transform legacy models into new models of the same type using machine learning. By using neural network models to create a new model that is the same type as the legacy model but will run in a different environment than the legacy model, the unconventional systems and methods of disclosed embodiments save time, reduce costs, and reduce errors.
The disclosed embodiments include a system for transforming a model into a neural network model. The system may include one or more memory units for storing instructions, and one or more processors configured to execute the instructions to perform operations. The operations may include receiving input data comprising an input model, an input dataset, and an input command specifying model selection criteria. The operations may include applying the input model to the input dataset to generate model output. The operations may include storing model output and at least one of input model features or a map of the input model and generating a plurality of candidate neural network models. The parameters of the candidate neural network models may be based on the input model features. The operations may include tuning the plurality of candidate neural network models to the input model. The operations may include receiving model output from the plurality of candidate neural network models and selecting a neural network model from the plurality of the candidate neural network models based on the candidate model output and the model selection criteria. In some aspects, the operations may include returning the selected neural network model.
Consistent with disclosed embodiments, a method for transforming a model into a neural network model is disclosed. The method may include receiving input data comprising an input model, an input dataset, and an input command specifying model selection criteria. The method may include applying the input model to the input dataset to generate model output. The method may include storing model output and at least one of input model features or a map of the input model and generating a plurality of candidate neural network models. The parameters of the candidate neural network models may be based on the input model features. The method may include tuning the plurality of candidate neural network models to the input model. The method may include receiving model output from the plurality of candidate neural network models and selecting a neural network model from the plurality of the candidate neural network models based on the candidate model output and the model selection criteria. In some aspects, the method may include returning the selected neural network model.
Consistent with other disclosed embodiments, non-transitory computer readable storage media may store program instructions, which are executed by at least one processor device and perform any of the methods described herein.
The foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are not necessarily to scale or exhaustive. Instead, emphasis is generally placed upon illustrating the principles of the embodiments described herein. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments consistent with the disclosure and, together with the description, serve to explain the principles of the disclosure. In the drawings:

FIG. 1 depicts an exemplary cloud-computing environment for generating data models, consistent with disclosed embodiments.

FIG. 2 depicts an exemplary process for generating data models, consistent with disclosed embodiments.

FIG. 3 depicts an exemplary process for generating synthetic data using existing data models, consistent with disclosed embodiments.

FIG. 4 depicts an exemplary implementation of the cloud-computing environment of FIG. 1, consistent with disclosed embodiments.

FIG. 5A depicts an exemplary process for generating synthetic data using class-specific models, consistent with disclosed embodiments.

FIG. 5B depicts an exemplary process for generating synthetic data using class and subclass-specific models, consistent with disclosed embodiments.

FIG. 6 depicts an exemplary process for training a classifier for generation of synthetic data, consistent with disclosed embodiments.

FIG. 7 depicts an exemplary process for training a classifier for generation of synthetic data, consistent with disclosed embodiments.

FIG. 8 depicts an exemplary process for training a generative adversarial using a normalized reference dataset, consistent with disclosed embodiments.

FIG. 9 depicts an exemplary process for training a generative adversarial network using a loss function configured to ensure a predetermined degree of similarity, consistent with disclosed embodiments.

FIG. 10 depicts an exemplary process for supplementing or transform datasets using code-space operations, consistent with disclosed embodiments.

FIGS. 11A and 11B depict an exemplary illustration of points in code-space, consistent with disclosed embodiments.

FIG. 12A depicts an exemplary illustration of supplementing datasets using code-space operations, consistent with disclosed embodiments.

FIG. 12B depicts an exemplary illustration of transforming datasets using code-space operations, consistent with disclosed embodiments.

FIG. 13 depicts an exemplary cloud computing system for generating a synthetic data stream that tracks a reference data stream, consistent with disclosed embodiments.

FIG. 14 depicts a process for generating synthetic JSON log data using the cloud computing system of FIG. 13, consistent with disclosed embodiments.

FIG. 15 depicts a system for secure generation and insecure use of models of sensitive data, consistent with disclosed embodiments.

FIG. 16 depicts a process for transforming any model into a neural network model, consistent with disclosed embodiments.

FIG. 17 depicts a process for transforming a legacy model, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, discussed with regards to the accompanying drawings. In some instances, the same reference numbers will be used throughout the drawings and the following description to refer to the same or like parts. Unless otherwise defined, technical and/or scientific terms have the meaning commonly understood by one of ordinary skill in the art. The disclosed embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosed embodiments. It is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the disclosed embodiments. Thus, the materials, methods, and examples are illustrative only and are not intended to be necessarily limiting.
The disclosed embodiments can be used to create models of datasets, which may include sensitive datasets (e.g., customer financial information, patient healthcare information, and the like). Using these models, the disclosed embodiments can produce fully synthetic datasets with similar structure and statistics as the original sensitive or non-sensitive datasets. The disclosed embodiments also provide tools for desensitizing datasets and tokenizing sensitive values. In some embodiments, the disclosed systems can include a secure environment for training a model of sensitive data, and a non-secure environment for generating synthetic data with similar structure and statistics as the original sensitive data. In various embodiments, the disclosed systems can be used to tokenize the sensitive portions of a dataset (e.g., mailing addresses, social security numbers, email addresses, account numbers, demographic information, and the like). In some embodiments, the disclosed systems can be used to replace parts of sensitive portions of the dataset (e.g., preserve the first or last 3 digits of an account number, social security number, or the like; change a name to a first and last initial). In some aspects, the dataset can include one or more JSON (JavaScript Object Notation) or delimited files (e.g., comma-separated value, or CSV, files). In various embodiments, the disclosed systems can automatically detect sensitive portions of structured and unstructured datasets and automatically replace them with similar but synthetic values.
FIG. 1 depicts a cloud-computing environment 100 for generating data models. Environment 100 can be configured to support generation and storage of synthetic data, generation and storage of data models, optimized choice of parameters for machine learning, and imposition of rules on synthetic data and data models. Environment 100 can be configured to expose an interface for communication with other systems. Environment 100 can include computing resources 101, dataset generator 103, database 105, model optimizer 107, model storage 109, model curator 111, and interface 113. These components of environment 100 can be configured to communicate with each other, or with external components of environment 100, using network 115. The particular arrangement of components depicted in FIG. 1 is not intended to be limiting. System 100 can include additional components, or fewer components. Multiple components of system 100 can be implemented using the same physical computing device or different physical computing devices.
Computing resources 101 can include one or more computing devices configurable to train data models. The computing devices can be special-purpose computing devices, such as graphical processing units (GPUs) or application-specific integrated circuits. The cloud computing instances can be general-purpose computing devices. The computing devices can be configured to host an environment for training data models. For example, the computing devices can host virtual machines, pods, or containers. The computing devices can be configured to run applications for generating data models. For example, the computing devices can be configured to run SAGEMAKER, or similar machine learning training applications. Computing resources 101 can be configured to receive models for training from model optimizer 107, model storage 109, or another component of system 100. Computing resources 101 can be configured provide training results, including trained models and model information, such as the type and/or purpose of the model and any measures of classification error.
Dataset generator 103 can include one or more computing devices configured to generate data. Dataset generator 103 can be configured to provide data to computing resources 101, database 105, to another component of system 100 (e.g., interface 113), or another system (e.g., an APACHE KAFKA cluster or other publication service). Dataset generator 103 can be configured to receive data from database 105 or another component of system 100. Dataset generator 103 can be configured to receive data models from model storage 109 or another component of system 100. Dataset generator 103 can be configured to generate synthetic data. For example, dataset generator 103 can be configured to generate synthetic data by identifying and replacing sensitive information in data received from database 103 or interface 113. As an additional example, dataset generator 103 can be configured to generate synthetic data using a data model without reliance on input data. For example, the data model can be configured to generate data matching statistical and content characteristics of a training dataset. In some aspects, the data model can be configured to map from a random or pseudorandom vector to elements in the training data space.
Database 105 can include one or more databases configured to store data for use by system 100. The databases can include cloud-based databases (e.g., AMAZON WEB SERVICES S3 buckets) or on-premises databases.
Model optimizer 107 can include one or more computing systems configured to manage training of data models for system 100. Model optimizer 107 can be configured to generate models for export to computing resources 101. Model optimizer 107 can be configured to generate models based on instructions received from a user or another system. These instructions can be received through interface 113. For example, model optimizer 107 can be configured to receive a graphical depiction of a machine learning model and parse that graphical depiction into instructions for creating and training a corresponding neural network on computing resources 101. Model optimizer 107 can be configured to select model training parameters. This selection can be based on model performance feedback received from computing resources 101. Model optimizer 107 can be configured to provide trained models and descriptive information concerning the trained models to model storage 109.
Model storage 109 can include one or more databases configured to store data models and descriptive information for the data models. Model storage 109 can be configured to provide information regarding available data models to a user or another system. This information can be provided using interface 113. The databases can include cloud-based databases (e.g., AMAZON WEB SERVICES S3 buckets) or on-premises databases. The information can include model information, such as the type and/or purpose of the model and any measures of classification error.
Model curator 111 can be configured to impose governance criteria on the use of data models. For example, model curator 111 can be configured to delete or control access to models that fail to meet accuracy criteria. As a further example, model curator 111 can be configured to limit the use of a model to a particular purpose, or by a particular entity or individual. In some aspects, model curator 11 can be configured to ensure that data model satisfies governance criteria before system 100 can process data using the data model.
Interface 113 can be configured to manage interactions between system 100 and other systems using network 115. In some aspects, interface 113 can be configured to publish data received from other components of system 100 (e.g., dataset generator 103, computing resources 101, database 105, or the like). This data can be published in a publication and subscription framework (e.g., using APACHE KAFKA), through a network socket, in response to queries from other systems, or using other known methods. The data can be synthetic data, as described herein. As an additional example, interface 113 can be configured to provide information received from model storage 109 regarding available datasets. In various aspects, interface 113 can be configured to provide data or instructions received from other systems to components of system 100. For example, interface 113 can be configured to receive instructions for generating data models (e.g., type of data model, data model parameters, training data indicators, training parameters, or the like) from another system and provide this information to model optimizer 107. As an additional example, interface 113 can be configured to receive data including sensitive portions from another system (e.g. in a file, a message in a publication and subscription framework, a network socket, or the like) and provide that data to dataset generator 103 or database 105.
Network 115 can include any combination of electronics communications networks enabling communication between components of system 100. For example, network 115 may include the Internet and/or any type of wide area network, an intranet, a metropolitan area network, a local area network (LAN), a wireless network, a cellular communications network, a Bluetooth network, a radio network, a device bus, or any other type of electronics communications network known to one of skill in the art.
FIG. 2 depicts a process 200 for generating data models. Process 200 can be used to generate a data model for a machine learning application, consistent with disclosed embodiments. The data model can be generated using synthetic data in some aspects. This synthetic data can be generated using a synthetic dataset model, which can in turn be generated using actual data. The synthetic data may be similar to the actual data in terms of values, value distributions (e.g., univariate and multivariate statistics of the synthetic data may be similar to that of the actual data), structure and ordering, or the like. In this manner, the data model for the machine learning application can be generated without directly using the actual data. As the actual data may include sensitive information, and generating the data model may require distribution and/or review of training data, the use of the synthetic data can protect the privacy and security of the entities and/or individuals whose activities are recorded by the actual data.
Process 200 can then proceed to step 201. In step 201, interface 113 can provide a data model generation request to model optimizer 107. The data model generation request can include data and/or instructions describing the type of data model to be generated. For example, the data model generation request can specify a general type of data model (e.g., neural network, recurrent neural network, generative adversarial network, kernel density estimator, random data generator, or the like) and parameters specific to the particular type of model (e.g., the number of features and number of layers in a generative adversarial network or recurrent neural network). In some embodiments, a recurrent neural network can include long short term memory modules (LSTM units), or the like.
Process 200 can then proceed to step 203. In step 203, one or more components of system 100 can interoperate to generate a data model. For example, as described in greater detail with regard to FIG. 3, a data model can be trained using computing resources 101 using data provided by dataset generator 103. In some aspects, this data can be generated using dataset generator 103 from data stored in database 105. In various aspects, the data used to train dataset generator 103 can be actual or synthetic data retrieved from database 105. This training can be supervised by model optimizer 107, which can be configured to select model parameters (e.g., number of layers for a neural network, kernel function for a kernel density estimator, or the like), update training parameters, and evaluate model characteristics (e.g., the similarity of the synthetic data generated by the model to the actual data). In some embodiments, model optimizer 107 can be configured to provision computing resources 101 with an initialized data model for training. The initialized data model can be, or can be based upon, a model retrieved from model storage 109.
Process 200 can then proceed to step 205. In step 205, model optimizer 107 can evaluate the performance of the trained synthetic data model. When the performance of the trained synthetic data model satisfies performance criteria, model optimizer 107 can be configured to store the trained synthetic data model in model storage 109. For example, model optimizer 107 can be configured to determine one or more values for similarity and/or predictive accuracy metrics, as described herein. In some embodiments, based on values for similarity metrics, model optimizer 107 can be configured to assign a category to the synthetic data model.
According to a first category, the synthetic data model generates data maintaining a moderate level of correlation or similarity with the original data, matches well with the original schema, and does not generate too many row or value duplicates. According to a second category, the synthetic data model may generate data maintaining a high level of correlation or similarity of the original level, and therefore could potentially cause the original data to be discernable from the original data (e.g., a data leak). A synthetic data model generating data failing to match the schema with the original data or providing many duplicated rows and values may also be placed in this category. According to a third category, the synthetic data model may likely generate data maintaining a high level of correlation or similarity with the original data, likely allowing a data leak. A synthetic data model generating data badly failing to match the schema with the original data or providing far too many duplicated rows and values may also be placed in this category.
In some embodiments, system 100 can be configured to provide instructions for improving the quality of the synthetic data model. If a user requires synthetic data reflecting less correlation or similarity with the original data, the use can change the models' parameters to make them perform worse (e.g., by decreasing number of layers in GAN models, or reducing the number of training iterations). If the users want the synthetic data to have better quality, they can change the models' parameters to make them perform better (e.g., by increasing number of layers in GAN models, or increasing the number of training iterations).
Process 200 can then proceed to step 207, in step 207, model curator 111 can evaluate the trained synthetic data model for compliance with governance criteria.
FIG. 3 depicts a process 300 for generating a data model using an existing synthetic data model, consistent with disclosed embodiments. Process 300 can include the steps of retrieving a synthetic dataset model from model storage 109, retrieving data from database 105, providing synthetic data to computing resources 101, providing an initialized data model to computing resources 101, and providing a trained data model to model optimizer 107. In this manner, process 300 can allow system 100 to generate a model using synthetic data.
Process 300 can then proceed to step 301. In step 301, dataset generator 103 can retrieve a training dataset from database 105. The training dataset can include actual training data, in some aspects. The training dataset can include synthetic training data, in some aspects. In some embodiments, dataset generator 103 can be configured to generate synthetic data from sample values. For example, dataset generator 103 can be configured to use the generative network of a generative adversarial network to generate data samples from random-valued vectors. In such embodiments, process 300 may forgo step 301.
Process 300 can then proceed to step 303. In step 303, dataset generator 103 can be configured to receive a synthetic data model from model storage 109. In some embodiments, model storage 109 can be configured to provide the synthetic data model to dataset generator 103 in response to a request from dataset generator 103. In various embodiments, model storage 109 can be configured to provide the synthetic data model to dataset generator 103 in response to a request from model optimizer 107, or another component of system 100. As a non-limiting example, the synthetic data model can be a neural network, recurrent neural network (which may include LSTM units), generative adversarial network, kernel density estimator, random value generator, or the like.
Process 300 can then proceed to step 305. In step 305, in some embodiments, dataset generator 103 can generate synthetic data. Dataset generator 103 can be configured, in some embodiments, to identify sensitive data items (e.g., account numbers, social security numbers, names, addresses, API keys, network or IP addresses, or the like) in the data received from model storage 109. In some embodiments, dataset generator 103 can be configured to identify sensitive data items using a recurrent neural network. Dataset generator 103 can be configured to use the data model retrieved from model storage 109 to generate a synthetic dataset by replacing the sensitive data items with synthetic data items.
Dataset generator 103 can be configured to provide the synthetic dataset to computing resources 101. In some embodiments, dataset generator 103 can be configured to provide the synthetic dataset to computing resources 101 in response to a request from computing resources 101, model optimizer 107, or another component of system 100. In various embodiments, dataset generator 103 can be configured to provide the synthetic dataset to database 105 for storage. In such embodiments, computing resources 101 can be configured to subsequently retrieve the synthetic dataset from database 105 directly, or indirectly through model optimizer 107 or dataset generator 103.
Process 300 can then proceed to step 307. In step 307, computing resources 101 can be configured to receive a data model from model optimizer 107, consistent with disclosed embodiments. In some embodiments, the data model can be at least partially initialized by model optimizer 107. For example, at least some of the initial weights and offsets of a neural network model received by computing resources 101 in step 307 can be set by model optimizer 107. In various embodiments, computing resources 101 can be configured to receive at least some training parameters from model optimizer 107 (e.g., batch size, number of training batches, number of epochs, chunk size, time window, input noise dimension, or the like).
Process 300 can then proceed to step 309. In step 309, computing resources 101 can generate a trained data model using the data model received from model optimizer 107 and the synthetic dataset received from dataset generator 103. For example, computing resources 101 can be configured to train the data model received from model optimizer 107 until some training criterion is satisfied. The training criterion can be, for example, a performance criterion (e.g., a Mean Absolute Error, Root Mean Squared Error, percent good classification, and the like), a convergence criterion (e.g., a minimum required improvement of a performance criterion over iterations or over time, a minimum required change in model parameters over iterations or over time), elapsed time or number of iterations, or the like. In some embodiments, the performance criterion can be a threshold value for a similarity metric or prediction accuracy metric as described herein. Satisfaction of the training criterion can be determined by one or more of computing resources 101 and model optimizer 107. In some embodiments, computing resources 101 can be configured to update model optimizer 107 regarding the training status of the data model. For example, computing resources 101 can be configured to provide the current parameters of the data model and/or current performance criteria of the data model. In some embodiments, model optimizer 107 can be configured to stop the training of the data model by computing resources 101. In various embodiments, model optimizer 107 can be configured to retrieve the data model from computing resources 101. In some embodiments, computing resources 101 can be configured to stop training the data model and provide the trained data model to model optimizer 107.
FIG. 4 depicts a specific implementation (system 400) of system 100 of FIG. 1. As shown in FIG. 4, the functionality of system 100 can be divided between a distributor 401, a dataset generation instance 403, a development environment 405, a model optimization instance 409, and a production environment 411. In this manner, system 100 can be implemented in a stable and scalable fashion using a distributed computing environment, such as a public cloud-computing environment, a private cloud computing environment, a hybrid cloud computing environment, a computing cluster or grid, or the like. As present computing requirements increase for a component of system 400 (e.g., as production environment 411 is called upon to instantiate additional production instances to address requests for additional synthetic data streams), additional physical or virtual machines can be recruited to that component. In some embodiments, dataset generator 103 and model optimizer 107 can be hosted by separate virtual computing instances of the cloud computing system.
Distributor 401 can be configured to provide, consistent with disclosed embodiments, an interface between the components of system 400, and between the components of system 400 and other systems. In some embodiments, distributor 401 can be configured to implement interface 113 and a load balancer. Distributor 401 can be configured to route messages between computing resources 101 (e.g., implemented on one or more of development environment 405 and production environment 411), dataset generator 103 (e.g., implemented on dataset generator instance 403), and model optimizer 107 (e.g., implemented on model optimization instance 409). The messages can include data and instructions. For example, the messages can include model generation requests and trained models provided in response to model generation requests. As an additional example, the messages can include synthetic data sets or synthetic data streams. Consistent with disclosed embodiments, distributor 401 can be implemented using one or more EC2 clusters or the like.
Data generation instance 403 can be configured to generate synthetic data, consistent with disclosed embodiments. In some embodiments, data generation instance 403 can be configured to receive actual or synthetic data from data source 417. In various embodiments, data generation instance 403 can be configured to receive synthetic data models for generating the synthetic data. In some aspects, the synthetic data models can be received from another component of system 400, such as data source 417.
Development environment 405 can be configured to implement at least a portion of the functionality of computing resources 101, consistent with disclosed embodiments. For example, development environment 405 can be configured to train data models for subsequent use by other components of system 400. In some aspects, development instances (e.g., development instance 407) hosted by development environment 405 can train one or more individual data models. In some aspects, development environment 405 be configured to spin up additional development instances to train additional data models, as needed. In some aspects, a development instance can implement an application framework such as TENSORBOARD, JUPYTER and the like; as well as machine learning applications like TENSORFLOW, CUDNN, KERAS, and the like. Consistent with disclosed embodiments, these application frameworks and applications can enable the specification and training of data models. In various aspects, development environment 405 can be implemented using one or more EC2 clusters or the like.
Model optimization instance 409 can be configured to manage training and provision of data models by system 400. In some aspects, model optimization instance 409 can be configured to provide the functionality of model optimizer 107. For example, model optimization instance 409 can be configured to provide training parameters and at least partially initialized data models to development environment 405. This selection can be based on model performance feedback received from development environment 405. As an additional example, model optimization instance 409 can be configured to determine whether a data model satisfies performance criteria. In some aspects, model optimization instance 409 can be configured to provide trained models and descriptive information concerning the trained models to another component of system 400. In various aspects, model optimization instance 409 can be implemented using one or more EC2 clusters or the like.
Production environment 405 can be configured to implement at least a portion of the functionality of computing resources 101, consistent with disclosed embodiments. For example, production environment 405 can be configured to use previously trained data models to process data received by system 400. In some aspects, a production instance (e.g., production instance 413) hosted by development environment 411 can be configured to process data using a previously trained data model. In some aspects, the production instance can implement an application framework such as TENSORBOARD, JUPYTER and the like; as well as machine learning applications like TENSORFLOW, CUDNN, KERAS, and the like. Consistent with disclosed embodiments, these application frameworks and applications can enable processing of data using data models. In various aspects, development environment 405 can be implemented using one or more EC2 clusters or the like.
A component of system 400 (e.g., model optimization instance 409) can determine the data model and data source for a production instance according to the purpose of the data processing. For example, system 400 can configure a production instance to produce synthetic data for consumption by other systems. In this example, the production instance can then provide synthetic data for testing another application. As a further example, system 400 can configure a production instance to generate outputs using actual data. For example, system 400 can configure a production instance with a data model for detecting fraudulent transactions. The production instance can then receive a stream of financial transaction data and identify potentially fraudulent transactions. In some aspects, this data model may have been trained by system 400 using synthetic data created to resemble the stream of financial transaction data. System 400 can be configured to provide an indication of the potentially fraudulent transactions to another system configured to take appropriate action (e.g., reversing the transaction, contacting one or more of the parties to the transaction, or the like).
Production environment 411 can be configured to host a file system 415 for interfacing between one or more production instances and data source 417. For example, data source 417 can be configured to store data in file system 415, while the one or more production instances can be configured to retrieve the stored data from file system 415 for processing. In some embodiments, file system 415 can be configured to scale as needed. In various embodiments, file system 415 can be configured to support parallel access by data source 417 and the one or more production instances. For example, file system 415 can be an instance of AMAZON ELASTIC FILE SYSTEM (EFS) or the like.
Data source 417 can be configured to provide data to other components of system 400. In some embodiments, data source 417 can include sources of actual data, such as streams of transaction data, human resources data, web log data, web security data, web protocols data, or system logs data. System 400 can also be configured to implement model storage 109 using a database (not shown) accessible to at least one other component of system 400 (e.g., distributor 401, dataset generation instance 403, development environment 405, model optimization instance 409, or production environment 411). In some aspects, the database can be an s3 bucket, relational database, or the like.
FIG. 5A depicts process 500 for generating synthetic data using class-specific models, consistent with disclosed embodiments. System 100, or a similar system, may be configured to use such synthetic data in training a data model for use in another application (e.g., a fraud detection application). Process 500 can include the steps of retrieving actual data, determining classes of sensitive portions of the data, generating synthetic data using a data model for the appropriate class, and replacing the sensitive data portions with the synthetic data portions. In some embodiments, the data model can be a generative adversarial network trained to generate synthetic data satisfying a similarity criterion, as described herein. By using class-specific models, process 500 can generate better synthetic data that more accurately models the underlying actual data than randomly generated training data that lacks the latent structures present in the actual data. Because the synthetic data more accurately models the underlying actual data, a data model trained using this improved synthetic data may perform better processing the actual data.
Process 500 can then proceed to step 501. In step 501, dataset generator 103 can be configured to retrieve actual data. As a non-limiting example, the actual data may have been gathered during the course of ordinary business operations, marketing operations, research operations, or the like. Dataset generator 103 can be configured to retrieve the actual data from database 105 or from another system. The actual data may have been purchased in whole or in part by an entity associated with system 100. As would be understood from this description, the source and composition of the actual data is not intended to be limiting.
Process 500 can then proceed to step 503. In step 503, dataset generator 103 can be configured to determine classes of the sensitive portions of the actual data. As a non-limiting example, when the actual data is account transaction data, classes could include account numbers and merchant names. As an additional non-limiting example, when the actual data is personnel records, classes could include employee identification numbers, employee names, employee addresses, contact information, marital or beneficiary information, title and salary information, and employment actions. Consistent with disclosed embodiments, dataset generator 103 can be configured with a classifier for distinguishing different classes of sensitive information. In some embodiments, dataset generator 103 can be configured with a recurrent neural network for distinguishing different classes of sensitive information. Dataset generator 103 can be configured to apply the classifier to the actual data to determine that a sensitive portion of the training dataset belongs to the data class. For example, when the data stream includes the text string “Lorem ipsum 012-34-5678 dolor sit amet,” the classifier may be configured to indicate that positions 13-23 of the text string include a potential social security number. Though described with reference to character string substitutions, the disclosed systems and methods are not so limited. As a non-limiting example, the actual data can include unstructured data (e.g., character strings, tokens, and the like) and structured data (e.g., key-value pairs, relational database files, spreadsheets, and the like).
Process 500 can then proceed to step 505. In step 505, dataset generator 103 can be configured to generate a synthetic portion using a class-specific model. To continue the previous example, dataset generator 103 can generate a synthetic social security number using a synthetic data model trained to generate social security numbers. In some embodiments, this class-specific synthetic data model can be trained to generate synthetic portions similar to those appearing in the actual data. For example, as social security numbers include an area number indicating geographic information and a group number indicating date-dependent information, the range of social security numbers present in an actual dataset can depend on the geographic origin and purpose of that dataset. A dataset of social security numbers for elementary school children in a particular school district may exhibit different characteristics than a dataset of social security numbers for employees of a national corporation. To continue the previous example, the social security-specific synthetic data model could generate the synthetic portion “03-74-3285.”
Process 500 can then proceed to step 507. In step 507, dataset generator 103 can be configured to replace the sensitive portion of the actual data with the synthetic portion. To continue the previous example, dataset generator 103 could be configured to replace the characters at positions 13-23 of the text string with the values “013-74-3285,” creating the synthetic text string “Lorem ipsum 013-74-3285 dolor sit amet.” This text string can now be distributed without disclosing the sensitive information originally present. But this text string can still be used to train models that make valid inferences regarding the actual data, because synthetic social security numbers generated by the synthetic data model share the statistical characteristic of the actual data.
FIG. 5B depicts a process 510 for generating synthetic data using class and subclass-specific models, consistent with disclosed embodiments. Process 510 can include the steps of retrieving actual data, determining classes of sensitive portions of the data, selecting types for synthetic data used to replace the sensitive portions of the actual data, generating synthetic data using a data model for the appropriate type and class, and replacing the sensitive data portions with the synthetic data portions. In some embodiments, the data model can be a generative adversarial network trained to generate synthetic data satisfying a similarity criterion, as described herein. This improvement addresses a problem with synthetic data generation, that a synthetic data model may fail to generate examples of proportionately rare data subclasses. For example, when data can be classified into two distinct subclasses, with a second subclass far less prevalent in the data than a first subclass, a model of the synthetic data may generate only examples of the most common first data subclasses. The synthetic data model effectively focuses on generating the best examples of the most common data subclasses, rather than acceptable examples of all the data subclasses. Process 510 addresses this problem by expressly selecting subclasses of the synthetic data class according to a distribution model based on the actual data.
Process 510 can then proceed through step 511 and step 513, which resemble step 501 and step 503 in process 500. In step 511, dataset generator 103 can be configured to receive actual data. In step 513, dataset generator can be configured to determine classes of sensitive portions of the actual data. In a non-limiting example, dataset generator 103 can be configured to determine that a sensitive portion of the data may contain a financial service account number. Dataset generator 103 can be configured to identify this sensitive portion of the data as a financial service account number using a classifier, which may in some embodiments be a recurrent neural network (which may include LSTM units).
Process 510 can then proceed to step 515. In step 515, dataset generator 103 can be configured to select a subclass for generating the synthetic data. In some aspects, this selection is not governed by the subclass of the identified sensitive portion. For example, in some embodiments the classifier that identifies the class need not be sufficiently discerning to identify the subclass, relaxing the requirements on the classifier. Instead, this selection is based on a distribution model. For example, dataset generator 103 can be configured with a statistical distribution of subclasses (e.g., a univariate distribution of subclasses) for that class and can select one of the subclasses for generating the synthetic data according to the statistical distribution. To continue the previous example, individual accounts and trust accounts may both be financial service account numbers, but the values of these accounts numbers may differ between individual accounts and trust accounts. Furthermore, there may be 19 individual accounts for every 1 trust account. In this example, dataset generator 103 can be configured to select the trust account subclass 1 time in 20, and use a synthetic data model for financial service account numbers for trust accounts to generate the synthetic data. As a further example, dataset generator 103 can be configured with a recurrent neural network that estimates the next subclass based on the current and previous subclasses. For example, healthcare records can include cancer diagnosis stage as sensitive data. Most cancer diagnosis stage values may be “no cancer” and the value of “stage 1” may be rare, but when present in a patient record this value may be followed by “stage 2,” etc. The recurrent neural network can be trained on the actual healthcare records to use prior and cancer diagnosis stage values when selecting the subclass. For example, when generating a synthetic healthcare record, the recurrent neural network can be configured to use the previously selected cancer diagnosis stage subclass in selecting the present cancer diagnosis stage subclass. In this manner, the synthetic healthcare record can exhibit an appropriate progression of patient health that matches the progression in the actual data.
Process 510 can then proceed to step 517. In step 517, which resembles step 505, dataset generator 103 can be configured to generate synthetic data using a class and subclass specific model. To continue the previous financial service account number example, dataset generator 103 can be configured to use a synthetic data for trust account financial service account numbers to generate the synthetic financial server account number.
Process 510 can then proceed to step 519. In step 519, which resembles step 507, dataset generator 103 can be configured to replace the sensitive portion of the actual data with the generated synthetic data. For example, dataset generator 103 can be configured to replace the financial service account number in the actual data with the synthetic trust account financial service account number.
FIG. 6 depicts a process 600 for training a classifier for generation of synthetic data. In some embodiments, such a classifier could be used by dataset generator 103 to classify sensitive data portions of actual data, as described above with regards to FIGS. 5A and 5B. Process 600 can include the steps of receiving data sequences, receiving content sequences, generating training sequences, generating label sequences, and training a classifier using the training sequences and the label sequences. By using known data sequences and content sequences unlikely to contain sensitive data, process 600 can be used to automatically generate a corpus of labeled training data. Process 600 can be performed by a component of system 100, such as dataset generator 103 or model optimizer 107.
Process 600 can then proceed to step 601. In step 601, system 100 can receive training data sequences. The training data sequences can be received from a dataset. The dataset providing the training data sequences can be a component of system 100 (e.g., database 105) or a component of another system. The data sequences can include multiple classes of sensitive data. As a non-limiting example, the data sequences can include account numbers, social security numbers, and full names.
Process 600 can then proceed to step 603. In step 603, system 100 can receive context sequences. The context sequences can be received from a dataset. The dataset providing the context sequences can be a component of system 100 (e.g., database 105) or a component of another system. In various embodiments, the context sequences can be drawn from a corpus of pre-existing data, such as an open-source text dataset (e.g., Yelp Open Dataset or the like). In some aspects, the context sequences can be snippets of this pre-existing data, such as a sentence or paragraph of the pre-existing data.
Process 600 can then proceed to step 605. In step 605, system 100 can generate training sequences. In some embodiments, system 100 can be configured to generate a training sequence by inserting a data sequence into a context sequence. The data sequence can be inserted into the context sequence without replacement of elements of the context sequence or with replacement of elements of the context sequence. The data sequence can be inserted into the context sequence between elements (e.g., at a whitespace character, tab, semicolon, html closing tag, or other semantic breakpoint) or without regard to the semantics of the context sequence. For example, when the context sequence is “Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod” and the data sequence is “013-74-3285,” the training sequence can be “Lorem ipsum dolor sit amet, 013-74-3285 consectetur adipiscing elit, sed do eiusmod,” “Lorem ipsum dolor sit amet, 013-74-3285 adipiscing elit, sed do eiusmod,” or “Lorem ipsum dolor sit amet, conse013-74-3285ctetur adipiscing elit, sed do eiusmod.” In some embodiments, a training sequence can include multiple data sequences.
After step 601 and step 603, process 600 can proceed to step 607. In step 607, system 100 can generate a label sequence. In some aspects, the label sequence can indicate a position of the inserted data sequence in the training sequence. In various aspects, the label sequence can indicate the class of the data sequence. As a non-limiting example, when the training sequence is “dolor sit amet, 013-74-3285 consectetur adipiscing,” the label sequence can be “00000000000000001111111111100000000000000000000000,” where the value “0” indicates that a character is not part of a sensitive data portion and the value “1” indicates that a character is part of the social security number. A different class or subclass of data sequence could include a different value specific to that class or subclass. Because system 100 creates the training sequences, system 100 can automatically create accurate labels for the training sequences.
Process 600 can then proceed to step 609. In step 609, system 100 can be configured to use the training sequences and the label sequences to train a classifier. In some aspects, the label sequences can provide a “ground truth” for training a classifier using supervised learning. In some embodiments, the classifier can be a recurrent neural network (which may include LSTM units). The recurrent neural network can be configured to predict whether a character of a training sequence is part of a sensitive data portion. This prediction can be checked against the label sequence to generate an update to the weights and offsets of the recurrent neural network. This update can then be propagated through the recurrent neural network, according to methods described in “Training Recurrent Neural Networks,” 2013, by Ilya Sutskever, which is incorporated herein by reference in its entirety.
FIG. 7 depicts a process 700 for training a classifier for generation of synthetic data, consistent with disclosed embodiments. According to process 700, a data sequence 701 can include preceding samples 703, current sample 705, and subsequent samples 707. In some embodiments, data sequence 701 can be a subset of a training sequence, as described above with regard to FIG. 6. Data sequence 701 may be applied to recurrent neural network 709. In some embodiments, neural network 709 can be configured to estimate whether current sample 705 is part of a sensitive data portion of data sequence 701 based on the values of preceding samples 703, current sample 705, and subsequent samples 707. In some embodiments, preceding samples 703 can include between 1 and 100 samples, for example between 25 and 75 samples. In various embodiments, subsequent samples 707 can include between 1 and 100 samples, for example between 25 and 75 samples. In some embodiments, the preceding samples 703 and the subsequent samples 707 can be paired and provided to recurrent neural network 709 together. For example, in a first iteration, the first sample of preceding samples 703 and the last sample of subsequent samples 707 can be provided to recurrent neural network 709. In the next iteration, the second sample of preceding samples 703 and the second-to-last sample of subsequent samples 707 can be provided to recurrent neural network 709. System 100 can continue to provide samples to recurrent neural network 709 until all of preceding samples 703 and subsequent samples 707 have been input to recurrent neural network 709. System 100 can then provide current sample 705 to recurrent neural network 709. The output of recurrent neural network 709 after the input of current sample 705 can be estimated label 711. Estimated label 711 can be the inferred class or subclass of current sample 705, given data sequence 701 as input. In some embodiments, estimated label 711 can be compared to actual label 713 to calculate a loss function. Actual label 713 can correspond to data sequence 701. For example, when data sequence 701 is a subset of a training sequence, actual label 713 can be an element of the label sequence corresponding to the training sequence. In some embodiments, actual label 713 can occupy the same position in the label sequence as occupied by current sample 705 in the training sequence. Consistent with disclosed embodiments, system 100 can be configured to update recurrent neural network 709 using loss function 715 based on a result of the comparison.
FIG. 8 depicts a process 800 for training a generative adversarial network using a normalized reference dataset. In some embodiments, the generative adversarial network can be used by system 100 (e.g., by dataset generator 103) to generate synthetic data (e.g., as described above with regards to FIGS. 2, 3, 5A and 5B). The generative adversarial network can include a generator network and a discriminator network. The generator network can be configured to learn a mapping from a sample space (e.g., a random number or vector) to a data space (e.g. the values of the sensitive data). The discriminator can be configured to determine, when presented with either an actual data sample or a sample of synthetic data generated by the generator network, whether the sample was generated by the generator network or was a sample of actual data. As training progresses, the generator can improve at generating the synthetic data and the discriminator can improve at determining whether a sample is actual or synthetic data. In this manner, a generator can be automatically trained to generate synthetic data similar to the actual data. However, a generative adversarial network can be limited by the actual data. For example, an unmodified generative adversarial network may be unsuitable for use with categorical data or data including missing values, not-a-numbers, or the like. For example, the generative adversarial network may not know how to interpret such data. Disclosed embodiments address this technical problem by at least one of normalizing categorical data or replacing missing values with supra-normal values.
Process 800 can then proceed to step 801. In step 801, system 100 (e.g., dataset generator 103) can retrieve a reference dataset from a database (e.g., database 105). The reference dataset can include categorical data. For example, the reference dataset can include spreadsheets or relational databases with categorical-valued data columns. As a further example, the reference dataset can include missing values, not-a-number values, or the like.
Process 800 can then proceed to step 803. In step 803, system 100 (e.g., dataset generator 103) can generate a normalized training dataset by normalizing the reference dataset. For example, system 100 can be configured to normalize categorical data contained in the reference dataset. In some embodiments, system 100 can be configured to normalize the categorical data by converting this data to numerical values. The numerical values can lie within a predetermined range. In some embodiments, the predetermined range can be zero to one. For example, given a column of categorical data including the days of the week, system 100 can be configured to map these days to values between zero and one. In some embodiments, system 100 can be configured to normalize numerical data in the reference dataset as well, mapping the values of the numerical data to a predetermined range.
Process 800 can then proceed to step 805. In step 805, system 100 (e.g., dataset generator 103) can generate the normalized training dataset by converting special values to values outside the predetermined range. For example, system 100 can be configured to assign missing values a first numerical value outside the predetermined range. As an additional example, system 100 can be configured to assign not-a-number values to a second numerical value outside the predetermined range. In some embodiments, the first value and the second value can differ. For example, system 100 can be configured to map the categorical values and the numerical values to the range of zero to one. In some embodiments, system 100 can then map missing values to the numerical value 1.5. In various embodiments, system 100 can then map not-a-number values to the numerical value of −0.5. In this manner system 100 can preserve information about the actual data while enabling training of the generative adversarial network.
Process 800 can then proceed to step 807. In step 807, system 100 (e.g., dataset generator 103) can train the generative network using the normalized dataset, consistent with disclosed embodiments.
FIG. 9 depicts a process 900 for training a generative adversarial network using a loss function configured to ensure a predetermined degree of similarity, consistent with disclosed embodiments. System 100 can be configured to use process 900 to generate synthetic data that is similar, but not too similar to the actual data, as the actual data can include sensitive personal information. For example, when the actual data includes social security numbers or account numbers, the synthetic data would preferably not simply recreate these numbers. Instead, system 100 would preferably create synthetic data that resembles the actual data, as described below, while reducing the likelihood of overlapping values. To address this technical problem, system 100 can be configured to determine a similarity metric value between the synthetic dataset and the normalized reference dataset, consistent with disclosed embodiments. System 100 can be configured to use the similarity metric value to update a loss function for training the generative adversarial network. In this manner, system 100 can be configured to determine a synthetic dataset differing in value from the normalized reference dataset at least a predetermined amount according to the similarity metric.
While described below with regard to training a synthetic data model, dataset generator 103 can be configured to use such trained synthetic data models to generate synthetic data (e.g., as described above with regards to FIGS. 2 and 3). For example, development instances (e.g., development instance 407) and production instances (e.g., production instance 413) can be configured to generate data similar to a reference dataset according to the disclosed systems and methods.
Process 900 can then proceed to step 901, which can resemble step 801. In step 901, system 100 (e.g., model optimizer 107, computational resources 101, or the like) can receive a reference dataset. In some embodiments, system 100 can be configured to receive the reference dataset from a database (e.g., database 105). The reference dataset can include categorical and/or numerical data. For example, the reference dataset can include spreadsheet or relational database data. In some embodiments, the reference dataset can include special values, such as missing values, not-a-number values, or the like.
Process 900 can then proceed to step 903. In step 903, system 100 (e.g., dataset generator 103, model optimizer 107, computational resources 101, or the like) can be configured to normalize the reference dataset. In some instances, system 100 can be configured to normalize the reference dataset as described above with regard to steps 803 and 805 of process 800. For example, system 100 can be configured to normalize the categorical data and/or the numerical data in the reference dataset to a predetermined range. In some embodiments, system 100 can be configured to replace special values with numerical values outside the predetermined range.
Process 900 can then proceed to step 905. In step 905, system 100 (e.g., model optimizer 107, computational resources 101, or the like) can generate a synthetic training dataset using the generative network. For example, system 100 can apply one or more random samples to the generative network to generate one or more synthetic data items. In some instances, system 100 can be configured to generate between 200 and 400,000 data items, or preferably between 20,000 and 40,000 data items.
Process 900 can then proceed to step 907. In step 907, system 100 (e.g., model optimizer 107, computational resources 101, or the like) can determine a similarity metric value using the normalized reference dataset and the synthetic training dataset. System 100 can be configured to generate the similarity metric value according to a similarity metric. In some aspects, the similarity metric value can include at least one of a statistical correlation score (e.g., a score dependent on the covariances or univariate distributions of the synthetic data and the normalized reference dataset), a data similarity score (e.g., a score dependent on a number of matching or similar elements in the synthetic dataset and normalized reference dataset), or data quality score (e.g., a score dependent on at least one of a number of duplicate elements in each of the synthetic dataset and normalized reference dataset, a prevalence of the most common value in each of the synthetic dataset and normalized reference dataset, a maximum difference of rare values in each of the synthetic dataset and normalized reference dataset, the differences in schema between the synthetic dataset and normalized reference dataset, or the like). System 100 can be configured to calculate these scores using the synthetic dataset and a reference dataset.
In some aspects, the similarity metric can depend on a covariance of the synthetic dataset and a covariance of the normalized reference dataset. For example, in some embodiments, system 100 can be configured to generate a difference matrix using a covariance matrix of the normalized reference dataset and a covariance matrix of the synthetic dataset. As a further example, the difference matrix can be the difference between the covariance matrix of the normalized reference dataset and the covariance matrix of the synthetic dataset. The similarity metric can depend on the difference matrix. In some aspects, the similarity metric can depend on the summation of the squared values of the difference matrix. This summation can be normalized, for example by the square root of the product of the number of rows and number of columns of the covariance matrix for the normalized reference dataset.
In some embodiments, the similarity metric can depend on a univariate value distribution of an element of the synthetic dataset and a univariate value distribution of an element of the normalized reference dataset. For example, for corresponding elements of the synthetic dataset and the normalized reference dataset, system 100 can be configured to generate histograms having the same bins. For each bin, system 100 can be configured to determine a difference between the value of the bin for the synthetic data histogram and the value of the bin for the normalized reference dataset histogram. In some embodiments, the values of the bins can be normalized by the total number of datapoints in the histograms. For each of the corresponding elements, system 100 can be configured to determine a value (e.g., a maximum difference, an average difference, a Euclidean distance, or the like) of these differences. In some embodiments, the similarity metric can depend on a function of this value (e.g., a maximum, average, or the like) across the common elements. For example, the normalized reference dataset can include multiple columns of data. The synthetic dataset can include corresponding columns of data. The normalized reference dataset and the synthetic dataset can include the same number of rows. System 100 can be configured to generate histograms for each column of data for each of the normalized reference dataset and the synthetic dataset. For each bin, system 100 can determine the difference between the count of datapoints in the normalized reference dataset histogram and the synthetic dataset histogram. System 100 can determine the value for this column to be the maximum of the differences for each bin. System 100 can determine the value for the similarity metric to be the average of the values for the columns. As would be appreciated by one of skill in the art, this example is not intended to be limiting.
In various embodiments, the similarity metric can depend on a number of elements of the synthetic dataset that match elements of the reference dataset. In some embodiments, the matching can be an exact match, with the value of an element in the synthetic dataset matching the value of an element in the normalized reference dataset. As a nonlimiting example, when the normalized reference dataset includes a spreadsheet having rows and columns, and the synthetic dataset includes a spreadsheet having rows and corresponding columns, the similarity metric can depend on the number of rows of the synthetic dataset that have the same values as rows of the normalized reference dataset. In some embodiments, the normalized reference dataset and synthetic dataset can have duplicate rows removed prior to performing this comparison. System 100 can be configured to merge the non-duplicate normalized reference dataset and non-duplicate synthetic dataset by all columns. In this non-limiting example, the size of the resulting dataset will be the number of exactly matching rows. In some embodiments, system 100 can be configured to disregard columns that appear in one dataset but not the other when performing this comparison.
In various embodiments, the similarity metric can depend on a number of elements of the synthetic dataset that are similar to elements of the normalized reference dataset. System 100 can be configured to calculate similarity between an element of the synthetic dataset and an element of the normalized reference dataset according to distance measure. In some embodiments, the distance measure can depend on a Euclidean distance between the elements. For example, when the synthetic dataset and the normalized reference dataset include rows and columns, the distance measure can depend on a Euclidean distance between a row of the synthetic dataset and a row of the normalized reference dataset. In various embodiments, when comparing a synthetic dataset to an actual dataset including categorical data (e.g., a reference dataset that has not been normalized), the distance measure can depend on a Euclidean distance between numerical row elements and a Hamming distance between non-numerical row elements. The Hamming distance can depend on a count of non-numerical elements differing between the row of the synthetic dataset and the row of the actual dataset. In some embodiments, the distance measure can be a weighted average of the Euclidean distance and the Hamming distance. In some embodiments, system 100 can be configured to disregard columns that appear in one dataset but not the other when performing this comparison. In various embodiments, system 100 can be configured to remove duplicate entries from the synthetic dataset and the normalized reference dataset before performing the comparison.
In some embodiments, system 100 can be configured to calculate a distance measure between each row of the synthetic dataset (or a subset of the rows of the synthetic dataset) and each row of the normalized reference dataset (or a subset of the rows of the normalized reference dataset). System 100 can then determine the minimum distance value for each row of the synthetic dataset across all rows of the normalized reference dataset. In some embodiments, the similarity metric can depend on a function of the minimum distance values for all rows of the synthetic dataset (e.g., a maximum value, an average value, or the like).
In some embodiments, the similarity metric can depend on a frequency of duplicate elements in the synthetic dataset and the normalized reference dataset. In some aspects, system 100 can be configured to determine the number of duplicate elements in each of the synthetic dataset and the normalized reference dataset. In various aspects, system 100 can be configured to determine the proportion of each dataset represented by at least some of the elements in each dataset. For example, system 100 can be configured to determine the proportion of the synthetic dataset having a particular value. In some aspects, this value may be the most frequent value in the synthetic dataset. System 100 can be configured to similarly determine the proportion of the normalized reference dataset having a particular value (e.g., the most frequent value in the normalized reference dataset).
In some embodiments, the similarity metric can depend on a relative prevalence of rare values in the synthetic and normalized reference dataset. In some aspects, such rare values can be those present in a dataset with frequencies less than a predetermined threshold. In some embodiments, the predetermined threshold can be a value less than 20%, for example 10%. System 100 can be configured to determine a prevalence of rare values in the synthetic and normalized reference dataset. For example, system 100 can be configured to determine counts of the rare values in a dataset and the total number of elements in the dataset. System 100 can then determine ratios of the counts of the rare values to the total number of elements in the datasets.
In some embodiments, the similarity metric can depend on differences in the ratios between the synthetic dataset and the normalized reference dataset. As a non-limiting example, an exemplary dataset can be an access log for patient medical records that tracks the job title of the employee accessing a patient medical record. The job title “Administrator” may be a rare value of job title and appear in 3% of the log entries. System 100 can be configured to generate synthetic log data based on the actual dataset, but the job title “Administrator” may not appear in the synthetic log data. The similarity metric can depend on difference between the actual dataset prevalence (3%) and the synthetic log data prevalence (0%). As an alternative example, the job title “Administrator” may be overrepresented in the synthetic log data, appearing in 15% of the of the log entries (and therefore not a rare value in the synthetic log data when the predetermined threshold is 10%). In this example, the similarity metric can depend on difference between the actual dataset prevalence (3%) and the synthetic log data prevalence (15%).
In various embodiments, the similarity metric can depend on a function of the differences in the ratios between the synthetic dataset and the normalized reference dataset. For example, the actual dataset may include 10 rare values with a prevalence under 10% of the dataset. The difference between the prevalence of these 10 rare values in the actual dataset and the normalized reference dataset can range from −5% to 4%. In some embodiments, the similarity metric can depend on the greatest magnitude difference (e.g., the similarity metric could depend on the value −5% as the greatest magnitude difference). In various embodiments, the similarity metric can depend on the average of the magnitude differences, the Euclidean norm of the ratio differences, or the like.
In various embodiments, the similarity metric can depend on a difference in schemas between the synthetic dataset and the normalized reference dataset. For example, when the synthetic dataset includes spreadsheet data, system 100 can be configured to determine a number of mismatched columns between the synthetic and normalized reference datasets, a number of mismatched column types between the synthetic and normalized reference datasets, a number of mismatched column categories between the synthetic and normalized reference datasets, and number of mismatched numeric ranges between the synthetic and normalized reference datasets. The value of the similarity metric can depend on the number of at least one of the mismatched columns, mismatched column types, mismatched column categories, or mismatched numeric ranges.
In some embodiments, the similarity metric can depend on one or more of the above criteria. For example, the similarity metric can depend on one or more of (1) a covariance of the output data and a covariance of the normalized reference dataset, (2) a univariate value distribution of an element of the synthetic dataset, (3) a univariate value distribution of an element of the normalized reference dataset, (4) a number of elements of the synthetic dataset that match elements of the reference dataset, (5) a number of elements of the synthetic dataset that are similar to elements of the normalized reference dataset, (6) a distance measure between each row of the synthetic dataset (or a subset of the rows of the synthetic dataset) and each row of the normalized reference dataset (or a subset of the rows of the normalized reference dataset), (7) a frequency of duplicate elements in the synthetic dataset and the normalized reference dataset, (8) a relative prevalence of rare values in the synthetic and normalized reference dataset, and (9) differences in the ratios between the synthetic dataset and the normalized reference dataset.
System 100 can compare a synthetic dataset to a normalized reference dataset, a synthetic dataset to an actual (unnormalized) dataset, or to compare two datasets according to a similarity metric consistent with disclosed embodiments. For example, in some embodiments, model optimizer 107 can be configured to perform such comparisons. In various embodiments, model storage 105 can be configured to store similarity metric information (e.g., similarity values, indications of comparison datasets, and the like) together with a synthetic dataset.
Process 900 can then proceed to step 909. In step 909, system 100 (e.g., model optimizer 107, computational resources 101, or the like) can train the generative adversarial network using the similarity metric value. In some embodiments, system 100 can be configured to determine that the synthetic dataset satisfies a similarity criterion. The similarity criterion can concern at least one of the similarity metrics described above. For example, the similarity criterion can concern at least one of a statistical correlation score between the synthetic dataset and the normalized reference dataset, a data similarity score between the synthetic dataset and the reference dataset, or a data quality score for the synthetic dataset.
In some embodiments, synthetic data satisfying the similarity criterion can be too similar to the reference dataset. System 100 can be configured to update a loss function for training the generative adversarial network to decrease the similarity between the reference dataset and synthetic datasets generated by the generative adversarial network when the similarity criterion is satisfied. In particular, the loss function of the generative adversarial network can be configured to penalize generation of synthetic data that is too similar to the normalized reference dataset, up to a certain threshold. To that end, a penalty term can be added to the loss function of the generative adversarial network. This term can penalize the calculated loss if the dissimilarity between the synthetic data and the actual data goes below a certain threshold. In some aspects, this penalty term can thereby ensure that the value of the similarity metric exceeds some similarity threshold, or remains near the similarity threshold (e.g., the value of the similarity metric may exceed 90% of the value of the similarity threshold). In this non-limiting example, decreasing values of the similarity metric can indicate increasing similarity. System 100 can then update the loss function such that the likelihood of generating synthetic data like the current synthetic data is reduced. In this manner, system 100 can train the generative adversarial network using a loss function that penalizes generation of data differing from the reference dataset by less than the predetermined amount.
FIG. 10 depicts a process 1000 for supplementing or transforming datasets using code-space operations, consistent with disclosed embodiments. Process 1000 can include the steps of generating encoder and decoder models that map between a code space and a sample space, identifying representative points in code space, generating a difference vector in code space, and generating extreme points or transforming a dataset using the difference vector. In this manner, process 1000 can support model validation and simulation of conditions differing from those present during generation of a training dataset. For example, while existing systems and methods may train models using datasets representative of typical operating conditions, process 1000 can support model validation by inferring datapoints that occur infrequently or outside typical operating conditions. As an additional example, a training data include operations and interactions typical of a first user population. Process 1000 can support simulation of operations and interactions typical of a second user population that differs from the first user population. To continue this example, a young user population may interact with a system. Process 1000 can support generation of a synthetic training dataset representative of an older user population interacting with the system. This synthetic training dataset can be used to simulate performance of the system with an older user population, before developing that userbase.
After starting, process 1000 can proceed to step 1001. In step 1001, system 1001 can generate an encoder model and a decoder model. Consistent with disclosed embodiments, system 100 can be configured to generate an encoder model and decoder model using an adversarially learned inference model, as disclosed in “Adversarially Learned Inference” by Vincent Dumoulin, et al. According to the adversarially learned inference model, an encoder maps from a sample space to a code space and a decoder maps from a code space to a sample space. The encoder and decoder are trained by selecting either a code and generating a sample using the decoder or by selecting a sample and generating a code using the encoder. The resulting pairs of code and sample are provided to a discriminator model, which is trained to determine whether the pairs of code and sample came from the encoder or decoder. The encoder and decoder can be updated based on whether the discriminator correctly determined the origin of the samples. Thus, the encoder and decoder can be trained to fool the discriminator. When appropriately trained, the joint distribution of code and sample for the encoder and decoder match. As would be appreciated by one of skill in the art, other techniques of generating a mapping from a code space to a sample space may also be used. For example, a generative adversarial network can be used to learn a mapping from the code space to the sample space.
Process 1000 can then proceed to step 1003. In step 1003, system 100 can identify representative points in the code space. System 100 can identify representative points in the code space by identifying points in the sample space, mapping the identified points into code space, and determining the representative points based on the mapped points, consistent with disclosed embodiments. In some embodiments, the identified points in the sample space can be elements of a dataset (e.g., an actual dataset or a synthetic dataset generated using an actual dataset).
System 100 can identify points in the sample space based on sample space characteristics. For example, when the sample space includes financial account information, system 100 can be configured to identify one or more first accounts belonging to users in their 20s and one or more second accounts belonging to users in their 40s.
Consistent with disclosed embodiments, identifying representative points in the code space can include a step of mapping the one or more first points in the sample space and the one or more second points in the sample space to corresponding points in the code space. In some embodiments, the one or more first points and one or more second points can be part of a dataset. For example, the one or more first points and one or more second points can be part of an actual dataset or a synthetic dataset generated using an actual dataset.
System 100 can be configured to select first and second representative points in the code space based on the mapped one or more first points and the mapped one or more second points. As shown in FIG. 11A, when the one or more first points include a single point, the mapping of this single point to the code space (e.g., point 1101) can be a first representative point in code space 1100. Likewise, when the one or more second points include a single point, the mapping of this single point to the code space (e.g., point 1103) can be a second representative point in code space 1100.
As shown in FIG. 11B, when the one or more first points include multiple points, system 100 can be configured to determine a first representative point in code space 1110. In some embodiments, system 100 can be configured to determine the first representative point based on the locations of the mapped one or more first points in the code space. In some embodiments, the first representative point can be a centroid or a medoid of the mapped one or more first points. Likewise, system 100 can be configured to determine the second representative point based on the locations of the mapped one or more second points in the code space. In some embodiments, the second representative point can be a centroid or a medoid of the mapped one or more second points. For example, system 100 can be configured to identify point 1113 as the first representative point based on the locations of mapped points 1111 a and 1111 b. Likewise, system 100 can be configured to identify point 1117 as the second representative point based on the locations of mapped points 1115 a and 1115 b.
In some embodiments, the code space can include a subset of Rⁿ. System 100 can be configured to map a dataset to the code space using the encoder. System 100 can then identify the coordinates of the points with respect to a basis vector in Rⁿ(e.g., one of the vectors of the identity matrix). System 100 can be configured to identify a first point with a minimum coordinate value with respect to the basis vector and a second point with a maximum coordinate value with respect to the basis vector. System 100 can be configured to identify these points as the first and second representative points. For example, taking the identity matrix as the basis, system 100 can be configured to select as the first point the point with the lowest value of the first element of the vector. To continue this example, system 100 can be configured to select as the second point the point with the highest value of the first element of the vector. In some embodiments, system 100 can be configured to repeat process 1000 for each vector in the basis.
Process 1000 can then proceed to step 1005. In step 1005, system 100 can determine a difference vector connecting the first representative point and the second representative point. For example, as shown in FIG. 11A, system 100 can be configured to determine a vector 1105 from first representative point 1101 to second representative point 1103. Likewise, as shown in FIG. 11B, system 100 can be configured to determine a vector 1119 from first representative point 1113 to second representative point 1117.
Process 1000 can then proceed to step 1007. In step 1007, as depicted in FIG. 12A, system 100 can generate extreme codes. Consistent with disclosed embodiments, system 100 can be configured to generate extreme codes by sampling the code space (e.g., code space 1200) along an extension (e.g., extension 1201) of the vector connecting the first representative point and the second representative point (e.g., vector 1105). In this manner, system 100 can generate a code extreme with respect to the first representative point and the second representative point (e.g. extreme point 1203).
Process 1000 can then proceed to step 1009. In step 1009, as depicted in FIG. 12A, system 100 can generate extreme samples. Consistent with disclosed embodiments, system 100 can be configured to generate extreme samples by converting the extreme code into the sample space using the decoder trained in step 1001. For example, system 100 can be configured to convert extreme point 1203 into a corresponding datapoint in the sample space.
Process 1000 can then proceed to step 1011. In step 1011, as depicted in FIG. 12B, system 100 can translate a dataset using the difference vector determined in step 1005 (e.g., difference vector 1105). In some aspects, system 100 can be configured to convert the dataset from sample space to code space using the encoder trained in step 1001. System 100 can be configured to then translate the elements of the dataset in code space using the difference vector. In some aspects, system 100 can be configured to translate the elements of the dataset using the vector and a scaling factor. In some aspects, the scaling factor can be less than one. In various aspects, the scaling factor can be greater than or equal to one. For example, as shown in FIG. 12B, the elements of the dataset can be translated in code space 1210 by the product of the difference vector and the scaling factor (e.g., original point 1211 can be translated by translation 1212 to translated point 1213).
Process 1000 can then proceed to step 1013. In step 1013, as depicted in FIG. 12B, system 100 can generate a translated dataset. Consistent with disclosed embodiments, system 100 can be configured to generate the translated dataset by converting the translated points into the sample space using the decoder trained in step 1001. For example, system 100 can be configured to convert extreme point translated point 1213 into a corresponding datapoint in the sample space.
FIG. 13 depicts an exemplary cloud computing system 1300 for generating a synthetic data stream that tracks a reference data stream. The flow rate of the synthetic data can resemble the flow rate of the reference data stream, as system 1300 can generate synthetic data in response to receiving reference data stream data. System 1300 can include a streaming data source 1301, model optimizer 1303, computing resource 1304, model storage 1305, dataset generator 1307, and synthetic data source 1309. System 1300 can be configured to generate a new synthetic data model using actual data received from streaming data source 1301. Streaming data source 1301, model optimizer 1303, computing resources 1304, and model storage 1305 can interact to generate the new synthetic data model, consistent with disclosed embodiments. In some embodiments, system 1300 can be configured to generate the new synthetic data model while also generating synthetic data using a current synthetic data model.
Streaming data source 1301 can be configured to retrieve new data elements from a database, a file, a datasource, a topic in a data streaming platform (e.g., IBM STREAMS), a topic in a distributed messaging system (e.g., APACHE KAFKA), or the like. In some aspects, streaming data source 1301 can be configured to retrieve new elements in response to a request from model optimizer 1303. In some aspects, streaming data source 1301 can be configured to retrieve new data elements in real-time. For example, streaming data source 1301 can be configured to retrieve log data, as that log data is created. In various aspects, streaming data source 1301 can be configured to retrieve batches of new data. For example, streaming data source 1301 can be configured to periodically retrieve all log data created within a certain period (e.g., a five-minute interval). In some embodiments, the data can be application logs. The application logs can include event information, such as debugging information, transaction information, user information, user action information, audit information, service information, operation tracking information, process monitoring information, or the like. In some embodiments, the data can be JSON data (e.g., JSON application logs).
System 1300 can be configured to generate a new synthetic data model, consistent with disclosed embodiments. Model optimizer 1303 can be configured to provision computing resources 1304 with a data model, consistent with disclosed embodiments. In some aspects, computing resources 1304 can resemble computing resources 101, described above with regard to FIG. 1. For example, computing resources 1304 can provide similar functionality and can be similarly implemented. The data model can be a synthetic data model. The data model can be a current data model configured to generate data similar to recently received data in the reference data stream. The data model can be received from model storage 1305. For example, model optimizer 1307 can be configured to provide instructions to computing resources 1304 to retrieve a current data model of the reference data stream from model storage 1305. In some embodiments, the synthetic data model can include a recurrent neural network, a kernel density estimator, or a generative adversarial network.
Computing resources 1304 can be configured to train the new synthetic data model using reference data stream data. In some embodiments, system 1300 (e.g., computing resources 1304 or model optimizer 1303) can be configured to include reference data stream data into the training data as it is received from streaming data source 1301. The training data can therefore reflect the current characteristics of the reference data stream (e.g., the current values, current schema, current statistical properties, and the like). In some aspects, system 1300 (e.g., computing resources 1304 or model optimizer 1303) can be configured to store reference data stream data received from streaming data source 1301 for subsequent use as training data. In some embodiments, computing resources 1304 may have received the stored reference data stream data prior to beginning training of the new synthetic data model. As an additional example, computing resources 1304 (or another component of system 1300) can be configured to gather data from streaming data source 1301 during a first time-interval (e.g., the prior repeat) and use this gathered data to train a new synthetic model in a subsequent time-interval (e.g., the current repeat). In various embodiments, computing resources 1304 can be configured to use the stored reference data stream data for training the new synthetic data model. In various embodiments, the training data can include both newly-received and stored data. When the synthetic data model is a Generative Adversarial Network, computing resources 1304 can be configured to train the new synthetic data model, in some embodiments, as described above with regard to FIGS. 8 and 9. Alternatively, computing resources 1304 can be configured to train the new synthetic data model according to know methods.
Model optimizer 1303 can be configured to evaluate performance criteria of a newly created synthetic data model. In some embodiments, the performance criteria can include a similarity metric (e.g., a statistical correlation score, data similarity score, or data quality score, as described herein). For example, model optimizer 1303 can be configured to compare the covariances or univariate distributions of a synthetic dataset generated by the new synthetic data model and a reference data stream dataset. Likewise, model optimizer 1303 can be configured to evaluate the number of matching or similar elements in the synthetic dataset and reference data stream dataset. Furthermore, model optimizer 1303 can be configured to evaluate a number of duplicate elements in each of the synthetic dataset and reference data stream dataset, a prevalence of the most common value in synthetic dataset and reference data stream dataset, a maximum difference of rare values in each of the synthetic dataset and reference data stream dataset, differences in schema between the synthetic dataset and reference data stream dataset, and the like.
In various embodiments, the performance criteria can include prediction metrics. The prediction metrics can enable a user to determine whether data models perform similarly for both synthetic and actual data. The prediction metrics can include a prediction accuracy check, a prediction accuracy cross check, a regression check, a regression cross check, and a principal component analysis check. In some aspects, a prediction accuracy check can determine the accuracy of predictions made by a model (e.g., recurrent neural network, kernel density estimator, or the like) given a dataset. For example, the prediction accuracy check can receive an indication of the model, a set of data, and a set of corresponding labels. The prediction accuracy check can return an accuracy of the model in predicting the labels given the data. Similar model performance for the synthetic and original data can indicate that the synthetic data preserves the latent feature structure of the original data. In various aspects, a prediction accuracy cross check can calculate the accuracy of a predictive model that is trained on synthetic data and tested on the original data used to generate the synthetic data. In some aspects, a regression check can regress a numerical column in a dataset against other columns in the dataset, determining the predictability of the numerical column given the other columns. In some aspects, a regression error cross check can determine a regression formula for a numerical column of the synthetic data and then evaluate the predictive ability of the regression formula for the numerical column of the actual data. In various aspects, a principal component analysis check can determine a number of principal component analysis columns sufficient to capture a predetermined amount of the variance in the dataset. Similar numbers of principal component analysis columns can indicate that the synthetic data preserves the latent feature structure of the original data.
Model optimizer 1303 can be configured to store the newly created synthetic data model and metadata for the new synthetic data model in model storage 1305 based on the evaluated performance criteria, consistent with disclosed embodiments. For example, model optimizer 1303 can be configured to store the metadata and new data model in model storage when a value of a similarity metric or a prediction metric satisfies a predetermined threshold. In some embodiments, the metadata can include at least one value of a similarity metric or prediction metric. In various embodiments, the metadata can include an indication of the origin of the new synthetic data model, the data used to generate the new synthetic data model, when the new synthetic data model was generated, and the like.
System 1300 can be configured to generate synthetic data using a current data model. In some embodiments, this generation can occur while system 1300 is training a new synthetic data model. Model optimizer 1303, model storage 1305, dataset generator 1307, and synthetic data source 1309 can interact to generate the synthetic data, consistent with disclosed embodiments.
Model optimizer 1303 can be configured to receive a request for a synthetic data stream from an interface (e.g., interface 113 or the like). In some aspects, model optimizer 1307 can resemble model optimizer 107, described above with regard to FIG. 1. For example, model optimizer 1307 can provide similar functionality and can be similarly implemented. In some aspects, requests received from the interface can indicate a reference data stream. For example, such a request can identify streaming data source 1301 and/or specify a topic or subject (e.g., a Kafka topic or the like). In response to the request, model optimizer 1307 (or another component of system 1300) can be configured to direct generation of a synthetic data stream that tracks the reference data stream, consistent with disclosed embodiments.
Dataset generator 1307 can be configured to retrieve a current data model of the reference data stream from model storage 1305. In some embodiments, dataset generator 1307 can resemble dataset generator 103, described above with regard to FIG. 1. For example, dataset generator 1307 can provide similar functionality and can be similarly implemented. Likewise, in some embodiments, model storage 1305 can resemble model storage 105, described above with regard to FIG. 1. For example, model storage 1305 can provide similar functionality and can be similarly implemented. In some embodiments, the current data model can resemble data received from streaming data source 1301 according to a similarity metric (e.g., a statistical correlation score, data similarity score, or data quality score, as described herein). In various embodiments, the current data model can resemble data received during a time interval extending to the present (e.g. the present hour, the present day, the present week, or the like). In various embodiments, the current data model can resemble data received during a prior time interval (e.g. the previous hour, yesterday, last week, or the like). In some embodiments, the current data model can be the most recently trained data model of the reference data stream.
Dataset generator 1307 can be configured to generate a synthetic data stream using the current data model of the reference data steam. In some embodiments, dataset generator 1307 can be configured to generate the synthetic data stream by replacing sensitive portions of the reference data steam with synthetic data, as described in FIGS. 5A and 5B. In various embodiments, dataset generator 1307 can be configured to generate the synthetic data stream without reference to the reference data steam data. For example, when the current data model is a recurrent neural network, dataset generator 1307 can be configured to initialize the recurrent neural network with a value string (e.g., a random sequence of characters), predict a new value based on the value string, and then add the new value to the end of the value string. Dataset generator 1307 can then predict the next value using the updated value string that includes the new value. In some embodiments, rather than selecting the most likely new value, dataset generator 1307 can be configured to probabilistically choose a new value. As a nonlimiting example, when the existing value string is “examin” the dataset generator 1307 can be configured to select the next value as “e” with a first probability and select the next value as “a” with a second probability. As an additional example, when the current data model is a generative adversarial network or an adversarially learned inference network, dataset generator 1307 can be configured to generate the synthetic data by selecting samples from a code space, as described herein.
In some embodiments, dataset generator 1307 can be configured to generate an amount of synthetic data equal to the amount of actual data retrieved from synthetic data stream 1309. In some aspects, the rate of synthetic data generation can match the rate of actual data generation. As a nonlimiting example, when streamlining data source 1301 retrieves a batch of 10 samples of actual data, dataset generator 1307 can be configured to generate a batch of 10 samples of synthetic data. As a further nonlimiting example, when streamlining data source 1301 retrieves a batch of actual data every 10 minutes, dataset generator 1307 can be configured to generate a batch of actual data every 10 minutes. In this manner, system 1300 can be configured to generate synthetic data similar in both content and temporal characteristics to the reference data stream data.
In various embodiments, dataset generator 1307 can be configured to provide synthetic data generated using the current data model to synthetic data source 1309. In some embodiments, synthetic data source 1309 can be configured to provide the synthetic data received from dataset generator 1307 to a database, a file, a datasource, a topic in a data streaming platform (e.g., IBM STREAMS), a topic in a distributed messaging system (e.g., APACHE KAFKA), or the like.
As discussed above, system 1300 can be configured to track the reference data stream by repeatedly switching data models of the reference data stream. In some embodiments, dataset generator 1307 can be configured to switch between synthetic data models at a predetermined time, or upon expiration of a time interval. For example, model optimizer 1307 can be configured to switch from an old model to a current model every hour, day, week, or the like. In various embodiments, system 1300 can detect when a data schema of the reference data stream changes and switch to a current data model configured to provide synthetic data with the current schema. Consistent with disclosed embodiments, switching between synthetic data models can include dataset generator 1307 retrieving a current model from model storage 1305 and computing resources 1304 providing a new synthetic data model for storage in model storage 1305. In some aspects, computing resources 1304 can update the current synthetic data model with the new synthetic data model and then dataset generator 1307 can retrieve the updated current synthetic data model. In various aspects, dataset generator 1307 can retrieve the current synthetic data model and then computing resources 1304 can update the current synthetic data model with the new synthetic data model. In some embodiments, model optimizer 1303 can provision computing resources 1304 with a synthetic data model for training using a new set of training data. In various embodiments, computing resources 1304 can be configured to continue updating the new synthetic data model. In this manner, a repeat of the switching process can include generation of a new synthetic data model and the replacement of a current synthetic data model by this new synthetic data model.
FIG. 14 depicts a process 1400 for generating synthetic JSON log data using the cloud computing system of FIG. 13. Process 1400 can include the steps of retrieving reference JSON log data, training a recurrent neural network to generate synthetic data resembling the reference JSON log data, generating the synthetic JSON log data using the recurrent neural network, and validating the synthetic JSON log data. In this manner system 1300 can use process 1400 to generate synthetic JSON log data that resembles actual JSON log data.
After starting, process 1400 can proceed to step 1401. In step 1401, substantially as described above with regard to FIG. 13, streaming data source 1301 can be configured to retrieve the JSON log data from a database, a file, a datasource, a topic in a distributed messaging system such Apache Kafka, or the like. The JSON log data can be retrieved in response to a request from model optimizer 1303. The JSON log data can be retrieved in real-time, or periodically (e.g., approximately every five minutes).
Process 1400 can then proceed to step 1403. In step 1403, substantially as described above with regard to FIG. 13, computing resources 1304 can be configured to train a recurrent neural network using the received data. The training of the recurrent neural network can proceed as described in “Training Recurrent Neural Networks,” 2013, by Ilya Sutskever, which is incorporated herein by reference in its entirety.
Process 1400 can then proceed to step 1405. In step 1405, substantially as described above with regards to FIG. 13, dataset generator 1307 can be configured to generate synthetic JSON log data using the trained neural network. In some embodiments, dataset generator 1307 can be configured to generate the synthetic JSON log data at the same rate as actual JSON log data is received by streaming data source 1301. For example, dataset generator 1307 can be configured to generate batches of JSON log data at regular time intervals, the number of elements in a batch dependent on the number of elements received by streaming data source 1301. As an additional example, dataset generator 1307 can be configured to generate an element of synthetic JSON log data upon receipt of an element of actual JSON log data from streaming data source 1301.
Process 1400 can then proceed to step 1407. In step 1407, dataset generator 1307 (or another component of system 1300) can be configured to validate the synthetic data stream. For example, dataset generator 1307 can be configured to use a JSON validator (e.g., JSON SCHEMA VALIDATOR, JSONLINT, or the like) and a schema for the reference data stream to validate the synthetic data stream. In some embodiments, the schema describes key-value pairs present in the reference data stream. In some aspects, system 1300 can be configured to derive the schema from the reference data stream. In some embodiments, validating the synthetic data stream can include validating that keys present in the synthetic data stream are present in the schema. For example, when the schema includes the keys “first_name”: {“type”: “string”} and “last_name”: {“type”: “string”}, system 1300 may not validate the synthetic data stream when objects in the data stream lack the “first_name” and “last_name” keys. Furthermore, in some embodiments, validating the synthetic data stream can include validating that key-value formats present in the synthetic data stream match corresponding key-value formats in the reference data stream. For example, when the schema includes the keys “first_name”: {“type”: “string”} and “last_name”: {“type”: “string”}, system 1300 may not validate the synthetic data stream when objects in the data stream include a numeric-valued “first_name” or “last_name”.
FIG. 15 depicts a system 1500 for secure generation and insecure use of models of sensitive data. System 1500 can include a remote system 1501 and a local system 1503 that communicate using network 1505. Remote system 1501 can be substantially similar to system 100 and be implemented, in some embodiments, as described in FIG. 4. For example, remote system 1501 can include an interface, model optimizer, and computing resources that resemble interface 113, model optimizer 107, and computing resources 101, respectively, described above with regards to FIG. 1. For example, the interface, model optimizer, and computing resources can provide similar functionality to interface 113, model optimizer 107, and computing resources 101, respectively, and can be similarly implemented. In some embodiments, remote system 1501 can be implemented using a cloud computing infrastructure. Local system 1503 can comprise a computing device, such as a smartphone, tablet, laptop, desktop, workstation, server, or the like. Network 1505 can include any combination of electronics communications networks enabling communication between components of system 1500 (similar to network 115).
In various embodiments, remote system 1501 can be more secure than local system 1503. For example, remote system 1501 can better protected from physical theft or computer intrusion than local system 1503. As a non-limiting example, remote system 1501 can be implemented using AWS or a private cloud of an institution and managed at an institutional level, while the local system can be in the possession of, and managed by, an individual user. In some embodiments, remote system 1501 can be configured to comply with policies or regulations governing the storage, transmission, and disclosure of customer financial information, patient healthcare records, or similar sensitive information. In contrast, local system 1503 may not be configured to comply with such regulations.
System 1500 can be configured to perform a process of generating synthetic data. According to this process, system 1500 can train the synthetic data model on sensitive data using remote system 1501, in compliance with regulations governing the storage, transmission, and disclosure of sensitive information. System 1500 can then transmit the synthetic data model to local system 1503, which can be configured to use the system to generate synthetic data locally. In this manner, local system 1503 can be configured to use synthetic data resembling the sensitive information, which comply with policies or regulations governing the storage, transmission, and disclosure of such information.
According to this process, the model optimizer can receive a data model generation request from the interface. In response to the request, the model optimizer can provision computing resources with a synthetic data model. The computing resources can train the synthetic data model using a sensitive dataset (e.g., consumer financial information, patient healthcare information, or the like). The model optimizer can be configured to evaluate performance criteria of the data model (e.g., the similarity metric and prediction metrics described herein, or the like). Based on the evaluation of the performance criteria of the synthetic data model, the model optimizer can be configured to store the trained data model and metadata of the data model (e.g., values of the similarity metric and prediction metrics, of the data, the origin of the new synthetic data model, the data used to generate the new synthetic data model, when the new synthetic data model was generated, and the like). For example, the model optimizer can determine that the synthetic data model satisfied predetermined acceptability criteria based on one or more similarity and/or prediction metric value.
Local system 1503 can then retrieve the synthetic data model from remote system 1501. In some embodiments, local system 1503 can be configured to retrieve the synthetic data model in response to a synthetic data generation request received by local system 1503. For example, a user can interact with local system 1503 to request generation of synthetic data. In some embodiments, the synthetic data generation request can specify metadata criteria for selecting the synthetic data model. Local system 1503 can interact with remote system 1501 to select the synthetic data model based on the metadata criteria. Local system 1503 can then generate the synthetic data using the data model in response to the data generation request.
FIG. 16 depicts a process 1600 for transforming any model into a neural network model, consistent with disclosed embodiments.
Process 1600 is performed by components of system 100, including computing resources 101, dataset generator 103, database 105, model optimizer 107, model storage 109, model curator 111, and interface 113, consistent with disclosed embodiments. In some embodiments, process 1600 is performed by components of system 400, an exemplary implementation of system 100. For example, steps of process 1600 may be performed by model optimizer 107 as implemented on model optimization instance 409.
As shown in FIG. 16, at step 1602, input data is received. In some embodiments, input is received at, for example, model optimizer 107 from one or more components of system 100. In some embodiments, input is received from a system outside system 100 via interface 113.
The input data of step 1602 includes an input command, an input model having an input model type and an input dataset. The input model may be any type of data model (e.g., a random forest model, a gradient boosting machine, a regression model, a logistic regression, an object based logical model, a physical data model, a neural network model, or any other data model). The input command includes a command to transform the input model into a neural network model. In some embodiments, the input command specifies one or more neural network types (e.g., neural network, recurrent neural network, generative adversarial network, or the like). In some embodiments, the input command specifies one or more model parameters for the one or more types of neural networks (e.g., the number of features and number of layers in a recurrent neural network). In some embodiments, the input command specifies model selection criteria. The model selection criteria may comprise a desired performance metric of the transformed model. The performance metric may be an accuracy score of the neural network model, a model run time, a root-mean-square error estimate (RMSE), a logloss, an Akaike's Information Criterion (AICC), a Bayesian Information Criterion (BIC), an area under a receiver operating characteristic (ROC) curve, Precision, Recall, an F-Score, or the like. In some embodiments, the input dataset is a dataset previously used to train the input model. In some embodiments, the input command specifies the location of a database, and receiving the input database includes retrieving an input dataset from the database.
At step 1604, the input model is applied to the input dataset to generate model output. In some embodiments, model optimizer 107 applies the input model, consistent with the embodiments. That is, computing resources are provisioned to run the model over the input dataset. In some embodiments, step 1604 includes spinning up a virtual machine or ephemeral container instance to run the input model (e.g., development instance 407). In some embodiments, step 1604 includes generating a map of input model features. The map may include references that relate output data to input data (e.g., a foreign key to the input data). For example, if the input dataset comprises rows and columns of data, the map may identify a correspondence between input data values in rows numbering row A to row Z and a set of 26 model output data values that the model produced based on input data values in rows A to Z. Model features may include input values from the input data set or transformed input data values used to run the model prior to step 1604 (e.g., via normalizing, averaging, or other transformations). In some embodiments, generating model output includes transforming the input values into transformed values, and running the input model over the transformed values.
At step 1606, model output is stored. In some embodiments, storing model output includes one of (a) storing model output along with a map of input model features or (b) storing model output along with model features. Model output may include a modeling result, a log, or other model output. Model output may be stored in a database or cloud computing bucket. For example, model output may be stored in database 105.
At step 1608, one or more candidate neural network models are generated. In some embodiments, model optimizer 107 generates candidate neural network models, consistent with the embodiments. Generating a candidate network model may include spinning up an ephemeral container instance (e.g., development instance 407). In some embodiments, the number and type of candidate neural network models are based on the command received at step 1602. In some embodiments, the number and type of candidate neural network models are pre-determined. In some embodiments, generating candidate neural network models includes retrieving a candidate neural network model from a model storage. For example, candidate neural network models may be retrieved from model storage 109. Retrieving candidate neural network models may be based on a model index.
The one or more candidate neural network models of step 1608 have model parameters which are based on the features of the input model such that the one or more candidate neural network models are overfitted to the input model. For example, if the input model is a linear regression model having a set of regression coefficients, each coefficient producing a result, then a candidate neural network may be designed to reproduce the result of each regression coefficient and the overall regression result of the input model. The model parameters of the one or more candidate neural network models may include, for example, the number of hidden layers, the number of nodes, the dropout rate, or other model parameters.
At step 1610, the candidate neural network models are tuned to the input model, consistent with disclosed embodiments. In some embodiments, model optimizer 107 tunes the candidate neural network models, consistent with the embodiments. Tuning includes, for example, adjusting a number of hidden layers, a number of inputs, or a type of layer for any of the one or more candidate neural network models. Tuning includes training a candidate model to reproduce features of the input model, consistent with disclosed embodiments. In some embodiments, tuning a candidate model includes iteratively performing operations to: select model training parameters; receive candidate model results; update the model training parameters based on the received candidate model results; and receive updated candidate model results based on the updated model training parameters. Model training parameters may include, for example, batch size, number of training batches, number of epochs, chunk size, time window, input noise dimension, or the like, consistent with disclosed embodiments. Training may terminate when a training condition is satisfied. For example, training may terminate at a pre-determined run time, after a pre-determined number of epochs, or based on an accuracy score of a candidate model. In some embodiments, different candidate models are trained using separate ephemeral container instances (e.g., development instance 407).
At step 1612, model output is received from the candidate neural network models. The candidate model output may include an overall accuracy score of a candidate model and a plurality of accuracy scores corresponding to the features of the input model. Model output at step 1612 may include a log file, a run time, a number of epochs, an error, an estimate of drift, or other model-run information. Model output may specify a model parameter, consistent with disclosed embodiments. In some embodiments, model optimizer 107 receives model output from, for example, resources provisioned to run the candidate neural network models, including an ephemeral container instance, consistent with the embodiments.
At step 1614, a candidate neural network model is selected based on one or more selection criteria. In some embodiments, model optimizer 107 selects the candidate neural network model, consistent with the embodiments. In some embodiments, the one or more selection criteria are the selection criteria received in the input command (step 1602). In some embodiments, the one or more selection criteria is predetermined. The model selection criteria may comprise a desired performance metric of the transformed model (e.g., an accuracy score of the neural network model, a model run time, a root-mean-square error estimate (RMSE), a logloss, an Akaike's Information Criterion (AICC), a Bayesian Information Criterion (BIC), an area under a receiver operating characteristic (ROC) curve, Precision, Recall, an F-Score, or the like). In some embodiments, selecting a candidate neural network model at step 1614 includes terminating processes relating to candidate neural network models that are not selected. For example, step 1614 may include spinning down or terminating container instances (e.g., development instances 407) running candidate neural network models that are not selected.
At step 1616, the selected neural network model is returned. In some embodiments, returning the selected neural network model includes transmitting, from model optimizer 107, the selected neural network model to an outside system via interface 113. In some embodiments, returning the selected neural network model includes storing the selected neural network model. For example, the step 1616 may include storing the selected neural network in a database or a bucket (e.g., database 105).
FIG. 17 depicts a process 1700 for transforming a legacy model, consistent with disclosed embodiments.
Process 1700 is performed by components of system 100, including computing resources 101, dataset generator 103, database 105, model optimizer 107, model storage 109, model curator 111, and interface 113, consistent with disclosed embodiments. In some embodiments, process 1600 is performed by components of system 400, an exemplary implementation of system 100. For example, steps of process 1700 may be performed by model optimizer 107 as implemented on model optimization instance 409.
As shown in FIG. 17, at step 1702, inputs are received. In some embodiments, inputs are received by optimizer 107 from interface 113, consistent with the embodiments. The input includes may include a model of any model type, e.g., the legacy model, and a command to transform a legacy model into a new model of the same model type as the legacy model, the new model having a different programming environment than the legacy model programming environment. For example, the command may be to transform a linear regression model built in SAS to a linear regression model built in PYTHON. In some embodiments, the legacy model and the new model share the same programming environment but use different code packages. For example, the legacy model may be a Gradient Boosting Machine built with SCIKIT LEARN (using PYTHON libraries) and the new model may be a Gradient Boosting Machine built with XGBOOST (also using PYTHON libraries). Step 1702 may include receiving metadata of the legacy model. Metadata may include arguments used by the model. For example, in some embodiments, the legacy model is a random forest and metadata includes a number of trees, a depth of trees, a min sample split.
In some embodiments, receiving input at step 1702 includes sub-steps to receive a model of any type, receive a dataset, and apply the model to the received dataset (e.g., steps 1602-1606). In some embodiments, model data is received from an API call via, for example, interface 113.
At step 1704, a determination is made whether model metadata is present, i.e., whether model metadata was received at step 1702, and the system proceeds to either step 1706 or step 1708 based on the determination. In some embodiments, model optimizer 107 may perform the determination of step 1704.
Step 1705 may be performed if model metadata was received at step 1702. At step 1705, a feature map is received. The feature map may include instructions to transform features of one programming environment into another programing environment (or from one package into another package). For example, using metadata, model optimizer 107 may identify features of the legacy model programming environment. In some aspects, legacy model features may map directly onto the new model programing environment. As an illustrative example, if the legacy model is a random forest models in SCIKIT-LEARN and the new model is a random forest model in XGBOOST, arguments using different syntax in both models may specify the number of trees, depth of trees, and/or min sample split, and the feature map may include instructions to transform these arguments from SCIKIT-LEARN to XGBOOST.
At step 1706, one or more candidate new models are generated with parameters that are based on the feature map Machine learning is used to optimize parameters not specified by the metadata. In some embodiments, model optimizer 107 may generate the candidate new models. In some embodiments, model optimizer 107 may spin up one or more ephemeral container instances (e.g., development instance 407) to generate a candidate new model.
Step 1708 may be performed if metadata was not received at step 1702. At step 1708, a global grid search over new model parameters may be performed to generate one or more candidate new models that approximates the model output of the legacy model. The global grid search of step 1708 may be a broad (unrefined) parameter search. For example, if the legacy model is a random forest model, the global grid search may comprise obtaining a model performance metric for each of a series of candidate random forest models that vary by the number of trees ranging from 0 to 10 with a step size of 2; the depth of trees ranging from 0 to 20 with a step size of 5; and/or a min sample split ranging from 0 to 1 with a step size of 0.1. A subset of candidate new models may be identified at step 1708 based on a model performance metric, consistent with disclosed embodiments. In some embodiments, model optimizer 107 performs the closed-loop grid search. In some embodiments, model optimizer 107 spins up one or more ephemeral container instances or identifies one or more running container instance to perform the global grid search (e.g., development instance 407).
At step 1710, a closed-loop (refined) grid search may be performed over the parameters to fit one or more candidate new models (of either step 1706 or step 1708) to the legacy model. In some embodiments, the closed-loop grid search may include a grid search over parameters near to the parameters of the received as input at step 1702, i.e. the parameters of the input model serves as a seed for the closed-loop grid search. In some embodiments, the close-loop grid search may include a grid search over parameters near the parameters of the subset of candidate new models identified at step 1708. For example, the range and step size of the closed-loop grid search may be smaller than the range and step size of parameters in used in the global grid search. In some embodiments, model optimizer 107 performs the closed-loop grid search. In some embodiments, model optimizer 107 spins up one or more ephemeral container instances or identifies one or more running container instance to perform the closed-loop grid search (e.g., development instance 407).
At step 1712, candidate new models may be applied to the input dataset and the results are compared to the legacy model output. In some embodiments, the comparison may include at least one of an accuracy score, a model run time, a root-mean-square error estimate (RMSE), a logloss, an AICC, a BIC, an area under an ROC curve, Precision, Recall, an F-Score, or the like. In some embodiments, model optimizer 107 may perform step 1712.
At step 1714, a candidate new model may be selected based on the comparison at step 1712 and one or more selection criteria. In some embodiments, model optimizer 107 may select the new candidate model.
At step 1716, an updated feature map may be created, consistent with disclosed embodiments. In some embodiments, the updated feature map may be based on one or more of the legacy model, the feature map received at step 1705, and the selected new model. In some embodiments, the updated feature map may be newly generated based on legacy model and the selected new model. The feature map may include instructions to transform features of one programming environment into another programing environment (or from one package into another package).
At step 1718, the selected new model may be returned. In some embodiments, returning the selected neural network model may include transmitting, by model optimizer 107, the selected neural network model to an outside system via interface 113. In some embodiments, returning the selected neural network model includes storing the selected neural network model. For example, step 1718 may include storing the selected neural network in a database or a bucket (e.g., database 105). In some embodiments, step 1718 may include at least one of returning the updated feature map with the selected new model or storing the updated feature map in memory (e.g., model storage 109).

EXAMPLE

Generating Cancer Data

As described above, the disclosed systems and methods can enable generation of synthetic data similar to an actual dataset (e.g., using dataset generator 103). The synthetic data can be generated using a data model trained on the actual dataset (e.g., as described above with regards to FIG. 9). Such data models can include generative adversarial networks. The following code depicts the creation a synthetic dataset based on sensitive patient healthcare records using a generative adversarial network.
The following step defines a Generative Adversarial Network data model.
model_options={‘GANhDim’: 498, ‘GANZDim’: 20, ‘num_epochs’: 3}
The following step defines the delimiters present in the actual data
data_options={‘delimiter’: ‘,’}
In this example, the dataset is the publicly available University of Wisconsin Cancer dataset, a standard dataset used to benchmark machine learning prediction tasks. Given characteristics of a tumor, the task to predict whether the tumor is malignant.
data=Data(input_file_path=‘wisconsin_cancer_train.csv’, options=data_options)
In these steps the GAN model is trained generate data statistically similar to the actual data.
ss=SimpleSilo(‘GAN’, model_options)
ss.train(data)
The GAN model can now be used to generate synthetic data.
generated_data=ss.generate(num_output_samples=5000)
The synthetic data can be saved to a file for later use in training other machine learning models for this prediction task without relying on the original data.
simplesilo.save_as_csv(generated_data, output_file_path=‘wisconsin_cancer_GAN.csv’)
ss.save_model_into_file(‘cancer_data_model’)
Tokenizing Sensitive Data
As described above with regards to at least FIGS. 5A and 5B, the disclosed systems and methods can enable identification and removal of sensitive data portions in a dataset. In this example, sensitive portions of a dataset are automatically detected and replaced with synthetic data. In this example, the dataset includes human resources records. The sensitive portions of the dataset are replaced with random values (though they could also be replaced with synthetic data that is statistically similar to the original data as described in FIGS. 5A and 5B). In particular, this example depicts tokenizing four columns of the dataset. In this example, the Business Unit and
Active Status columns are tokenized such that all the characters in the values can be replaced by random chars of the same type while preserving format. For the column of Employee number, the first three characters of the values can be preserved but the remainder of each employee number can be tokenized. Finally, the values of the Last Day of Work column can be replaced with fully random values. All of these replacements can be consistent across the columns.
input_data=Data(‘hr_data.csv’)
keys_for_formatted scrub={‘Business Unit’:None, ‘Active Status’: None, ‘Company’: (0,3)}
keys_to_randomize=[‘Last Day of Work’]
tokenized_data, scrub_map=input_data.tokenize(keys_for_formatted_scrub=keys_for_formatted scrub, keys_to_randomize=keys_to_randomize) tokenized_data.save_data_into_file(‘hr_data_tokenized.csv’)
Alternatively, the system can use the scrub map to tokenize another file in a consistent way (e.g., replace the same values with the same replacements across both files) by passing the returned scrub_map dictionary to a new application of the scrub function.
input_data_2=Data(‘hr_data_part2.csv’)
keys_for_formatted_scrub={‘Business Unit’:None, ‘Company’: (0,3)}
keys_to_randomize=[‘Last Day of Work’]
to tokenize the second file, we pass the scrub_map diction to tokenize function.
tokenized_data_2, scrub_map=input_data_2.tokenize(keys_for_formatted_scrub=keys_for_formatted scrub, keys_to_randomize=keys_to_randomize, scrub_map=scrub_map)
tokenized_data_2.save_data_into_file(‘hr_data_tokenized_2.csv’)
In this manner, the disclosed systems and methods can be used to consistently tokenize sensitive portions of a file.
Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosed embodiments being indicated by the following claims. Furthermore, although aspects of the disclosed embodiments are described as being associated with data stored in memory and other tangible computer-readable storage mediums, one skilled in the art will appreciate that these aspects can also be stored on and executed from many types of tangible computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, or other forms of RAM or ROM. Accordingly, the disclosed embodiments are not limited to the above-described examples, but instead are defined by the appended claims in light of their full scope of equivalents.
Moreover, while illustrative embodiments have been described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations or alterations based on the present disclosure. The elements in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering steps or inserting or deleting steps. It is intended, therefore, that the specification and examples be considered as example only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.

Claims

1-20. (canceled)

21. A system for transforming an input model into a neural network model, the system comprising:

one or more memory units for storing instructions; and

one or more processors configured to execute the instructions to perform operations comprising:

receiving input data comprising the input model;

obtaining dataset model output by applying the input model to an input dataset;

storing the generated dataset model output and at least one of:

input model features; or a map of the input model features;

generating a plurality of candidate neural network models based on the input model features;

tuning the plurality of candidate neural network models by adjusting at least one of a plurality of hidden layers, a plurality of inputs, or a type of layer during tuning such that at least one of the input model features is reproduced;

selecting a neural network model from the plurality of candidate neural network models based on one or more model selection criteria; and

returning the selected neural network model.

22. The system of claim 21, wherein the input model comprises a regression model.

23. The system of claim 21, wherein the input dataset comprises synthetic data being a representation of original data.

24. The system of claim 21, wherein obtaining the dataset model output comprises:

sending a command to a development instance to apply the input model to the input dataset; and

obtaining the dataset model output from the development instance.

25. The system of claim 24, wherein the development instance comprises a virtual machine or an ephemeral container instance.

26. The system of claim 21, wherein generating the plurality of candidate neural network models comprises sending a command to a development instance to generate the plurality of candidate neural network models based on the input model features or the map of the input model features.

27. The system of claim 26, wherein the development instance comprises a virtual machine or an ephemeral container instance.

28. The system of claim 26, wherein:

the command specifies one or more model parameters; and

generating the plurality of neural network models comprises generating at least one of the plurality of neural network models based on the one or more model parameters.

29. The system of claim 26, wherein:

the command specifies a model type; and

generating the plurality of candidate neural network models comprises generating at least one candidate neural network model of the specified model type.

30. The system of claim 29, wherein:

the command further specifies a number of candidate neural network models of the specified model type; and

generating the plurality of candidate neural network models comprises generating the specified number of candidate neural network models of the specified type.

31. The system of claim 21, wherein generating the plurality of candidate neural network models comprises retrieving at least one candidate neural network model from a model storage.

32. The system of claim 21, wherein generating the plurality of candidate neural network models comprises overfitting at least one of the plurality of candidate neural network models to the input model.

33. The system of claim 21, wherein tuning the plurality of candidate neural network models comprises:

training at least one of the plurality of candidate neural network models; and

terminating the training when one or more training conditions are satisfied.

34. The system of claim 33, wherein the one or more training conditions comprise at least one of a run time, a number of epochs, or an accuracy score.

35. The system of claim 33, wherein training the at least one of the plurality of candidate neural network models comprises:

sending a first command to a first development instance to train a first candidate neural network model; and

sending a second command to a second development instance different from the first development instance to train a second candidate neural network model.

36. The system of claim 21, wherein the one or more model selection criteria comprise a selection criterium associated with an accuracy score of a candidate neural network model with respect to the input model features.

37. The system of claim 21, wherein the one or more model selection criteria comprise a selection criterium associated with a model run time of a candidate neural network model.

38. The system of claim 21, wherein generating the plurality of candidate neural network models comprises:

sending a first command to a first development instance to generate a first candidate neural network model; and

sending a second command to a second development instance different from the first development instance to generate a second candidate neural network model.

39. A method for transforming an input model into a neural network model, the method comprising:

obtaining dataset model output by applying an input model to an input dataset, the input model having a plurality of input model features;

returning the selected neural network model.

40. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, are configured to cause the at least one processor to perform operations comprising:

selecting a neural network model from the plurality of candidate neural network models based on one or more model selection criteria, a model type of the selected neural network model being different from a model type of the input model; and

returning the selected neural network model.