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
On Github GUI, created a new repo called "hurricane_trimesh".
Answered the questions, using "hurricane_trimesh" as project name:
Verified that hurricane_trimesh folder got created locally:
Pushed to github following the github instructions for creating a new repository from the command line:
Added my notebooks, changed the environment.yml to suit my environment needs, and modified postBuild to specify a specific version of the jupyterlab-manager extension that is compatible with the specific version of the jupyterlab python package.
Clicked the "launch binder" button and waited (about 20 min) for binder.pangeo.io to build and launch.
Started up trimesh notebook: the kube cluster spun up in only a few minutes.
Calculated the max water level and interactively browsed the output with pyviz:
I successfully used
cookiecutter-pangeo-binder
to create a repo called "hurricane_trimesh":https://github.com/rsignell-usgs/hurricane_trimesh
Here's the play-by-play:
On Github GUI, created a new repo called "hurricane_trimesh".
Answered the questions, using "hurricane_trimesh" as project name:
Verified that hurricane_trimesh folder got created locally:
Pushed to github following the github instructions for creating a new repository from the command line:
Added my notebooks, changed the
environment.yml
to suit my environment needs, and modifiedpostBuild
to specify a specific version of thejupyterlab-manager
extension that is compatible with the specific version of thejupyterlab
python package.Clicked the "launch binder" button and waited (about 20 min) for binder.pangeo.io to build and launch.
Started up trimesh notebook: the kube cluster spun up in only a few minutes.
Calculated the max water level and interactively browsed the output with pyviz:
Thanks @jhamman for an awesome tool!
The text was updated successfully, but these errors were encountered: