Pol Febrer Calabozo

> > I find it much easier to write documentation in notebooks. Could you give an example of the searching problem? The only problem that I noticed for now is...

I didn't know it was even legal to pass both a geometry and a lattice to Grid :sweat_smile:

I don't know if I should fix this or keep it in mind for the `sisl.viz` PR. My plan is to work on that during August so that I can...

What is the error exactly? Is it that when you use `plot_geom=True` you get the lattice of the geometry?

Ah ok, you can raise the error here: https://github.com/zerothi/sisl/blob/1ef16ed437174d84c510f6872f01f0613ffcbe9a/src/sisl/viz/plots/grid.py#L539-L545 Using `self.grid` or `grid`. But does different lattices make sense for other `sisl` functionalities?

I see, yes it makes sense :+1:

1. Agree 2/3. I don't understand the results you are proposing. Why do we need a 2D array of results? To me the result of categorizing should be an atom-wise...

> The main problem of the way things currently work is exactly that it is a category per atom. Isn't the problem that the category is computed atom by atom?...

By the way all this lazy arithmetic (and the caching) could be supported by the `nodes` framework.

> Yes, the problem is that it is an atom-wise property. That is exactly what I am trying to propose to go about. A Category should be able to encompass...