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
The text was updated successfully, but these errors were encountered:
jtmiclat
changed the title
Determine how much complexity it is to run non-tutorial notebooks in collab and decide if it is worth keeping in the notebook.
Decide if it is worth keeping collab specific code in the notebook just for it to run non tutorial notebooks
Jun 29, 2022
jtmiclat
changed the title
Decide if it is worth keeping collab specific code in the notebook just for it to run non tutorial notebooks
Decide if it is worth keeping collab specific code in non tutorial notebooks just for it to run in collab
Jun 29, 2022
jtmiclat
changed the title
Decide if it is worth keeping collab specific code in non tutorial notebooks just for it to run in collab
Create meta function to install necessary packages and resources to run in colab
Jun 30, 2022
Related to this, I found that we could simplify the generation of the colab link in the docs from manually specifying in each notebook to just adding an entry in the docs/_config.yml file.
default_badges:
colab: true
I can start a PR to start cleaning up the notebooks.
Currently we are installing a bunch of things within notebooks just so it works in collab
geowrangler/notebooks/02_vector_zonal_stats.ipynb
Lines 20 to 25 in a918c66
Is this something we should keep doing?
The text was updated successfully, but these errors were encountered: