Skip to content
Create an open-source library in Python for your scientific research.
Jupyter Notebook Python
Branch: master
Clone or download
Latest commit cfd0299 Oct 4, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
images add image Oct 4, 2019
mylibrary remove qutip from yml Apr 8, 2019
.gitignore git ignore Apr 10, 2019
0-open.md Update 0-open.md Sep 10, 2019
1-code.md update code section git Apr 11, 2019
2-develop.md add full stop Apr 10, 2019
3-test.md travis Apr 20, 2019
4-package.md changes Oct 4, 2019
5-docs.md add full stop Apr 10, 2019
6-distribute.md changes Oct 4, 2019
7-publish.md
8-host.md add links page Apr 16, 2019
9-links.md add packaging links Apr 26, 2019
LICENSE Create LICENSE Apr 11, 2019
README.md update readme fixing typo Oct 4, 2019

README.md

scikit-project: A Guide to Building Your Open-Source Science Project

A cheatsheet to develop a scientific open-source library from scratch.

scikit-project

Zero to Library

Here you will find information to design, build, and release an open-source library to perform scientific research in Python from scratch to finish.

0 - Open Source for Open Science: Some information about the Python and open source ecosystem, and how they relate to open science are also given.

  • StackOverflow

1 - Before Starting Coding: Setting up the working environment on your machine, including the tools you will need to write code efficiently.

  • Sublime, Git, GitHub

2 - Developing your Project: A step-by-step guide with best practices for coding, and tips for making code development as effortless as possible.

  • PEP 8, PEP 257
  • jupyter notebook
  • nbconvert

3 - Testing: Especially in software related to scientific research, at start, the destination is not always crystal clear. Code is written, optimized, reorganized. Unit testing is a crucial task to avoid getting lost in the process.

  • nose2, pytest
  • Travis CI

4 - Packaging: Build your package to import your library like any other library.

  • setuptools

5 - Documentation: "Code is more often read than written" said Guido Van Rossum, the creator of Python. This is especially true for collaborative projects in the scientific research space, in which researchers might interact with code in a delocalized manner, at different times, and on different time scales. Making good comments of features, from functions to classes, allows one to generate with little effort a full fledged online documentation, drastically increasing the rate of adoption.

  • Sphinx
  • Read the Docs

6 - Distributing: It's time to release your library. Making importing your library easy is a key feature for its users, potential future contributors. Several tools now allow to deploy code in a variety of environments using package managers.

  • conda-forge
  • pip

7 - Publishing: As a researcher, you are asked to publish your research results. In the case of a code project these can be novel research results derived from the software or the software itself, if it provides an innovative method or approach that can help the research community. Some examples on best practices to publish code and datasets are given, such as considering Zenodo for file hosting and an immediate DOI reference. A list of research journals especially relevant for physicists is provided.

  • Zenodo

8 - Hosting: Interactive notebooks allow users to play with your code effortlessly, without worrying about installing software. They are also a great solution for interactive workshop and in the classroom, as they allow students and in general users to tinker with code without any installation.

  • My Binder
  • JupyterHub
  • BinderHub

9 - Useful Links: A collection of useful links is provided.

This Repository

This library is thought to help you in two ways:

  1. The files linked above in the table of contents provide a guide that you can navigate to learn more.

  2. The folders present in this repository have all the contents to build an example of mylibrary and deploy it. You can then modify the contents according to your project. The mylibrary folder comprises:

  • mylibrary/mylibrary: where the code is located;

  • mylibrary/mylibrary-notebooks: where the .pynb notebooks are kept.

Other folders will be automatically generated by the setup.py file and by creating the documentation.

References

This project stems from a series of talks, lectures, and other ideas developed in relation to the QuTiP (Quantum Toolbox in Python) library and open source in quantum-tech research. The aim is to provide useful information in a concentric way, starting from the quantum-tech research community, to the physics, academic and in general scientific community engaging with open-source software.

"Open-source scientific computing for quantum technology: QuTiP", Nathan Shammah RIKEN Berkeley workshop, Berkeley, USA, 2019

"The rise of open source in quantum physics research", Nathan Shammah and Shahnawaz Ahmed, Nature's physics blog, January 9, 2019

"Make Your Code Count", Shahnawaz Ahmed FOSDEM Conference - Quantum Software Track, Bruxelles, Belgium, YouTube, 2019 JST ImPACT School, Toyama, Japan, 2018

"Bit to QuBit: Data in the age of quantum computers", Shahnawaz Ahmed, PyData 2018, Warsaw, Poland, YouTube, 2019

"Scientific computing for quantum technology", Nathan Shammah, EuroSciPy 2018, Trento, Italy, YouTube, 2018

You can’t perform that action at this time.