Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TO-DOs to complete tutorial #16

Open
emiliom opened this issue Sep 11, 2017 · 2 comments
Open

TO-DOs to complete tutorial #16

emiliom opened this issue Sep 11, 2017 · 2 comments

Comments

@emiliom
Copy link
Member

emiliom commented Sep 11, 2017

This TO-DO list is for me only, to keep track of my remaining TO-DO's.

  1. (DONE) Update Introduction episode.
  2. (DONE) Update Geospatial Concepts episode
    • Minor tweaks only (add links, correct spelling and other errors, etc)
  3. (DONE) Update Encodings, Formats and Libraries episode
    • Ideally overhaul it substantially! This episode was never mature. It was more of an outline.
    • Incorporate Don's fixed/new syntax highlighting code for software carpentry
  4. Finish notebooks and convert them to the software carpentry markdown
    • Apply "manual" changes to markdown generated by the jupyter converter
      • Change link to actual notebook, to point to notebook on tutorial_contents repo
    • Regenerate the images (png's) from the notebooks, and upload to the repo
    • Missing pieces to add (decide with Don):
      • (DONE, updated db.json) New read-only user & password
      • (DONE, but changed plans) Where to place the db.json file, and where to place user instructions about accessing it? We'll ask people to create it manually from Jupyter (using "Create new file"), using the notebook template text + the credentials we give them. This will slow down the pace, but we'll deal with it.
@emiliom
Copy link
Member Author

emiliom commented Sep 13, 2017

Regarding db.json file: In the end I decided to include it in the tutorial_contents repo (under vector/data), for convenience to participants and to minimize time wasted during the tutorial while people manually constructed and saved the file. That worked out smoothly. Note that it also involved editing .gitignore to allow the file to be tracked.

After GeoHackWeek is over, consider removing the file from github, by removing it from github and adding it to .gitignore (on both github and my local clone, probably).

@emiliom
Copy link
Member Author

emiliom commented Sep 15, 2017

Issue of Matplotlib 2.0 vs 1.5 in conda environment. Look into creating a new env that builds with 2.0, then re-run the notebooks (and rebuild notebook-based episodes? Yikes)

9/19/2017: See "solution" from Filipe: #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant