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
Raster Vision is an open source Python framework for building computer vision models on satellite, aerial, and other large imagery sets (including oblique drone imagery).
13
-
* It allows users (who don't need to be experts in deep learning!) to quickly and repeatably configure experiments that execute a machine learning workflow including: analyzing training data, creating training chips, training models, creating predictions, evaluating models, and bundling the model files and configuration for easy deployment.
13
+
* It allows users (who don't need to be experts in deep learning!) to quickly and repeatably configure experiments that execute a machine learning pipeline including: analyzing training data, creating training chips, training models, creating predictions, evaluating models, and bundling the model files and configuration for easy deployment.
14
14

15
-
* There is built-in support for chip classification, object detection, and semantic segmentation with backends using PyTorch and Tensorflow.
15
+
* There is built-in support for chip classification, object detection, and semantic segmentation with backends using PyTorch.
16
16

17
17
* Experiments can be executed on CPUs and GPUs with built-in support for running in the cloud using [AWS Batch](https://github.com/azavea/raster-vision-aws).
18
-
* The framework is extensible to new data sources, tasks (eg. object detection), backends (eg. TF Object Detection API), and cloud providers.
18
+
* The framework is extensible to new data sources, tasks (eg. instance segmentation), backends (eg. Detectron2), and cloud providers.
19
19
20
20
See the [documentation](https://docs.rastervision.io) for more details.
21
21
@@ -24,13 +24,11 @@ See the [documentation](https://docs.rastervision.io) for more details.
24
24
There are several ways to setup Raster Vision:
25
25
* To build Docker images from scratch, after cloning this repo, run `docker/build`, and run the container using `docker/run`.
26
26
* Docker images are published to [quay.io](https://quay.io/repository/azavea/raster-vision). The tag for the `raster-vision` image determines what type of image it is:
27
-
- The `tf-cpu-*` tags are for running the Tensorflow CPU containers.
28
-
- The `tf-gpu-*` tags are for running the Tensorflow GPU containers.
29
27
- The `pytorch-*` tags are for running the PyTorch containers.
30
28
- We publish a new tag per merge into `master`, which is tagged with the first 7 characters of the commit hash. To use the latest version, pull the `latest` suffix, e.g. `raster-vision:pytorch-latest`. Git tags are also published, with the Github tag name as the Docker tag suffix.
31
29
* Raster Vision can be installed directly using `pip install rastervision`. However, some of its dependencies will have to be installed manually.
32
30
33
-
For more detailed instructions, see the [Setup docs](https://docs.rastervision.io/en/0.11/setup.html).
31
+
For more detailed instructions, see the [Setup docs](https://docs.rastervision.io/en/0.12/setup.html).
34
32
35
33
### Example
36
34
@@ -39,124 +37,94 @@ The best way to get a feel for what Raster Vision enables is to look at an examp
Raster Vision uses a unittest-like method for executing experiments. For instance, if the above was defined in `tiny_spacenet.py`, with the proper setup you could run the experiment using:
148
118
149
119
```bash
150
-
> rastervision run local-p tiny_spacenet.py
120
+
> rastervision run local tiny_spacenet.py
151
121
```
152
122
153
-
See the [Quickstart](https://docs.rastervision.io/en/0.11/quickstart.html) for a more complete description of running this example.
123
+
See the [Quickstart](https://docs.rastervision.io/en/0.12/quickstart.html) for a more complete description of running this example.
Copy file name to clipboardExpand all lines: docs/architecture.rst
+5-5
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Architecture and Customization
5
5
6
6
.. _codebase overview:
7
7
8
-
Codebase overview
8
+
Codebase Overview
9
9
-------------------
10
10
11
11
The Raster Vision codebase is designed with modularity and flexibility in mind.
@@ -32,7 +32,7 @@ Writing pipelines and plugins
32
32
33
33
In this section, we explain the most important aspects of the ``rastervision.pipeline`` package through a series of examples which incrementally build on one another. These examples show how to write custom pipelines and configuration schemas, how to customize an existing pipeline, and how to package the code as a plugin.
34
34
35
-
The full source code for Examples 1 and 2 is in `rastervision.pipeline_example_plugin1 <https://github.com/azavea/raster-vision/tree/master/rastervision_pipeline/rastervision/pipeline_example_plugin1>`_ and Example 3 is in `rastervision.pipeline_example_plugin2 <https://github.com/azavea/raster-vision/tree/master/rastervision_pipeline/rastervision/pipeline_example_plugin2>`_ and they can be run from inside the RV Docker image. However, **note that new plugins are typically created in a separate repo and Docker image**, and :ref:`bootstrap` shows how to do this.
35
+
The full source code for Examples 1 and 2 is in `rastervision.pipeline_example_plugin1 <https://github.com/azavea/raster-vision/tree/0.12/rastervision_pipeline/rastervision/pipeline_example_plugin1>`_ and Example 3 is in `rastervision.pipeline_example_plugin2 <https://github.com/azavea/raster-vision/tree/0.12/rastervision_pipeline/rastervision/pipeline_example_plugin2>`_ and they can be run from inside the RV Docker image. However, **note that new plugins are typically created in a separate repo and Docker image**, and :ref:`bootstrap` shows how to do this.
36
36
37
37
.. _example 1:
38
38
@@ -59,7 +59,7 @@ Finally, in order to package this code as a plugin, and make it usable within th
59
59
60
60
We can invoke the Raster Vision CLI to run the pipeline using:
61
61
62
-
.. code-block:: shell
62
+
.. code-block:: terminal
63
63
64
64
> rastervision run inprocess rastervision.pipeline_example_plugin1.config1 -a root_uri /opt/data/pipeline-example/1/ -s 2
65
65
@@ -94,7 +94,7 @@ We can configure the pipeline using:
94
94
95
95
The pipeline can then be run with the above configuration using:
96
96
97
-
.. code-block:: shell
97
+
.. code-block:: terminal
98
98
99
99
> rastervision run inprocess rastervision.pipeline_example_plugin1.config2 -a root_uri /opt/data/pipeline-example/2/ -s 2
100
100
@@ -129,7 +129,7 @@ The code to implement the new configuration and behavior, and a sample configura
129
129
130
130
We can run the pipeline as follows:
131
131
132
-
.. code-block:: shell
132
+
.. code-block:: terminal
133
133
134
134
> rastervision run inprocess rastervision.pipeline_example_plugin2.config3 -a root_uri /opt/data/pipeline-example/3/ -s 2
Copy file name to clipboardExpand all lines: docs/bootstrap.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,9 @@
3
3
Bootstrap new projects with a template
4
4
=======================================
5
5
6
-
When using Raster Vision on a new project, the best practice is to create a new repo with its own Docker image based on the Raster Vision image. This involves a fair amount of boilerplate code which has a few things that vary between projects. To facilitate bootstrapping new projects, there is a `cookiecutter <https://cookiecutter.readthedocs.io/>`_ template. Assuming that you cloned the Raster Vision repo and ran ``pip install cookiecutter==1.7.0``, you can instantiate the template as follows (after adjusting paths appropriately for your particular setup).
6
+
When using Raster Vision on a new project, the best practice is to create a new repo with its own Docker image based on the Raster Vision image. This involves a fair amount of boilerplate code which has a few things that vary between projects. To facilitate bootstrapping new projects, there is a `cookiecutter <https://cookiecutter.readthedocs.io/>`_ `template<https://github.com/azavea/raster-vision/tree/0.12/cookiecutter_template>`_. Assuming that you cloned the Raster Vision repo and ran ``pip install cookiecutter==1.7.0``, you can instantiate the template as follows (after adjusting paths appropriately for your particular setup).
0 commit comments