From 168a29012abc743ad3c6ea876993f53721f7398a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emre=20=C5=9Eahin?= Date: Mon, 15 Feb 2021 11:26:10 +0300 Subject: [PATCH 01/14] Added basic concepts: workspace document. --- .../user-guide/basic-concepts/workspace.md | 43 +++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index bfdf0044ad..42f96b1fb5 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -6,3 +6,46 @@ tooltip: >- models, etc. Typically, it's also a Git repository. It will contain your DVC project. --- + + + +# Workspace + +A data science project consists of data obtained from many different sources. +Most of the time it needs to convert the the format of this data into a form +that is required by the training models and supplying to data science / machine +learning workflows. Sometimes it needs to be split into multiple files or +directories or (as the project structure needs) have different versions for +different requirements. e.g. A smaller / simplified version might be required in +protoyping for faster feedback and shorter training times. + +These activities all involve to change the machine learning / data science +project structure in unforeseeable ways and tracking them manually becomes +tedious. A single workspace to manage all artifacts of a project is desirable, +although versioning needs and managing dependencies make it increasingly +complex. + +DVC allows a single directory to contain all your project artifacts. In the +documentation the workspace is the _user visible_ part of the directory that +contains all your project files e.g. raw datasets, source code, ML models, etc. +Users work in this directory using their data and model files that and +manipulate the contents through DVC commands. + +Files and directories in the workspace can be added to DVC (`dvc add`) or they +can be downloaded from external sources (`dvc get`, `dvc import`, +`dvc import-url`). Changes to the files, directories, notebooks, models and in +general machine learning file system can be tracked (`dvc commit`). +Pipelines and dependencies between them can be defined +(`dvc run`). Data and model files can be sent to or retrieved from +remotes (`dvc push`, `dvc pull`) and can be removed (`dvc remove`, +`dvc gc`) from the workspace. DVC supports all typical operations of files and +directories of a file sytem through its commands. + +Behind the scene these operations of a DVC project uses +metafiles to track the content and dependencies. + +## Further Reading + +- [What is DVC?](/doc/user-guide/what-is-dvc) +- [Versioning Data and Model](/doc/use-cases/versioning-data-and-model-files) + from Use Cases From 3130952ac241733364e00785589867d3651cee45 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Emre=20=C5=9Eahin?= Date: Mon, 15 Feb 2021 11:29:12 +0300 Subject: [PATCH 02/14] added a basic concepts section to the sidebar and added workspace document to the links --- content/docs/sidebar.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/docs/sidebar.json b/content/docs/sidebar.json index e6fa86237d..89d8469284 100644 --- a/content/docs/sidebar.json +++ b/content/docs/sidebar.json @@ -91,6 +91,12 @@ "label": "What is DVC?", "slug": "what-is-dvc" }, + { + "label": "Basic Concepts", + "slug": "basic-concepts", + "source": false, + "children": ["workspace"] + }, { "slug": "project-structure", "source": "user-guide/project-structure/index.md", From d11972919a2591cd7d5a9eebef696a5b9bae5429 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Tue, 16 Feb 2021 19:39:40 +0300 Subject: [PATCH 03/14] fixed typos --- .../docs/user-guide/basic-concepts/workspace.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 42f96b1fb5..28db7456b7 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -12,12 +12,12 @@ tooltip: >- # Workspace A data science project consists of data obtained from many different sources. -Most of the time it needs to convert the the format of this data into a form -that is required by the training models and supplying to data science / machine -learning workflows. Sometimes it needs to be split into multiple files or -directories or (as the project structure needs) have different versions for -different requirements. e.g. A smaller / simplified version might be required in -protoyping for faster feedback and shorter training times. +Most of the time it needs to convert the format of this data into a form that is +required by the training models and supplying to data science / machine learning +workflows. Sometimes it needs to be split into multiple files or directories or +(as the project structure needs) have different versions for different +requirements. e.g. A smaller / simplified version might be required in +prototyping for faster feedback and shorter training times. These activities all involve to change the machine learning / data science project structure in unforeseeable ways and tracking them manually becomes @@ -39,7 +39,7 @@ general machine learning file system can be tracked (`dvc commit`). (`dvc run`). Data and model files can be sent to or retrieved from remotes (`dvc push`, `dvc pull`) and can be removed (`dvc remove`, `dvc gc`) from the workspace. DVC supports all typical operations of files and -directories of a file sytem through its commands. +directories of a file system through its commands. Behind the scene these operations of a DVC project uses metafiles to track the content and dependencies. From e0d915ef00fce1d92037202c1d5553944fc189d8 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Tue, 16 Feb 2021 19:58:14 +0300 Subject: [PATCH 04/14] Revised initial two paragraphs into a single one and abbr link for project --- .../user-guide/basic-concepts/workspace.md | 24 +++++++------------ 1 file changed, 9 insertions(+), 15 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 28db7456b7..b0ffd422ea 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -12,24 +12,18 @@ tooltip: >- # Workspace A data science project consists of data obtained from many different sources. -Most of the time it needs to convert the format of this data into a form that is -required by the training models and supplying to data science / machine learning -workflows. Sometimes it needs to be split into multiple files or directories or -(as the project structure needs) have different versions for different -requirements. e.g. A smaller / simplified version might be required in -prototyping for faster feedback and shorter training times. - -These activities all involve to change the machine learning / data science -project structure in unforeseeable ways and tracking them manually becomes -tedious. A single workspace to manage all artifacts of a project is desirable, -although versioning needs and managing dependencies make it increasingly -complex. +This data may be split into multiple files or directories or (as the project +structure needs) have different versions for different requirements. e.g. A +smaller / simplified version might be required in prototyping for faster +feedback and shorter training times. A single workspace to manage all artifacts +of a project is desirable, although versioning needs and managing dependencies +make it increasingly complex. DVC allows a single directory to contain all your project artifacts. In the documentation the workspace is the _user visible_ part of the directory that -contains all your project files e.g. raw datasets, source code, ML models, etc. -Users work in this directory using their data and model files that and -manipulate the contents through DVC commands. +contains all your project files e.g. raw datasets, source code, ML +models, etc. Users work in this directory using their data and model files that +and manipulate the contents through DVC commands. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, From bdbcc9765877c13f9bf8caa9289d89bc214f94e9 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Tue, 16 Feb 2021 20:21:11 +0300 Subject: [PATCH 05/14] modified the text to mention `checkout` and removed `run` and `gc` --- content/docs/user-guide/basic-concepts/workspace.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index b0ffd422ea..dc0e126949 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -28,12 +28,12 @@ and manipulate the contents through DVC commands. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, `dvc import-url`). Changes to the files, directories, notebooks, models and in -general machine learning file system can be tracked (`dvc commit`). -Pipelines and dependencies between them can be defined -(`dvc run`). Data and model files can be sent to or retrieved from -remotes (`dvc push`, `dvc pull`) and can be removed (`dvc remove`, -`dvc gc`) from the workspace. DVC supports all typical operations of files and -directories of a file system through its commands. +general machine learning file system can be tracked (`dvc commit`) and versioned +in Git (`dvc checkout`). Pipelines and dependencies +between them can be defined. Data and model files can be moved to the cloud +(`dvc remote`) and retrieved one by one when necessary (`dvc push`, `dvc pull`). +They can be removed (`dvc remove`) from the workspace. DVC supports all typical +operations of files and directories of a file system through its commands. Behind the scene these operations of a DVC project uses metafiles to track the content and dependencies. From 7f2e93d7100145dddcf89f1040d1a2e45ed8438b Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Thu, 18 Feb 2021 11:06:57 +0300 Subject: [PATCH 06/14] Removed listed keywords and some other minor modifications --- content/docs/user-guide/basic-concepts/workspace.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index dc0e126949..6d649157b3 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -7,8 +7,6 @@ tooltip: >- project. --- - - # Workspace A data science project consists of data obtained from many different sources. @@ -27,13 +25,12 @@ and manipulate the contents through DVC commands. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, -`dvc import-url`). Changes to the files, directories, notebooks, models and in +`dvc import-url`). Changes to the files, directories, notebooks, models, and in general machine learning file system can be tracked (`dvc commit`) and versioned -in Git (`dvc checkout`). Pipelines and dependencies -between them can be defined. Data and model files can be moved to the cloud -(`dvc remote`) and retrieved one by one when necessary (`dvc push`, `dvc pull`). -They can be removed (`dvc remove`) from the workspace. DVC supports all typical -operations of files and directories of a file system through its commands. +in Git (`dvc checkout`). They can be removed (`dvc remove`) from the workspace. Pipelines and dependencies between them can be +defined. Data and model files can be moved to the cloud and retrieved +when necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of +files and directories of a file system through its commands. Behind the scene these operations of a DVC project uses metafiles to track the content and dependencies. From 523f1c14dc2073e8af87965e88c3d711527a1905 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Thu, 18 Feb 2021 11:07:59 +0300 Subject: [PATCH 07/14] styled --- content/docs/user-guide/basic-concepts/workspace.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 6d649157b3..8f4db554b5 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -27,10 +27,11 @@ Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, `dvc import-url`). Changes to the files, directories, notebooks, models, and in general machine learning file system can be tracked (`dvc commit`) and versioned -in Git (`dvc checkout`). They can be removed (`dvc remove`) from the workspace. Pipelines and dependencies between them can be -defined. Data and model files can be moved to the cloud and retrieved -when necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of -files and directories of a file system through its commands. +in Git (`dvc checkout`). They can be removed (`dvc remove`) from the workspace. +Pipelines and dependencies between them can be +defined. Data and model files can be moved to the cloud and retrieved when +necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of files +and directories of a file system through its commands. Behind the scene these operations of a DVC project uses metafiles to track the content and dependencies. From 50964b104a867e31fc3f095539115d6f6beb5949 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Thu, 18 Feb 2021 11:47:15 +0300 Subject: [PATCH 08/14] Modified the definition for more clear sentence. --- content/docs/user-guide/basic-concepts/workspace.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 8f4db554b5..62ce7edd89 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -17,11 +17,11 @@ feedback and shorter training times. A single workspace to manage all artifacts of a project is desirable, although versioning needs and managing dependencies make it increasingly complex. -DVC allows a single directory to contain all your project artifacts. In the -documentation the workspace is the _user visible_ part of the directory that -contains all your project files e.g. raw datasets, source code, ML -models, etc. Users work in this directory using their data and model files that -and manipulate the contents through DVC commands. +DVC allows a single directory to contain all your project artifacts. The +workspace is the directory containing _user visible_ part of your +project e.g. raw datasets, source code, ML models, etc. Users work +in this directory using their data and model files that and manipulate the +contents through DVC commands. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, From 46fe4bba62b254644a704ae6e106905b28eb97d7 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Thu, 18 Feb 2021 11:57:26 +0300 Subject: [PATCH 09/14] Added dvc filenames to the last paragraph. --- content/docs/user-guide/basic-concepts/workspace.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 62ce7edd89..f79d8166c2 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -34,7 +34,8 @@ necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of files and directories of a file system through its commands. Behind the scene these operations of a DVC project uses -metafiles to track the content and dependencies. +metafiles like the `.dvc/` directory, `dvc.yaml` or files with +`*.dvc` extension to track the content and dependencies. ## Further Reading From 44af0a9f9d5633fa98a5c2d4a85a292e575381b5 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Mon, 22 Feb 2021 21:33:42 +0300 Subject: [PATCH 10/14] Modified the paragraph to emphasize the evolution aspects --- .../docs/user-guide/basic-concepts/workspace.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index f79d8166c2..e6568d6e22 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -18,10 +18,16 @@ of a project is desirable, although versioning needs and managing dependencies make it increasingly complex. DVC allows a single directory to contain all your project artifacts. The -workspace is the directory containing _user visible_ part of your -project e.g. raw datasets, source code, ML models, etc. Users work -in this directory using their data and model files that and manipulate the -contents through DVC commands. +workspace is the directory containing _visible_ part of your +project e.g. raw data, source code, model files. You can have +multiple versions of data, models and other kinds of artifacts within the +workspace and limit your focus to a subset of these, then record your progress +in a commit and move along your data and model history. DVC provides a _machine +learning file system_ to manipulate your data and models using its commands. No +need to keep different artifact versions in different directories, under +different names, without any semantic relation among them. Instead DVC is able +to link your data and models and can show the evolution, progress and +interrelationships. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, From 42559e2536309ea60c9b1bdba8cc8a70dc988b8f Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Mon, 22 Feb 2021 21:42:57 +0300 Subject: [PATCH 11/14] Modified the paragraph to reduce "file, directory" repeats --- content/docs/user-guide/basic-concepts/workspace.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index e6568d6e22..1bef206902 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -31,9 +31,9 @@ interrelationships. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, -`dvc import-url`). Changes to the files, directories, notebooks, models, and in -general machine learning file system can be tracked (`dvc commit`) and versioned -in Git (`dvc checkout`). They can be removed (`dvc remove`) from the workspace. +`dvc import-url`). Changes to the data, notebooks, models, and any related +machine learning artifact can be tracked (`dvc commit`) and versioned in Git +(`dvc checkout`). They can be removed (`dvc remove`) from the workspace. Pipelines and dependencies between them can be defined. Data and model files can be moved to the cloud and retrieved when necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of files From 6cc0f6c53c0d272871f859a9b677293afe8ba542 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Mon, 22 Feb 2021 22:33:23 +0300 Subject: [PATCH 12/14] Removed pipelines etc. sentences --- content/docs/user-guide/basic-concepts/workspace.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 1bef206902..f76b22d3fa 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -32,12 +32,10 @@ interrelationships. Files and directories in the workspace can be added to DVC (`dvc add`) or they can be downloaded from external sources (`dvc get`, `dvc import`, `dvc import-url`). Changes to the data, notebooks, models, and any related -machine learning artifact can be tracked (`dvc commit`) and versioned in Git -(`dvc checkout`). They can be removed (`dvc remove`) from the workspace. -Pipelines and dependencies between them can be -defined. Data and model files can be moved to the cloud and retrieved when -necessary (`dvc push`, `dvc pull`). DVC supports all typical operations of files -and directories of a file system through its commands. +machine learning artifact can be tracked (`dvc commit`) and their content can be +synchronized (`dvc checkout`). Tracked data can be removed (`dvc remove`) from +the workspace. DVC supports all typical operations of files and directories of a +file system through its commands. Behind the scene these operations of a DVC project uses metafiles like the `.dvc/` directory, `dvc.yaml` or files with From e85a0d762e36573566e957a8e6310bc2fcd0b309 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Mon, 22 Feb 2021 22:42:35 +0300 Subject: [PATCH 13/14] Moved typical ops sentence to the next paragraph and some rephrasing --- content/docs/user-guide/basic-concepts/workspace.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index f76b22d3fa..5be3e7980e 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -34,12 +34,12 @@ can be downloaded from external sources (`dvc get`, `dvc import`, `dvc import-url`). Changes to the data, notebooks, models, and any related machine learning artifact can be tracked (`dvc commit`) and their content can be synchronized (`dvc checkout`). Tracked data can be removed (`dvc remove`) from -the workspace. DVC supports all typical operations of files and directories of a -file system through its commands. +the workspace. -Behind the scene these operations of a DVC project uses -metafiles like the `.dvc/` directory, `dvc.yaml` or files with -`*.dvc` extension to track the content and dependencies. +DVC supports all typical operations of a versioned data file system through its +commands. Behind the scene these operations use metafiles like the +`.dvc/` directory, `dvc.yaml` files or files with `*.dvc` extension to track the +content and dependencies. ## Further Reading From 0b099f61e7eb68a9818b3f34c3c257506f59b218 Mon Sep 17 00:00:00 2001 From: Emre Sahin Date: Fri, 26 Feb 2021 20:05:27 +0300 Subject: [PATCH 14/14] Modified some sentences and the tooltip for clarity --- .../user-guide/basic-concepts/workspace.md | 40 +++++++++---------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/content/docs/user-guide/basic-concepts/workspace.md b/content/docs/user-guide/basic-concepts/workspace.md index 5be3e7980e..c0df21dbe6 100644 --- a/content/docs/user-guide/basic-concepts/workspace.md +++ b/content/docs/user-guide/basic-concepts/workspace.md @@ -2,39 +2,39 @@ name: Workspace match: [workspace] tooltip: >- - Directory containing all your project files e.g. raw datasets, source code, ML - models, etc. Typically, it's also a Git repository. It will contain your DVC + The directory containing all your project files, e.g., the raw data, source + code, ML models. Typically, it's also a Git repository. It contains your DVC project. --- # Workspace -A data science project consists of data obtained from many different sources. -This data may be split into multiple files or directories or (as the project -structure needs) have different versions for different requirements. e.g. A +A data science project can consist of data obtained from many distinct sources. +These may be split into multiple files or directories or (as the project +structure needs) have different versions for different requirements, e.g., a smaller / simplified version might be required in prototyping for faster feedback and shorter training times. A single workspace to manage all artifacts of a project is desirable, although versioning needs and managing dependencies -make it increasingly complex. +make it increasingly difficult. DVC allows a single directory to contain all your project artifacts. The -workspace is the directory containing _visible_ part of your -project e.g. raw data, source code, model files. You can have -multiple versions of data, models and other kinds of artifacts within the -workspace and limit your focus to a subset of these, then record your progress -in a commit and move along your data and model history. DVC provides a _machine -learning file system_ to manipulate your data and models using its commands. No -need to keep different artifact versions in different directories, under -different names, without any semantic relation among them. Instead DVC is able -to link your data and models and can show the evolution, progress and -interrelationships. +workspace is the directory containing the _visible_ part of your +project, e.g., the raw data, source code, model files. You can have +multiple versions of data, models, and other kinds of artifacts within the +workspace and limit your focus to a subset of these. You can record your +progress in a commit and analyze your data and model history. DVC provides a +_machine learning file system_ to manipulate your data and models using its +commands. No need to rename your models for minor changes, save cleaned up data +in different directories or save tens of different renamed files for training +programs. DVC can keep track of all of these in a single directory called the +workspace. -Files and directories in the workspace can be added to DVC (`dvc add`) or they +Files and directories in the workspace can be added to DVC (`dvc add`), or they can be downloaded from external sources (`dvc get`, `dvc import`, `dvc import-url`). Changes to the data, notebooks, models, and any related -machine learning artifact can be tracked (`dvc commit`) and their content can be -synchronized (`dvc checkout`). Tracked data can be removed (`dvc remove`) from -the workspace. +machine learning artifact can be tracked (`dvc commit`), and their content can +be synchronized (`dvc checkout`). Tracked data can be removed (`dvc remove`) +from the workspace. DVC supports all typical operations of a versioned data file system through its commands. Behind the scene these operations use metafiles like the