In the Core Engine, you are a part of an organization and it is possible for your organization to be working on numerous tasks or projects at the same time. Moreover, as a user, you might be participating in multiple projects simultaneously. The concept of workspaces is created to maintain an organized and efficient structure within the ML workflow of your organization.
For the beta, the notion of an organization is slightly abstracted from the CLI. Every user implictly belongs to one organization.
What is it for?
Through a workspace, developers can:
- Gather all their solutions about a problem under one roof
- Collaborate on the same problem by sharing their experiments and solutions
Relation to pipelines
One workspace can have many pipelines. In addition, all pipelines within the same workspace:
- Utilize a shared metadata store, which tracks all the executed steps within the workspace
- Make use of the shared metadata store to skip previously executed processes for efficiency and to trace the results
- Can be compared against each other with the pipeline
It is important to note that for most intents and purposes, pipelines within the same workspace should probably share the same datasource to be comparable across runs. However, you are free to use as many datasources as you want.
In order to see the available workspaces within your organization:
In order to create a new workspace:
|name||str||the name of the workspace|
In order to make a workspace active:
|<workspace_id>||int||the id of the selected workspace|
For now, each user can only create 5 workspaces maximum. Please contact us at email@example.com to lift these pesky limitations!