Skip to content

Commit

Permalink
install updates
Browse files Browse the repository at this point in the history
  • Loading branch information
kbarnhart committed May 9, 2019
1 parent e058a61 commit 8eb5d89
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ This repository contains resources used in a clinic on using [Dakota](https://da

## Options for running the examples.

1) Use [this Binder link](https://mybinder.org/v2/gh/kbarnhart/calibration_with_dakota_clinic.git/master).
2) Use [Hydroshare]().
1) Use [Binder](https://mybinder.org/v2/gh/kbarnhart/calibration_with_dakota_clinic.git/master).
2) Use [Hydroshare]() (link not yet active).
3) Install the repo and Dakota yourself.

## Install instructions
Expand All @@ -32,11 +32,15 @@ Open a terminal and execute the following commands to download the repository, c
$ git clone https://github.com/kbarnhart/calibration_with_dakota_clinic.git
$ conda env create -f environment_YOUR_OS_HERE.yml
$ conda activate dakota_clinic
$ cd heat/
$ make install
$ pytest
```

If you want to test your install, type
```bash
pytest
```
This may take ~15 minutes (you are running all of the experiments we will do in the clinic and testing that they work).

#### Option B: Dakota Binary + conda env

Step 1: [Install the Dakota binary for Windows](https://dakota.sandia.gov/download.html) and make a [conda environment](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#managing-environments) based on the file `environment_everything_but_dakota.yml`.
Expand All @@ -46,17 +50,14 @@ After downloading/installing the Dakota binary, open a terminal and do the follo
$ git clone https://github.com/kbarnhart/calibration_with_dakota_clinic.git
$ conda env create -f environment_everything_but_dakota.yml
$ conda activate dakota_clinic
$ cd heat/
$ make install
$ pytest
```

### Step 2: Open a notebook.

Assuming that the results of `pytest` don't include any failures, go up one directory level and open jupyter notebooks.
Assuming that the results of `pytest` don't include any failures, open Jupyter Notebooks.

```bash
$ cd ..
$ jupyter notebook
```

Expand Down

0 comments on commit 8eb5d89

Please sign in to comment.