Hello,
I just wanted to report what I believe is a bug, please forgive me if I am wrong.
Before, in the siesta input atomic coordinates could be written like this:
0.000 0.000 0.000 1
or like this:
0.000 0.000 0.000 1 Cr
However in the recent versions you could also write them like this:
Cr 0.000 0.000 0.000 1
Which indeed is more consistent with other DFT packages.
Then, when you run tb2j, there is a crash:
species = _a.fromiteri(map(lambda x: x.split()[3], species[:na])) - 1
ValueError: invalid literal for int() with base 10: '0.000'
Which it comes from sisl trying to extract the species type (1) from the number in the 4th position which is the z coordinate in this format (0.000).
In my case, I will just change to the old format my coordinates, but I wanted to report this issue.
Thanks a lot,
Dorye