-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add short example notebooks #48
Comments
My suggestion is to make an example related to the optics / chlorophyll quenching part which seem to be well developed. |
Now that we're on conda-forge I'll move forward with some example notebooks. @lukegre what considerations should we take with these? Obviously we want to avoid recreating the monster notebook. Are the 16 MB of data in tests/data necessary? |
Great looking forward to these example notebooks! Will you focus on the optics part of GliderTools? It is very advanced! @tjryankeogh |
I have created a repo for the notebooks here: |
Awesome! Should we add a link to the binder/repo to the README and/or docs? |
I think that would be nice. If @callumrollo is interested maybe the demo repo can live in the community (https://github.com/GliderToolsCommunity) but as a separate object from the Glidertools. |
Thats a great idea! |
Good shout Dhruv, I've just transferred it |
Rationale
The only current notebook is huge and overwhelming. A set of small notebooks for specific, common tasks would be much more appealing to the casually interested scientist
How the user would call this functionality.
Ideally by clicking a button in the README that launches a Binder notebook e.g. "Intro to glider tools" or "correct for chlorophyll quenching"
Outline what is needed for this feature
Should write notebooks for features that
I think porting the package to conda-forge (#45) will make this easier. In my experience, binder prefers conda packages to pip.
This is an issue from the #46 wishlist
The text was updated successfully, but these errors were encountered: