[overview](#overview) | [launching the notebooks](#launching-the-notebooks) | [running the notebooks](#running-the-notebooks) | [issues](#issues) | [contributing](#for-contributors)
# gpgLabs
[](https://mybinder.org/v2/gh/geoscixyz/gpgLabs/master?filepath=Notebooks%2Findex.ipynb) [](https://travis-ci.org/geoscixyz/gpgLabs) [](http://simpeg.xyz)
## Overview
This is a repo of interactive examples for http://gpg.geosci.xyz.
The notebooks are available on - [Binder](https://mybinder.org/v2/gh/geoscixyz/gpgLabs/master?filepath=Notebooks%2Findex.ipynb)
- <!– <img src=”https://em.geosci.xyz/_images/DC_LayeredEarth_notebook.png” width=60% align=”center”>
–>
## Launching the notebooks
The notebooks can be run online through [Binder](#Binder), or [downloaded and run locally](#Locally).
### Binder
Launch the binder by clicking on the badge above or going to: https://mybinder.org/v2/gh/geoscixyz/gpgLabs/master?filepath=Notebooks%2Findex.ipynb. This can sometimes take a couple minutes, so be patient…
Select the notebook of interest from the contents
[Run the Jupyter notebook](#Running-the-notebooks)

### Locally
To run them locally, you will need to have python installed, preferably through [anaconda](https://www.anaconda.com/download/).
You can then clone this reposiroty. From a command line, run
` git clone https://github.com/geoscixyz/gpgLabs.git `
Then cd into gpgLabs
` cd gpgLabs `
To setup your software environment, we recommend you use the provided conda environment
` conda env create -f environment.yml source activate em-apps-environment `
alternatively, you can install dependencies through pypi ` pip install -r requirements.txt `
You can then launch Jupyter ` jupyter notebook `
Jupyter will then launch in your web-browser.
## Running the notebooks
Each cell of code can be run with shift + enter or you can run the entire notebook by selecting cell, Run All in the toolbar.

For more information on running Jupyter notebooks, see the [Jupyter Documentation](https://jupyter.readthedocs.io/en/latest/)
## Issues
If you run into problems or bugs, please let us know by [creating an issue](https://github.com/geoscixyz/em-apps/issues/new) in this repository.
## For Contributors
### Notebook Structure
Each notebook has the following structure
Purpose : Motivation and key concepts addressed by the notebook
Setup : Overview of the relevant parameters in the problem
Questions : Guiding questions related to the purpose
App : interactive visualizations
Explore : further questions that can be explored with the app
### Setting up your environment
to develop code for these notebooks, please see https://github.com/geoscixyz/gpgLabs
add the notebook name and path to the [index](index.ipynb)
Metadata
Release files for gpgLabs 0.0.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gpgLabs-0.0.12.tar.gz | 34.7 kB | Without provenance | Details |
Release files / gpgLabs-0.0.12.tar.gz
| Download URL | gpgLabs-0.0.12.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fee6c3292d81ed57a15f3eb77ca354822f043fa084e045003b526618f5062879
|
|
BLAKE2b-256 checksum How to use checksums |
b0e01d86bc55ae0cd86683171365a3afac4642145bfb7c2a65797406ff7c796a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/2.7.15
|
Security for gpgLabs 0.0.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.