|
137 | 137 | "source": [ |
138 | 138 | "### Resource Organization Using Namespace\n", |
139 | 139 | "\n", |
140 | | - "You can use a [namespace](https://developer.nvidia.com/docs/nemo-microservices/manage-entities/namespaces/index.html) to isolate and organize the artifacts in this tutorial." |
| 140 | + "You can use a [namespace](https://docs.nvidia.com/nemo/microservices/latest/manage-entities/namespaces/index.html) to isolate and organize the artifacts in this tutorial." |
141 | 141 | ] |
142 | 142 | }, |
143 | 143 | { |
|
191 | 191 | "source": [ |
192 | 192 | "#### Verify Namespaces\n", |
193 | 193 | "\n", |
194 | | - "The following [Data Store API](https://developer.nvidia.com/docs/nemo-microservices/api/datastore.html) and [Entity Store API](https://developer.nvidia.com/docs/nemo-microservices/api/entity-store.html) list the namespace created in the previous cell." |
| 194 | + "The following [Data Store API](https://docs.nvidia.com/nemo/microservices/latest/api/datastore.html) and [Entity Store API](https://docs.nvidia.com/nemo/microservices/latest/api/entity-store.html) list the namespace created in the previous cell." |
195 | 195 | ] |
196 | 196 | }, |
197 | 197 | { |
|
252 | 252 | "\n", |
253 | 253 | "**Note that this step does not interact with Hugging Face at all, it just uses the client library to interact with NeMo Data Store.** This is in comparison to the previous notebook, where we used the `load_dataset` API to download the xLAM dataset from Hugging Face's repository.\n", |
254 | 254 | "\n", |
255 | | - "More information can be found in [documentation](https://developer.nvidia.com/docs/nemo-microservices/manage-entities/tutorials/manage-dataset-files.html#set-up-hugging-face-client)" |
| 255 | + "More information can be found in [documentation](https://docs.nvidia.com/nemo/microservices/latest/manage-entities/tutorials/manage-dataset-files.html#set-up-hugging-face-client-with-nemo-data-store)" |
256 | 256 | ] |
257 | 257 | }, |
258 | 258 | { |
|
313 | 313 | "id": "97ac352a-31b9-4144-ad0f-699fcceebfc2", |
314 | 314 | "metadata": {}, |
315 | 315 | "source": [ |
316 | | - "Next, creating a dataset programmatically requires two steps: uploading and registration. More information can be found in [documentation](https://developer.nvidia.com/docs/nemo-microservices/manage-entities/datasets/create-dataset.html#how-to-create-a-dataset)." |
| 316 | + "Next, creating a dataset programmatically requires two steps: uploading and registration. More information can be found in [documentation](https://docs.nvidia.com/nemo/microservices/latest/manage-entities/datasets/create-dataset.html)." |
317 | 317 | ] |
318 | 318 | }, |
319 | 319 | { |
|
1005 | 1005 | "### 2.3 Validate Availability of Custom Model\n", |
1006 | 1006 | "The following NeMo Entity Store API should display the model when the training job is complete.\n", |
1007 | 1007 | "The list below shows all models filtered by your namespace and sorted by the latest first.\n", |
1008 | | - "For more information about this API, see the [NeMo Entity Store API reference](https://developer.nvidia.com/docs/nemo-microservices/api/entity-store.html).\n", |
| 1008 | + "For more information about this API, see the [NeMo Entity Store API reference](https://docs.nvidia.com/nemo/microservices/latest/api/entity-store.html).\n", |
1009 | 1009 | "With the following code, you can find all customized models, including the one trained in the previous cells.\n", |
1010 | 1010 | "Look for the `name` fields in the output, which should match your `CUSTOMIZED_MODEL`." |
1011 | 1011 | ] |
|
1384 | 1384 | "name": "python", |
1385 | 1385 | "nbconvert_exporter": "python", |
1386 | 1386 | "pygments_lexer": "ipython3", |
1387 | | - "version": "3.12.3" |
| 1387 | + "version": "3.10.12" |
1388 | 1388 | } |
1389 | 1389 | }, |
1390 | 1390 | "nbformat": 4, |
|
0 commit comments