Merge branch 'dev' into openROM-verilogoutput

To test recent changes with ROM verilog output

docs/source/basic_setup.md

@@ -30,16 +30,38 @@ you don't have to worry about updating/installing these tools. OpenRAM installs
 Anaconda silently in the background (without affecting any existing Anaconda
 setup you have).
 
+You don't have to manually activate/deactivate the Anaconda environment. OpenRAM
+automatically manages this before and after running the tools.
+
 OpenRAM uses Anaconda by default, but you can turn this feature off by setting
 `use_conda = False` in your config file. Then, OpenRAM will use the tools you
 have installed on your system.
 
+You can also tell OpenRAM where Anaconda should be installed or which Anaconda
+setup it should use. You can set the `$CONDA_HOME` variable like this:
+```
+export CONDA_HOME="/path/to/conda/setup"
+```
+
 > **Note**: If you want to install Anaconda without running OpenRAM (for example
 > to run unit tests, which do not install Anaconda), you can run:
 > ```
 > ./install_conda.sh
 > ```
 
+> **Note**: You can uninstall OpenRAM's Anaconda installation by simply deleting
+> the folder Anaconda is installed to. You can run:
+> ```
+> rm -rf miniconda
+> ```
+
+> **Note**: You can change a tool's version with the following commands:
+> ```
+> source ./miniconda/bin/activate
+> conda uninstall <tool>
+> conda install -y -c vlsida-eda <tool>=<version>
+> ```
+
 
 
 ## Docker (deprecated, use Anaconda instead)

docs/source/index.md

@@ -9,6 +9,7 @@ navigate through the documentation.
 ## Table of Contents
 1. [OpenRAM Dependencies](#openram-dependencies)
 1. [Supported Technologies](#supported-technologies)
+1. [Online Playground](./OpenRAM.ipynb)
 1. [Basic Setup](./basic_setup.md#go-back)
 1. [Basic SRAM Usage](./basic_usage.md#go-back)
 1. [Basic ROM Usage](./basic_rom_usage.md#go-back)

docs/source/python_library.md

@@ -47,6 +47,13 @@ point to that OpenRAM installation directory.
 If you don't want to use this feature, you can simply unset these environment
 variables.
 
+> **Note**: If you are a developer working on the source code on local clone of
+> the repository and want to use the Python library at the same time, you should
+> set both `OPENRAM_HOME` and `OPENRAM_TECH` to point to the local clone (follow
+> [Basic Setup](./basic_setup.md#go-back)). This way, the library will use the
+> source code located at these paths and you won't have to rebuild the library
+> after every change.
+
 
 
 ## Usage