List view
- Due by June 15, 2022•3/3 issues closed
- Due by February 20, 2022•12/12 issues closed
- Due by January 20, 2022•18/18 issues closed
- Due by December 21, 2021•7/7 issues closed
- Due by October 18, 2021•7/7 issues closed
- Due by September 20, 2021•7/7 issues closed
- Due by August 16, 2021•9/9 issues closed
- Due by July 17, 2021•15/15 issues closed
- Due by May 17, 2021•14/14 issues closed
- Due by April 30, 2021•14/14 issues closed
- Due by March 17, 2021•5/5 issues closed
- Due by February 18, 2021•11/11 issues closed
- Due by January 26, 2021•13/13 issues closed
- No due date•4/4 issues closed
- No due date•4/4 issues closed
- Due by October 22, 2020•2/2 issues closed
- Due by October 21, 2020•11/11 issues closed
- Due by December 6, 2019•13/13 issues closed
🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄🦄
Due by May 12, 2017•9/11 issues closedMore drivers (notably UHFLI and alazar fixed), smaller fixes. Possibly remove multiprocessing completely.
Due by March 10, 2017•10/12 issues closedThis will remove all the print statements, and finally implement sane module wide logging. It may or may not work with multiprocessing out of the box, but then again multiprocessing is not a first class feature for now. The idea is to have a zmq based log handler implemented using the standard (much wow) python logging module, where every qcodes module gets a logger (and so should every driver). This way a QT and a web interface can easily be provided. The issues to explore are mostly related to how much scientist will blindly log without realizing that it's not free, and won't ever be free but then again, given how much print statement there are already and how slow they are we should not see any big hit.
No due date•4/4 issues closedMostly things that were meant to be in v0.1.2 but took Alex a bit longer to develop, or too incompatible to incorporate: refactor parameter, examples and missing documentation , QT plot
No due date•4/4 issues closedBasically make sure that most of the info is on the docs, but still lives in GitHub. THe idea being that scientist won't have to touch GitHub.
No due date•9/11 issues closedAll the quirks and features that are not really critical but still really relevant.
No due date•7/10 issues closedFirst release of QCoDes. Remove all the hacks that make it really hard to debug and sometime use. Simplify and modularise. Focus scientist facing APIs rather than implementation, aim to freeze APIs. Keep process based architecture as a second class citizen, because it is introducing more issues than benefits.
Due by October 21, 2016•12/12 issues closed