Pol Febrer Calabozo

Hmm well I'm not sure which approach is better (object oriented vs functional), but to me it is not that clear that functional is better, specially for interactive programming. If...

I'm curious, who gave you that feedback? Was it from users? What is the problem of having many methods? Is it maintainability, usage or some other thing?

Hmm there are a lot of methods to convert indices which maybe could be in a single method called `indices`? It could work much like a unit converter: ```python geometry.indices([1,2,3],...

> although that is bad for chaining operations in the same line :( You could always add a `__getattr__` to `Geometry` to get the methods from the `operations`, `measurements` and...

> making the documentation easier to read. And easier for the GUI to present methods to the user of course :)

An example of the code or the plotting? I mean some object that handles the parametrization and ticks for a 2D mesh of k points, so that you can get...

Hmm but the `MonkhorstPack` grid only allows: - Planes that are orthogonal to a cartesian coordinate. - 2D grids that span the whole cell Right? I was thinking that one...

Sorry I didn't express myself right. See for example the reciprocal lattice of a simple cubic lattice:  You might want to sample the triangle formed by `Gamma`, `M` and...

For 2D band structures the k sampling would need to be in a surface, because then you can represent them as: `xy` the coordinates of the surface and `z` the...

> No, that is not correct, the size argument define the size of the BZ, and displacement defines the center of the BZ. > > You can even do better...