Skip to content

Commit 75a1ba8

Browse files
authored
Update README.md
1 parent 4a26889 commit 75a1ba8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Assuming a Dask cluster is already set up, the steps involved to parallelize any
2727

2828
3. Since we use popular Python libraries (Dask, Numpy, etc.), this makes the system hardware agnostic. As long as we can compile an accelerator for the available hardware platform, the system can be deployed on that platform. We have run this setup on various hardware platforms such as Pynq-Z1 boards, AWS F1 instances, Nimbix cloud instances, and our in-house Alveo servers.
2929

30-
### Installation
30+
## Installation
3131

3232
Create a virtual environment
3333

@@ -42,7 +42,7 @@ Install octoray (this takes several minutes)
4242
`pip install -v -e . `
4343
`python3 setup.py install`
4444

45-
### Getting started
45+
## Getting started
4646

4747
OctoRay is build on two fundamental concepts: the cluster configuration and OctoRay kernels. The cluster configuration consists of a dictionary that is used to specify how the Dask distributed cluster should be deployed. OctoRay kernels are structures that consist of all the specifications necessary to deploy an application on the cluster. The example notebooks provide explanations on how to use the cluster configuration and OctoRay kernels to scale applications.
4848

0 commit comments

Comments
 (0)