Giter Club home page Giter Club logo

qutip-doc's Introduction

QuTiP: Quantum Toolbox in Python

A. Pitchford, C. Granade, A. Grimsmo, N. Shammah, S. Ahmed, N. Lambert, E. Giguère, B. Li, J. Lishman, S. Cross, A. Galicia, P. Menczel, P. Hopf, P. D. Nation, and J. R. Johansson

Build Status Coverage Status Maintainability license PyPi Downloads Conda-Forge Downloads

QuTiP is open-source software for simulating the dynamics of closed and open quantum systems. It uses the excellent Numpy, Scipy, and Cython packages as numerical backends, and graphical output is provided by Matplotlib. QuTiP aims to provide user-friendly and efficient numerical simulations of a wide variety of quantum mechanical problems, including those with Hamiltonians and/or collapse operators with arbitrary time-dependence, commonly found in a wide range of physics applications. QuTiP is freely available for use and/or modification, and it can be used on all Unix-based platforms and on Windows. Being free of any licensing fees, QuTiP is ideal for exploring quantum mechanics in research as well as in the classroom.

Support

Unitary Fund Powered by NumFOCUS

We are proud to be affiliated with Unitary Fund and numFOCUS.

We are grateful for Nori's lab at RIKEN and Blais' lab at the Institut Quantique for providing developer positions to work on QuTiP.

We also thank Google for supporting us by financing GSoC students to work on the QuTiP as well as other supporting organizations that have been supporting QuTiP over the years.

Installation

Pip Package Conda-Forge Package

QuTiP is available on both pip and conda (the latter in the conda-forge channel). You can install QuTiP from pip by doing

pip install qutip

to get the minimal installation. You can instead use the target qutip[full] to install QuTiP with all its optional dependencies. For more details, including instructions on how to build from source, see the detailed installation guide in the documentation.

All back releases are also available for download in the releases section of this repository, where you can also find per-version changelogs. For the most complete set of release notes and changelogs for historic versions, see the changelog section in the documentation.

The pre-release of QuTiP 5.0 is available on PyPI and can be installed using pip:

pip install --pre qutip

This version breaks compatibility with QuTiP 4.7 in many small ways. Please see the changelog for a list of changes, new features and deprecations. This version should be fully working. If you find any bugs, confusing documentation or missing features, please create a GitHub issue.

Documentation

Documentation Status - Latest

The documentation for the latest stable release and the master branch is available for reading on Read The Docs.

The documentation for official releases, in HTML and PDF formats, can be found in the documentation section of the QuTiP website.

The latest development documentation is available in this repository in the doc folder.

A selection of demonstration notebooks is available, which demonstrate some of the many features of QuTiP. These are stored in the qutip/qutip-tutorials repository here on GitHub.

Contribute

You are most welcome to contribute to QuTiP development by forking this repository and sending pull requests, or filing bug reports at the issues page. You can also help out with users' questions, or discuss proposed changes in the QuTiP discussion group. All code contributions are acknowledged in the contributors section in the documentation.

For more information, including technical advice, please see the "contributing to QuTiP development" section of the documentation.

Citing QuTiP

If you use QuTiP in your research, please cite the original QuTiP papers that are available here.

qutip-doc's People

Contributors

aagentile avatar ajgpitch avatar alexios-xi avatar anubhavvardhan avatar bencbartlett avatar boxili avatar cgranade avatar christian512 avatar davidschlegel avatar ericgig avatar hodgestar avatar jakelishman avatar javadnoorb avatar jrjohansson avatar kwyip avatar mrrobot2211 avatar nathanshammah avatar nonhermitian avatar nwlambert avatar phyks avatar purva-thakre avatar quantshah avatar samwolski avatar stared avatar tehruhn avatar tgag17 avatar wrzadkow avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

qutip-doc's Issues

Extraneous backslashes in latexpdf ipython output

There are a lot of backslashes in the place of where [OUT] would expected to be seen in the ipython generated latex.
For example:

\PYG{g+go}{\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}\PYGZbs{}

(this actually goes on much longer, I just copied a fraction of it)

Does not appear in the HTML output

Ipython directive breaks for functions

The sphinx Ipython directive parser breaks for functions. See ipython/ipython#11362

This breaks our documentation build as the code blocks in qutip-doc/guide/dynamics/dynamics-bloch-redfield.rst define some functions which cannot be produced by the Ipython directive. I spent a lot of time trying to make this work but to no avail.

I have a completely new version of the docs where I setup Sphinx from scratch which does not require the Ipython directive to run. The only catch is that we have to manually run the code blocks and generate the output and put them in the docs. I am trying to find other automated ways but would actually be happy to move from Ipython and just use the doc-test directive provided by Sphinx.

@nathanshammah @ajgpitch Let me know what do you think? It is time we update the documentation generator.

Remove matplotlib.sphinxext.only_directives

Matplotlib removed the sphinx directives and they are a part of Ipython now. See issue. So anyone on the latest Sphinx will face an error when trying to build the documentation.

This was also faced in #62. I have a version of the docs built from scratch with the latest sphinx which should fix this. Just thinking of the best way to deal with figures and output without using IPython at all as it leads to other issues.

Running Sphinx v1.8.4

Extension error:
Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')
make: *** [html] Error 2

Update qutip

Hi
I can't update qutip to last version
What I do?

Build depends on missing examples?

In trying to get the doc build working, I ran make html with an up-to-date Sphinx installation and got the following error:

Exception occurred:
  File "/home/cgranade/academics/software-projects/qutip-doc/_sphinxext/plot_directive.py", line 633, in run
    fd = open(source_file_name, 'r')
IOError: [Errno 2] No such file or directory: u'/home/cgranade/academics/software-projects/qutip-doc/../qutip/qutip/examples/ex_50.py'

The mentioned directory, ../qutip/ is the correct location for my local clone of qutip/qutip, but there doesn't seem to be an examples folder at all in qutip/qutip@a44a3c3. The only mention I can find of ex_50.py is in README.txt.

Duplicate entry for 'Monte Carlo Solver' in html doc sidebar

Screen Shot 2019-09-04 at 10 00 43

As can be seen in the image, there is a duplicate entry for 'Monte Carlo Solver' in the sidebar of the html documentation. It appears on different browsers and operating systems, so I believe it to be a misconfiguration in the docs themselves.

I'm happy to work on this, although I don't have much experience with sphinx.

Add sphinx-doctest

Using sphinx-doctest allows to test the examples in rst. The doctest directive for interactive code blocks allows to test examples. For static blocks this can be done with testcode (matched by testoutput and eventually with the ghost block testsetup).

Problem buliding for 4.4

Working in my branch:https://github.com/Ericgig/qutip-doc/tree/build4.4
I have problem building the doc.
Main errors
RuntimeError: Non Expected exception in qutip-doc/guide/guide-states.rst line 615
and
qutip-doc/guide/guide-visualization.rst line 331
Any help appreciated.
ps. matplotlib 2.3, scipy 1.2, recent version don't work.
patch for scipy 1.3 comming.

Add a list of libraries using qutip and qutip plugins

There are several libraries that rely on QuTiP for quantum physics or quantum information processing. Examples include Krotov, Matsubara and PyEPR. It would be nice to have a place in the documentation (and on the qutip website, possibly even beyond the documentation) where these are listed, with links taking to them and a short, one line description.

A difference could be made in cathegorizing them between "libraries using QuTiP" and "QuTiP plugins" (they heavily rely on QuTiP for basic functionalities).

The Github tool "Used by" could be used for to find all of the former that are just not forks.

Instructions for installing on Windows with Python 2.7 / 3.4

@nonhermitian I am very happy with the idea that we state clearly that we will only offer support for qutip on Windows using Python 3.5+ and Visual Studio as the compiler. However, there are some users who don't have the ~10GB free needed for Visual Studio 2015. I have just been helping such a student here.

I see in the latest version of the installation docs we no longer give any information on installing qutip on Windows with Python 2.7 / 3.4. Can I add something on distutils.cfg and mingwpy? This seems to work ok with the new c++ extensions.

Bibliography crashes on build with docclass 'memoir'

The latest conda version of sphinx 1.5.1 fails to build the latex documentation
Doesn't like any biblio entries.

! LaTeX Error: \begin{bibitemlist} on input line 1547 ended by \end{sphinxthebibliography}.

Builds ok with sphinx 1.4.6
I think it's related to sphinx-doc/sphinx#2629
Anyway, I have tried with docclass 'manual', and ditching our preamble, and I think it looks better anyway.
@nonhermitian I am going to proceed this way unless anyone says that memoir is essential.

Cannot build documentation

Hi,

After installing the required dependencies and cloning the repo, I issued the following command:

make html

and got the following error:

Extension error:
Could not import extension matplotlib.sphinxext.only_directives (exception: No module named 'matplotlib.sphinxext.only_directives')
make: *** [latexpdf] Error 2

What am I doing wrong? Can anyone help me fix this please? Thanks!

Building docs locally ?

How should I build docs locally ?

I am making changes to docstrongs in qutip/qutip and I want to test the build. For this, I have a clone of qutip/qutip folder but the makefile is in qutip-doc. Should I clone qutip-doc in the local folder of qutip/qutip ?

Document Models - PIQS

@nathanshammah @sahmed95
Documentation is required for Models and specifically PIQS

Does not need a lot. Can just copy some stuff from the intro notebook
Also the module needs linking for the API docs

Pin Sphinx version exactly for build depending on Python version

At this link, a line is given to install doc build dependencies. The problem is that it installs the latest version of Sphinx which has an issue with missing colon when documentation is built.

When I build documentation locally, the colon in the screenshot after inpt below does not appear.
image

I use Python 3.8 in my virtual environment which is incompatible with the Sphinx version specified in this configuration file. So, to install this older version of Sphinx, a user will also have to make sure they switch to Python 3.6. This will also end up installing older versions of many dependencies.

For more information, see the fix applied by RTD and the issues references within for an earlier version of Sphinx . One of the issues in the RTD link discusses enforcing the build in html4 or making changes in CSS to avoid this error (don't know if any of these would fix it or not).

qutip badge on read the docs failing

QuTiP's read-the-docs badge, which should tell if the documentation is building correctly, says it is failing. This could be related also to the way qutip's documentation is built, not from qutip/qutip, but from qutip/qutip-doc.

broken API documentation?

It looks like the latest API documentation has a problem (unless this is a display problem on my end only - in which case I must apologize).

Example: looking at http://qutip.org/docs/latest/apidoc/classes.html#qobj , what I see as the first two Parameters of Qobj is:
inptarray_like
dimslist

I suspect this should be inpt: array_like and dims: list
Is this an issue related to the space preceding the colon in the corresponding docstrings in the qutip source code?

Capture

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.