JupyterDay in the Triangle

2018-10-04T16:15:00+00:00

We’re excited to announce the next JupyterDay event! Please join us for JupyterDay in the Triangle on November 13, 2018 at the Carolina Club on the University of North Carolina at Chapel Hill campus. The event is hosted by the UNC University Libraries with additional funding from our generous sponsors.

JupyterDay in the Triangle will be an engaging mix of talks, discussions, and birds of a feather sessions on topics spanning the full ecosystem of Jupyter. The theme of the event focuses on the work of Early Career Researchers & Data Scientists. We are hoping for contributions from this group, but are open to all proposals. We are committed to creating a welcoming environment that fosters diversity and inclusion in the broad spectrum of projects and ideas that will be discussed.

The Day’s Agenda

8:00am — 9:00am: Check-in, network, and enjoy breakfast
9:00am — 9:30am: Introductions & logistics
9:30am — 10:30am: Keynote with Q&A
10:30am — 10:45am: Relax, it’s break time
10:45am — 12:00pm: Two brief 25 minute talks
12:00pm — 1:00pm: Lunchtime
1:00pm — 2:00pm: Two brief 25 minute talks
2:00pm — 2:15pm: Relax, it’s time for some PM snacks and a break
2:15pm — 3:30pm: Lightning talks from attendees, 5 minutes each
3:30pm — 5:00pm: Birds of a Feather discussions on topics from the community

Submit a Proposal

We are accepting proposals for 25 minute talks, 5 minute talks, and birds of a feather (BoF) sessions until October 12, 2018. Any Jupyter-related topic you think would be of interest to attendees will be of interest to us. Selected speakers and BoF session leads will receive complimentary admission.

Click here to submit your proposal

Register to Attend

Registration to attend Jupyter Day in the Triangle is now open. You can purchase student ($10) or professional tickets ($25 early bird, $30 regular) on our EventBrite page.

Click here to register

If your organization is a fan of Project Jupyter and would like to give back to the community, we are looking for contributors and sponsors. Please contact us for further information.

For More Information

Please visit the event website for up-to-date information about the agenda, confirmed speakers, venue, transportation, lodging, etc.

Jupyter Kernel Gateway

2016-03-09T03:19:00+00:00

Last Friday, the Jupyter Steering Council voted to make the incubating Kernel Gateway project a top-level Jupyter project. I want to thank everyone for their contributions so far — code from my teammates at IBM and beyond; advice from the Jupyter development team; and questions, issues, and requirements from end users.

What is it?

The kernel gateway is a web server that clients can use to spawn and communicate with Jupyter kernels. Currently, it supports two such mechanisms:

A 100% Jupyter Notebook server compatible API for:
Creating, listing, and deleting Jupyter kernels via HTTP
Communicating with those kernels using the Jupyter kernel protocol via Websockets
A notebook-defined API that maps HTTP verbs (e.g., GET, POST) and resources (e.g., /foo/:bar) to code that executes on a kernel

What problem does it solve?

People are creating novel web applications that use Jupyter kernels as interactive code execution engines. For example:

pyxie uses kernels to evaluate code from a text area on a web page
Thebe uses kernels to evaluate code from multiple input areas on a web page
gist exec uses kernels to evaluate code from GitHub gists rendered as web pages
Atom Notebook uses kernels to enable a notebook experience in the Atom text editor
Eclairjs uses the Apache Toree kernel as a means of making Apache Spark API calls from JavaScript
Jupyter dashboard server uses kernels to evaluate code from notebooks rendered as interactive dashboards

These applications have two important properties in common:

They spawn kernels using provisioning APIs that run separate, and often remote, from the user-facing applications themselves.
They communicate with kernels using Websockets rather than directly with ZeroMQ.

Developers can deploy instances of the full Jupyter Notebook server to satisfy these requirements. However, this approach is less than ideal:

The notebook UI is exposed, but only the programmatic API is used.
The notebook authentication mechanism is form- and cookie-based and meant for humans, not programmatic clients.
The notebook transport mechanisms and APIs serve the notebook user experience, and are not meant to be replaced or extended to support other clients.

The kernel gateway addresses these issues, and others, in a Python package that can be used across new Jupyter-enabled applications.

What’s next?

In the short term, we plan to bring the documentation, test suite, and code into line with other Jupyter projects. Over time, we hope to separate the different APIs layers into more maintainable packages, and gather requirements from users developing new kernel-powered applications.

For More Information

Visit the jupyter/kernel_gateway GitHub project for the source and issue tracker.
Check out the posts about the kernel gateway on the IBM Emerging Technology blog. Then visit the jupyter/kernel_gateway_demos project to try some of the examples yourself.
Reach-out on the Jupyter Google Group or in the jupyter/jupyter gitter channel.
Chat with me at the Berkeley Data Science Meetup on March 29th, 2016.

Jupyter Blog - Peter Parente

JupyterDay in the Triangle

The Day’s Agenda

Submit a Proposal

Register to Attend

Help Sponsor

For More Information

Jupyter Kernel Gateway

What is it?

What problem does it solve?

What’s next?

For More Information