Skip to content

Commit 201ee6d

Browse files
committed
replaced python with json highlighting
1 parent f61aecd commit 201ee6d

File tree

2 files changed

+6
-12
lines changed

2 files changed

+6
-12
lines changed

README.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ algorithm.init({"data": "https://i.imgur.com/bXdORXl.jpeg"})
215215
Model Manifests are optional files that you can provide to your algorithm to easily
216216
define important model files, their locations; and metadata - this file is called `model_manifest.json`.
217217
<!-- embedme examples/pytorch_image_classification/model_manifest.json -->
218-
```python
218+
```json
219219
{
220220
"required_files" : [
221221
{ "name": "squeezenet",
@@ -249,7 +249,7 @@ define important model files, their locations; and metadata - this file is calle
249249
With the Model Manifest system, you're also able to "freeze" your model_manifest.json, creating a model_manifest.json.freeze.
250250
This file encodes the hash of the model file, preventing tampering once frozen - forver locking a version of your algorithm code with your model file.
251251
<!-- embedme examples/pytorch_image_classification/model_manifest.json.freeze -->
252-
```python
252+
```json
253253
{
254254
"required_files":[
255255
{
@@ -298,7 +298,7 @@ For this, you'll need to select an MLOps Enabled Environment; and you will need
298298
Once setup, you will need to define your `mlops.json` file, including your deployment and model ids.
299299

300300
<!-- embedme examples/mlops_hello_world/mlops.json -->
301-
```python
301+
```json
302302
{
303303
"model_id": "YOUR_MODEL_ID",
304304
"deployment_id": "YOUR_DEPLOYMENT_ID",
@@ -345,9 +345,6 @@ algorithm.init(0.25, mlops=True)
345345

346346
```
347347

348-
report_deployment_stats()
349-
350-
351348

352349

353350
## Readme publishing

README_template.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,12 +61,12 @@ Check out these examples to help you get started:
6161
Model Manifests are optional files that you can provide to your algorithm to easily
6262
define important model files, their locations; and metadata - this file is called `model_manifest.json`.
6363
<!-- embedme examples/pytorch_image_classification/model_manifest.json -->
64-
```python
64+
```json
6565
```
6666
With the Model Manifest system, you're also able to "freeze" your model_manifest.json, creating a model_manifest.json.freeze.
6767
This file encodes the hash of the model file, preventing tampering once frozen - forver locking a version of your algorithm code with your model file.
6868
<!-- embedme examples/pytorch_image_classification/model_manifest.json.freeze -->
69-
```python
69+
```json
7070
```
7171

7272
As you can link to both hosted data collections, and AWS/GCP/Azure based block storage media, you're able to link your algorithm code with your model files, wherever they live today.
@@ -81,7 +81,7 @@ For this, you'll need to select an MLOps Enabled Environment; and you will need
8181
Once setup, you will need to define your `mlops.json` file, including your deployment and model ids.
8282

8383
<!-- embedme examples/mlops_hello_world/mlops.json -->
84-
```python
84+
```json
8585
```
8686

8787
Along with defining your `DATAROBOT_MLOPS_API_TOKEN` as a secret to your Algorithm, you're ready to start sending MLOps data back to DataRobot!
@@ -90,9 +90,6 @@ Along with defining your `DATAROBOT_MLOPS_API_TOKEN` as a secret to your Algorit
9090
```python
9191
```
9292

93-
report_deployment_stats()
94-
95-
9693

9794

9895
## Readme publishing

0 commit comments

Comments
 (0)