The array index will not be correctly found when pvpq array is not sorted

[chengts95]

Check This line
pvpq_lookup = zeros(pvpq[-1]+1, dtype=int), I think the pvpq[-1] may not always be the largest index of the pvpq array, it should be like pvpq_lookup = zeros(pvpq).max() , dtype=int) to ensure the largest index will be always found. This can help to compatible with common pypower case format.

[lthurner]

The functions in pandapower/pypower_extension are for now only recommended to use within pandapower, not with casefiles that were not generated by pandapower.

We want to make the numba accelerations available for pypower, so that they work for all pypower casefiles. There are probably some issues to resolve before this generally works, and this is one of them, so thanks for pointing it out. For now, this is nothing that needs fixing in pandapower, since it works for casefiles generated by pandpower (pandapower always creates casefiles with consequitie bus numbering).

[chengts95]

Thanks for the reply, I was calculating a customized power systemwhich had been created in pypower before in pandapower. In fact I used the converter.fromppc at first, but the conversion was a little inaccurate due to the differences in the transformer's model(seems to be another issue). that is why I modified some functions in pypower_extension to make the pandapower's runpf directly compatible with pypower cases to verify the results.

[jhmenke]

If the transformer caused differences after conversion, you can take a look at the trafo_model parameter of your transformers. Maybe changing the type from "t" to "pi" or vice versa is enough to fix your problem.

http://www.uni-kassel.de/eecs/fileadmin/datas/fb16/Fachgebiete/energiemanagement/Software/pandapower-doc/elements/trafo.html#electric-model