You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: Carme can generate synthetic data in a controlled environment. However, there will be an unwillingness to transport that data out of the controlled environment because it cannot be clearly and easily differentiated from the real data by a 3rd party. There is a need to be able to transport out a light-weight configuration file which could be used outside of the environment to generate the data.
Inside secure environment. The user has access to the actual data and runs a command with option to generate only the configuration file (recommend a .yaml file). The .yaml file contains everything needed to generate the data outside of the secure environment. The .yaml file is passed on to inspection and transferred to the consultant outside of the secure environment.
Outside the secure environment. The user generates the sample data using the .yaml file and works on the problem.
The text was updated successfully, but these errors were encountered:
Problem: Carme can generate synthetic data in a controlled environment. However, there will be an unwillingness to transport that data out of the controlled environment because it cannot be clearly and easily differentiated from the real data by a 3rd party. There is a need to be able to transport out a light-weight configuration file which could be used outside of the environment to generate the data.
Inside secure environment. The user has access to the actual data and runs a command with option to generate only the configuration file (recommend a .yaml file). The .yaml file contains everything needed to generate the data outside of the secure environment. The .yaml file is passed on to inspection and transferred to the consultant outside of the secure environment.
Outside the secure environment. The user generates the sample data using the .yaml file and works on the problem.
The text was updated successfully, but these errors were encountered: