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
Copy file name to clipboardExpand all lines: _sources/private_recipes.rst.txt
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ for more information on the :code:`ggd check-recipe` command see :ref:`ggd check
63
63
.. note::
64
64
65
65
Installing private data recipes will take longer because the recipe goes through the normal check and validation step before it is
66
-
installed. Additionally, there is now way to cache private data recipes, so the speedup seen from installing public data recipes is
66
+
installed. Additionally, there is no way to cache private data recipes, so the speedup seen from installing public data recipes is
67
67
not available.
68
68
69
69
@@ -75,7 +75,7 @@ Now that the data recipe has been created, it has been checked, and installed, y
75
75
76
76
.. note::
77
77
78
-
We are suggesting adding the *data recipe* not the actual data to the private github repository
78
+
We are suggesting adding the *data recipe*, not the actual data to the private github repository
79
79
80
80
81
81
@@ -104,7 +104,7 @@ C. Listing installed private recipes
104
104
105
105
:code:`ggd list` has a :code:`--prefix` argument that is used to list installed data recipes in different
106
106
conda environments. The :code:`--prefix` argument **can** be used for private recipes. This means you can list
107
-
private data recipes that are installed in a different conda environment then the currently active environment
107
+
private data recipes that are installed in a different conda environment than the currently active environment
108
108
you are using.
109
109
110
110
For more information about the :code:`ggd list` command see: :ref:`ggd-list`
@@ -117,7 +117,7 @@ D. Getting data files for private recipes
117
117
118
118
:code:`ggd get-files` has a :code:`--prefix` argument that is used to get installed data files from different conda environments.
119
119
This :code:`--prefix` argument **can** be used for private recipes. This means you can get installed data files from private recipes
120
-
that are in a different conda environment then the currently active one.
120
+
that are in a different conda environment than the currently active one.
121
121
122
122
For more information about the :code:`ggd get-files` command see: :ref:`ggd-get-files`
123
123
@@ -144,20 +144,20 @@ data recipe.
144
144
145
145
.. note::
146
146
147
-
The :code:`-du` argument is absent from the :code:`ggd check-recipe` command.
147
+
To uninstall the private data recipe you must omit the :code:`-du` argument from the :code:`ggd check-recipe` command.
148
148
149
149
150
150
151
151
Finally
152
152
-------
153
153
154
-
GGD is a data management system built to mange and distribute publicly available scientific data. As this is the main purpose of GGD we encourage
154
+
GGD is a data management system built to manage and distribute publicly available scientific data. As this is the main purpose of GGD we encourage
155
155
user to add ggd recipes to the public ggd repositories for the scientific community to use. GGD is built to help remove the inconsistencies with
156
-
data processing and management that has plagued researchers for year. Therefore, GGD will continue to encourage public data access, management, and
157
-
reproducibility. We understand that sometimes data cannot be shared publicly, but that the convenience and power of GGD can assist researchers and
158
-
scientist during an analysis. The features on this page are here to assist if you want to use GGD but truly need to retain data privacy.
159
-
However, GGD will continue to promote public data sharing whenever possible, and therefore, the GGD features will be maintained to support such
160
-
goals.
156
+
data processing and management that have plagued researchers for year. Therefore, GGD will continue to encourage public data access, management, and
157
+
reproducibility. We understand that sometimes data cannot be shared publicly, but a user may wish to use GGD to process and manage their data, as well
158
+
as to use the infrastructure of data recipes for reproducibility. The features on this page are here to assist if you want to use GGD but truly need
159
+
to retain data privacy. However, GGD will continue to promote public data sharing whenever possible, and therefore, the GGD features will be maintained
@@ -179,7 +179,7 @@ <h2>5. How to access installed data from private recipe<a class="headerlink" hre
179
179
<pclass="admonition-title">Note</p>
180
180
<p><codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">list</span></code> has a <codeclass="code docutils literal notranslate"><spanclass="pre">--prefix</span></code> argument that is used to list installed data recipes in different
181
181
conda environments. The <codeclass="code docutils literal notranslate"><spanclass="pre">--prefix</span></code> argument <strong>can</strong> be used for private recipes. This means you can list
182
-
private data recipes that are installed in a different conda environment then the currently active environment
182
+
private data recipes that are installed in a different conda environment than the currently active environment
183
183
you are using.</p>
184
184
</div>
185
185
<p>For more information about the <codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">list</span></code> command see: <aclass="reference internal" href="list.html#ggd-list"><spanclass="std std-ref">ggd list</span></a></p>
@@ -192,7 +192,7 @@ <h2>5. How to access installed data from private recipe<a class="headerlink" hre
192
192
<pclass="admonition-title">Note</p>
193
193
<p><codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">get-files</span></code> has a <codeclass="code docutils literal notranslate"><spanclass="pre">--prefix</span></code> argument that is used to get installed data files from different conda environments.
194
194
This <codeclass="code docutils literal notranslate"><spanclass="pre">--prefix</span></code> argument <strong>can</strong> be used for private recipes. This means you can get installed data files from private recipes
195
-
that are in a different conda environment then the currently active one.</p>
195
+
that are in a different conda environment than the currently active one.</p>
196
196
</div>
197
197
<p>For more information about the <codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">get-files</span></code> command see: <aclass="reference internal" href="list-file.html#ggd-get-files"><spanclass="std std-ref">ggd get-files</span></a></p>
198
198
</div></blockquote>
@@ -217,18 +217,18 @@ <h2>7. Uninstalling a previously installed private data recipe<a class="headerli
217
217
data recipe.</p>
218
218
<divclass="admonition note">
219
219
<pclass="admonition-title">Note</p>
220
-
<p>The <codeclass="code docutils literal notranslate"><spanclass="pre">-du</span></code> argument is absent from the <codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">check-recipe</span></code> command.</p>
220
+
<p>To uninstall the private data recipe you must omit the <codeclass="code docutils literal notranslate"><spanclass="pre">-du</span></code> argument from the <codeclass="code docutils literal notranslate"><spanclass="pre">ggd</span><spanclass="pre">check-recipe</span></code> command.</p>
221
221
</div>
222
222
</div>
223
223
<divclass="section" id="finally">
224
224
<h2>Finally<aclass="headerlink" href="#finally" title="Permalink to this headline">¶</a></h2>
225
-
<p>GGD is a data management system built to mange and distribute publicly available scientific data. As this is the main purpose of GGD we encourage
225
+
<p>GGD is a data management system built to manage and distribute publicly available scientific data. As this is the main purpose of GGD we encourage
226
226
user to add ggd recipes to the public ggd repositories for the scientific community to use. GGD is built to help remove the inconsistencies with
227
-
data processing and management that has plagued researchers for year. Therefore, GGD will continue to encourage public data access, management, and
228
-
reproducibility. We understand that sometimes data cannot be shared publicly, but that the convenience and power of GGD can assist researchers and
229
-
scientist during an analysis. The features on this page are here to assist if you want to use GGD but truly need to retain data privacy.
230
-
However, GGD will continue to promote public data sharing whenever possible, and therefore, the GGD features will be maintained to support such
231
-
goals.</p>
227
+
data processing and management that have plagued researchers for year. Therefore, GGD will continue to encourage public data access, management, and
228
+
reproducibility. We understand that sometimes data cannot be shared publicly, but a user may wish to use GGD to process and manage their data, as well
229
+
as to use the infrastructure of data recipes for reproducibility. The features on this page are here to assist if you want to use GGD but truly need
230
+
to retain data privacy. However, GGD will continue to promote public data sharing whenever possible, and therefore, the GGD features will be maintained
0 commit comments