Skip to content

Commit b9b3572

Browse files
Merge pull request #5 from RichardScottOZ/patch-2
Update 3-dask-gatewaycluster.ipynb
2 parents 75bfbca + 26f4c38 commit b9b3572

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

1-multiple-cogs.ipynb

+1-1
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,7 @@
203203
"\n",
204204
"Here is an example of interactive visualization again using hvplot. Since we're using full resolution arrays it's key to set the `rasterize=True` keyword argument. That uses the datashader library to pre-render images before sending them to the browser.\n",
205205
"\n",
206-
"This is extremely powerful because, resolution updates as you soom in, and you can scrub through the data cube with an interactive slider widget"
206+
"This is extremely powerful because, resolution updates as you zoom in, and you can scrub through the data cube with an interactive slider widget"
207207
]
208208
},
209209
{

3-dask-gatewaycluster.ipynb

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
"\n",
99
"**Part 4. Dask GatewayCluster**\n",
1010
"\n",
11-
"Unlike LocalCluster, a Dask GatewayCluster gives us the ability to dynamically increase our CPU and RAM across many machines! This is extremely powerful, because now we can load very big datasets into RAM for efficient calculations. There is a complication in that now we are running computations on many physical machines instead of just one, so network communication is more challenging and the dask machines likely don't have access to your local files. When COGS are store on S3 though, we can access them from any machine!"
11+
"Unlike LocalCluster, a Dask GatewayCluster gives us the ability to dynamically increase our CPU and RAM across many machines! This is extremely powerful, because now we can load very big datasets into RAM for efficient calculations. There is a complication in that now we are running computations on many physical machines instead of just one, so network communication is more challenging and the dask machines likely don't have access to your local files. When COGS are stored on S3 though, we can access them from any machine!"
1212
]
1313
},
1414
{
@@ -48,7 +48,7 @@
4848
"source": [
4949
"### Dask GatewayCluster\n",
5050
"\n",
51-
"dask gateway allow us to connect to a Kubernetes Cluster so that we can go beyond the RAM and CPU of a single machine. It can take several minutes for these machines to initialize on the Cloud, so be patient when starting a cluster."
51+
"dask gateway allows us to connect to a Kubernetes Cluster so that we can go beyond the RAM and CPU of a single machine. It can take several minutes for these machines to initialize on the Cloud, so be patient when starting a cluster."
5252
]
5353
},
5454
{
@@ -203,7 +203,7 @@
203203
"source": [
204204
"### Visualization\n",
205205
"\n",
206-
"Using hvplot like we've done before will utilize the dask cluster as you request to plot each image"
206+
"Using hvplot like we've done before will utilize the dask cluster as you request plotting of each image"
207207
]
208208
},
209209
{

0 commit comments

Comments
 (0)