Talks  & Tutorial Presentations

SciPy is a community dedicated to the advancement of scientific computing through open source Python software for science, mathematics, analytics and engineering.

 

The SciPy Conference allows participants from academic, commercial, and governmental organizations to showcase their latest projects, learn from skilled users and developers, and collaborate on code development.

This year, we do not have specialized tracks or theme and welcome submissions on any scientific or analytical topic including (but not limited to): machine learning, data science, computational science, scientific visualization, image processing, and reproducibility.

Speakers will be notified on July 27th.

Important Talk & Tutorial Dates:

 

  • May 15, 2020

    • Talk & Tutorials call for proposals opens

  • July 8, 2020

    • Talk & Tutorials submission deadline

  • July 31, 2020

    • Accepted conference and tutorials speakers notified

  • August 11, 2020

    • Schedule Announced

  • October 30-31, 2020

    • SciPy Japan 2020 Conference

Program Chairs
Tetsuo Koyama, ARK Information Systems
 
Chris Angell, PhD, Enthought

Talks

Talks will be 25 min pre-recorded videos.

 

Planning for your Talk proposal submission?​

 

 

 

Proposals must be submitted by July 1, 2020. Here's what you'll need for a submission:

The Short Summary

The brief description which will appear in the online program and give attendees a basic sense of your talk. This should be around 100 words or less.

The Abstract

Your placement in the program will be based on reviews of your abstract. This should be a roughly 500 word outline of your presentation. This outline should concisely describe software of interest to the SciPy community, tools or techniques for more effective computing, or how scientific Python was applied to solve a research problem. A traditional background/motivation, methods, results, and conclusion structure is encouraged but not required. Links to project websites, source code repositories, figures, full papers, and evidence of public speaking ability are encouraged.

Tips for Submitting a Proposal

The SciPy Conference is in awe of the work that is being done in the community. We receive many interesting and thought-provoking proposals but we have a limited number of spaces. Please take a look at our tips below to improve your chances of having a talk accepted by the conference. In the unfortunate event that your proposal is not accepted, please keep in mind that you are welcome to give a lightning talk, book a room for a Birds of a Feather discussion.

  • Submit your proposal early.

  • In your abstract, be sure to include answers to some basic questions:

    • Who is the intended audience for your talk?

    • What, specifically, will attendees learn from your talk?

  • Ensure that your talk will be relevant to a broad range of people. If your talk is on a particular Python package or piece of software, it should useful to more than a niche group.

  • Include links to source code, articles, blog posts, or other writing that adds context to the presentation.

  • If you've given a talk, tutorial, or other presentation before, include that information as well as a link to slides or a video if they're available.

  • SciPy talks are generally 25 minutes with 2-3 minutes for questions. Please keep the length of time in mind as you structure your outline.

  • Your talk should not be a commercial for your company’s product. However, you are welcome to talk about how your company solved a problem, or notable open-source projects that may benefit attendees.

Many of these tips are adapted from the PyCon Proposal Resources. Thanks PSF!

Talks may be given in Japanese or English. We ask that you include both languages on the slides if possible.

 
 

Tutorials

Tutorials will be taught live.

Topics

Proposals must be submitted by July 1, 2020. Here's what you'll need for a submission:

Tutorials should be focused on covering a well-defined topic in a hands-on manner. We want to see attendees coding! We encourage submissions to be designed to allow at least 50% of the time for hands-on exercises even if this means the subject matter needs to be limited. Tutorials will be 4 hours in duration. In your tutorial application, you can indicate what prerequisite skills and knowledge will be needed for your tutorial, and the approximate expected level of knowledge of your students (i.e., beginner, intermediate, advanced).

For examples of content and format, you can refer to past tutorials from past SciPy tutorial sessions (SciPy 2019, SciPy 2018, SciPy2017)

 

We are looking for interesting techniques or packages, helping new or advanced Python programmers develop better or faster scientific applications.

Information for Tutorial Presenters

Selection

Accepted tutorials will be announced late July. Final tutorial materials and instructions for attendees will be due on October 1st. This will include final version numbers of required software, detailed and tested installation instructions, and a test script that can be run by attendees to ensure that they have sufficient time to prepare their laptops before the conference. In addition, there will be a pre-tutorial slack channel created before the conference, and tutorial presenters are expected to make themselves available to help with setup instructions.

Stipend

In recognition of the effort required to plan and prepare a high quality tutorial, we pay a stipend of $500 to each instructor (or team of instructors) for each half-day session they lead.

Submission

For the submission you will need the following information:

  • A short bio of the presenter or team members, containing a description of past experiences as a trainer/teacher/speaker, and (ideally) links to videos of these experiences if available.

  • A list of prerequisite skills expected of attendees, so that participants can choose level appropriate tutorials.

  • A description of the tutorial, suitable for posting on the SciPy website for attendees to view. It should include the target audience, the expected level of knowledge prior to the class, and the goals of the class.

  • A more detailed outline of the tutorial content, including the duration of each part and exercise sessions. Please include a description of how you plan to make the tutorial hands-on.

  • Detailed installation instructions for various common Python environments so that attendees can have everything ready for participating before heading to SciPy.​

  • If available, the tutorial notes, slides, exercise files, and IPython notebooks, even if they are preliminary.

Authors of exemplary submissions from previous years have generously agreed to share their proposals to help new instructors: https://github.com/scipy-conference/scipy-conference/tree/master/data/tutorial_submissions