Closed joellohyy closed 7 years ago
Hi!
Thank you for reporting the issue. Your problem can be spitted into two problems.
1) The "Ox. state" field is always shows charges in CIF file, doesn't matter your command line. Therefore you should look to net column "Used". There you can find charges, which will be processed in the program. If you run, for example, your command with -q
option without dry-run (the run will take around 30 seconds)
supercell -q -p "In1:c=+3" -p "In2:c=+3" -p "O1:c=-2" -i 2310009.cif
or in short form
supercell -q -p "In*:c=+3" -p "O*:c=-2" -i 2310009.cif
You can see supercell_coulomb_energy.txt
file with proper electrostatic energy inside. As you can see, the program got your charges.
2) The second problem is why the oxidation number is NaN in supercell, despite it is specified in CIF file. The reason is that supercell program requires full matching for labels in _atom_site_label
and _atom_type_oxidation_number
. If you change last 5 lines of your CIF file to
loop_
_atom_type_symbol
_atom_type_oxidation_number
In1 +3
In2 +3
O1 -2
and run supercell program, you will get an expected result
----------------------------------------------------------------
| Atom Label | charge | mult | occup x mult
| | Ox. state | Used | (cif) |
----------------------------------------------------------------
| In1 | 3 | 3 | 8 | 8
| In2 | 3 | 3 | 24 | 24
| O1 | -2 | -2 | 48 | 48
----------------------------------------------------------------
Ah I see! Thanks!
Hi, when I tried to run the supercell.exe on In2O3 2310009.cif (as shown below), ./supercell -d -i 2310009.cif, it outputs
If I manually set the charge ./supercell -d -p "In1:c=+3" -p "In2:c=+3" -p "O1:c=-2" -i 2310009.cif I still get nan in the ox.state table.
I've managed to run the examples in the tutorials without any problems, the Ox.state column would show the correct values.
I don't see a problem in the cif. file below. How do I set the Ox charge properly?
Precompiled supercell program in Ubuntu 14.04.