This is a first draft of the blogpost combining waterinfo package with eel data. This is far from ready, but I do think this is the right moment to have a first review round: concept/storyline/code handling/...
The main file to review is the notebook waterinfo-tidal.ipynb. All suggestions are welcome! One of the things I'm a bit stuck with, is the amount of R programming in the blogpost. We want to show how the wateRinfo package works (code required), but for the other sections (plots,...) the code gets more complex and explaining this would miss the main message... Would it be an option to just exclude plot-code from the post and only show code for the wateRinfo section?
Furthermore: @peterdesmet What to do with the other notebook (a preanalysis of the station distances which is not part of the blogpost)? I propose to create a gist on my account to refer to and remove the notebook here, ok?
This is a first draft of the blogpost combining waterinfo package with eel data. This is far from ready, but I do think this is the right moment to have a first review round: concept/storyline/code handling/...
The main file to review is the notebook
waterinfo-tidal.ipynb
. All suggestions are welcome! One of the things I'm a bit stuck with, is the amount of R programming in the blogpost. We want to show how the wateRinfo package works (code required), but for the other sections (plots,...) the code gets more complex and explaining this would miss the main message... Would it be an option to just exclude plot-code from the post and only show code for the wateRinfo section?Furthermore: @peterdesmet What to do with the other notebook (a preanalysis of the station distances which is not part of the blogpost)? I propose to create a gist on my account to refer to and remove the notebook here, ok?