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

Build collection of jupyter notebooks to illustrate each collector #54

Open
emiliom opened this issue Jan 1, 2016 · 9 comments
Open

Comments

@emiliom
Copy link
Contributor

emiliom commented Jan 1, 2016

Over the last two years @ocefpaf, myself, and several others (via the ioos system integration test) have created a bunch of jupyter notebooks that use various pyoos collectors. It would help in documenting pyoos usage if we compiled (after some cleanup) these in a notebooks group here.

Off the top of my head, I can remember seeing existing notebooks (including my own) for these collectors:

  • IoosSweSos
  • NDBC
  • COOPS
  • NERRS
  • HADS

That'd be a darn good start that hopefully will be fairly easy for a group of us to put together.

@emiliom
Copy link
Contributor Author

emiliom commented Jan 1, 2016

For reference, and to get the ball rolling a bit:

@ocefpaf
Copy link
Member

ocefpaf commented Jan 4, 2016

COOPS: @ocefpaf has a notebook or two

I have this one:
http://nbviewer.ipython.org/github/ocefpaf/inundation_notebook/blob/master/inundation_notebook.ipynb

We need to clean them up and make them consistent with each other. Region, filtering, text, etc. I am starting a branch with them.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 4, 2016

@emiliom see #55

@emiliom
Copy link
Contributor Author

emiliom commented Jan 4, 2016

@ocefpaf, that was fast!! Maybe too fast ... for me at least. I see you added HADS and NERRS notebooks. I suggest you let me handle that, and I'll make sure the notebooks we use are up-to-date; as I noted, the ones I linked to were fairly old, and I listed them only to add tangible references/examples.

I'm in no hurry on this. I created this issue b/c the idea popped in my head then, and we've been talking about pyoos documentation. I can probably dedicate time to it next week, but not this week.

If your NDBC and COOPS notebooks are already consistent with each other, I'll use those as templates for my notebooks.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 4, 2016

@ocefpaf, that was fast!! Maybe too fast ... for me at least. I see you added HADS and NERRS notebooks. I suggest you let me handle that, and I'll make sure the notebooks we use are up-to-date; as I noted, the ones I linked to were fairly old, and I listed them only to add tangible references/examples.

Sure. I just wanted to aggregate them into one place.

If your NDBC and COOPS notebooks are already consistent with each other, I'll use those as templates for my notebooks.

COOPS is ready to be reviewed. NDBC will be ready soon.

@emiliom
Copy link
Contributor Author

emiliom commented Jan 4, 2016

COOPS is ready to be reviewed. NDBC will be ready soon.

Cool! I don't think I'll review it until next week, unfortunately. FYI, my "pyoos time" this week will be focused on helping/prodding 😉 to get a pyoos release soon, and tracking issues with the IoosSweSos collector and 52North SOS that came up last week.

@ocefpaf
Copy link
Member

ocefpaf commented Jan 4, 2016

get a pyoos release soon.

Let me know if I can help you with that.

@rsignell-usgs
Copy link
Member

@emiliom , can this be closed?

@emiliom
Copy link
Contributor Author

emiliom commented May 19, 2017

@rsignell-usgs, well, I never got back to providing updated notebooks. But I won't do that in the next 3-4 weeks either. So, go ahead and close the issue for housekeeping if you'd like, and there's interest in updating notebooks if in the future, I can be pinged.

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

3 participants