- Feb 15, 2019
-
-
Joseph Weston authored
'temp' is too short a parameter name, especially for an API, and could be confused with 'temporary'.
-
Joseph Weston authored
-
Joseph Weston authored
-
Joseph Weston authored
-
Joseph Weston authored
-
- Feb 14, 2019
-
-
Joseph Weston authored
-
- Feb 12, 2019
-
-
Joseph Weston authored
Closes #263.
-
- Feb 08, 2019
-
-
Joseph Weston authored
Also fixup some docstrings for better formatting.
-
- Feb 06, 2019
-
-
Joseph Weston authored
-
- Feb 05, 2019
-
-
Joseph Weston authored
-
- Feb 04, 2019
-
-
Joseph Weston authored
-
- Dec 31, 2018
-
-
Anton Akhmerov authored
-
- Dec 20, 2018
-
-
Joseph Weston authored
-
- Dec 14, 2018
-
-
Joseph Weston authored
This avoids "sparse efficiency" warnings.
-
Joseph Weston authored
-
-
- Nov 28, 2018
-
-
Pablo Piskunow authored
-
- Oct 12, 2018
-
-
Anton Akhmerov authored
This has a lower chance to give an impression that the substitution happens in-place. Closes gitlab issue #237
-
- Sep 26, 2018
-
-
Christoph Groth authored
-
Christoph Groth authored
-
- Sep 21, 2018
-
-
Joseph Weston authored
-
- Sep 20, 2018
-
-
-
and without default values. Co-authored-by:
Joseph Weston <joseph@weston.cloud>
-
- Aug 14, 2018
-
-
Christoph Groth authored
-
Christoph Groth authored
So it's no longer necessary to provide the REFNAME environment variable. Also the link template string format is now more general to support at least gitlab github and cgit.
-
- Aug 09, 2018
-
-
Joseph Weston authored
-
Joseph Weston authored
'box-forced' is deprecated as of matplotlib 2.2.
-
- Aug 06, 2018
-
-
Christoph Groth authored
-
- Aug 03, 2018
-
-
Joseph Weston authored
Previously 'plotter.density' was not as well factored as 'plotter.current', which made it hard to compose, e.g. for passing custom parameters to 'plotter.interpolate_density'.
-
Joseph Weston authored
-
- May 22, 2018
-
-
Joseph Weston authored
-
Joseph Weston authored
Also add reference documentation for 'density'.
-
Joseph Weston authored
-
- May 18, 2018
-
-
Christoph Groth authored
Thanks to Alexandre Bernard for reporting this. https://mailman-mail5.webfaction.com/pipermail/kwant-devel/2018-May/000088.html
-
Christoph Groth authored
-
- Apr 03, 2018
-
-
Joseph Weston authored
Previously we used the matplotlib default behavior of setting the colormap limits (vmin and vmax) to the limits of the plotted data, if they are not provided by the user. Now we set the colormap limits to the 2nd and 98th percentile of the input data, and stretch the limits by 10% on either end in an attempt to include all the data in the limits. If we cannot do so we set the limits to the percentiles plus the stretch and issue a warning. Also, whenever the data falls outside the colorbar limits (even when the latter are set by the user) we set the appropriate ends of the colorbar to be pointy, indicating that the data extends beyond the colorbar. Closes #183
-
- Feb 27, 2018
-
-
Joseph Weston authored
This can always be resurrected from Git if it is really needed, but at the moment its just 3000 lines that aren't used.
-
- Feb 26, 2018
-
-
Joseph Weston authored
-
- Feb 22, 2018
-
-
Christoph Groth authored
Thanks to Tibor Sekera for suggesting this feature.
-
- Dec 15, 2017
-
-
Christoph Groth authored
Previously, in order to not to fix the matplotlib backend, we required users to import matplotlib.pyplot before calling any Kwant plotting functions. This did not have the desired effect, since we did import `matplotlib.backends` and that also fixes the backend. Now, both backends and pyplot are imported at the last possible moment and a warning is emitted if this fixes the backend.
-