Skip to content

Commit

Permalink
development_setup.md update (microsoft#349)
Browse files Browse the repository at this point in the history
* development_setup.md update

development_setup.md updated to use install_requirements.sh.

See microsoft#158:

> Use conda rather than pip packages when possible (as recommended in AML docs).
> Dev environment is hence also constrained to conda (no more pip install -r requirements.txt).

* Content of install_requirements.sh deleted

* build_train_pipeline.py filename fixed

* build_train_pipeline.py filename fixed
  • Loading branch information
satonaoki authored Feb 16, 2021
1 parent 31512d3 commit aba8aef
Showing 1 changed file with 5 additions and 12 deletions.
17 changes: 5 additions & 12 deletions docs/development_setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,31 +10,24 @@ In order to configure the project locally, create a copy of `.env.example` in th

[Install the Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli). The Azure CLI will be used to log you in interactively.

Create a virtual environment using [venv](https://docs.python.org/3/library/venv.html), [conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html) or [pyenv-virtualenv](https://github.com/pyenv/pyenv-virtualenv).
Install [conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html).

Here is an example for setting up and activating a `venv` environment with Python 3:
Install the required Python modules. [`install_requirements.sh`](https://github.com/microsoft/MLOpsPython/blob/master/environment_setup/install_requirements.sh) creates and activates a new conda environment with required Python modules.

```
python3 -mvenv .venv
source .venv/bin/activate
```

Install the required Python modules in your virtual environment.

```
pip install -r environment_setup/requirements.txt
. environment_setup/install_requirements.sh
```

### Running local code

To run your local ML pipeline code on Azure ML, run a command such as the following (in bash, all on one line):

```
export BUILD_BUILDID=$(uuidgen); python ml_service/pipelines/build_train_pipeline.py && python ml_service/pipelines/run_train_pipeline.py
export BUILD_BUILDID=$(uuidgen); python ml_service/pipelines/diabetes_regression_build_train_pipeline.py && python ml_service/pipelines/run_train_pipeline.py
```

BUILD_BUILDID is a variable used to uniquely identify the ML pipeline between the
`build_train_pipeline.py` and `run_train_pipeline.py` scripts. In Azure DevOps it is
`diabetes_regression_build_train_pipeline.py` and `run_train_pipeline.py` scripts. In Azure DevOps it is
set to the current build number. In a local environment, we can use a command such as
`uuidgen` so set a different random identifier on each run, ensuring there are
no collisions.

0 comments on commit aba8aef

Please sign in to comment.